ADE Version 1.60.4836 Beta Released

[GHD]

I am running W7 (64 bit) Home Premium with SP1.

Net Framework 4 Client Profile and Net Framework 4 Extended.

Sorry Don, moving individual vertices does work (on both XP and W7)

The problem is that as soon as I release the mouse button, the polygon disappears until I resize the window. So, it takes multiple attempts to move the vertex to the required place.

Reloading a saved project does not show the polygon in the same place that it was on save (Both XP and W7).

PS. I have Net Framework 2.0, 3.0, 3.5 and 4 on XP.

 

[gadgets]

Sorry Don, moving individual vertices does work (on both XP and W7)

Whew!!

Net Framework 4 Client Profile and Net Framework 4 Extended.

Don't know what these are or how they might be affecting the editor - but I'll find out.

Reloading a saved project does not show the polygon in the same place that it was on save (Both XP and W7).

I'm reworking that area now. However, it's curious that it doesn't work for you since it does work for me. (You did catch my earlier point that correct operation will only occur after a recent save following an edit of the object.)

The problem is that as soon as I release the mouse button, the polygon disappears until I resize the window. So, it takes multiple attempts to move the vertex to the required place

Maybe this is related to Net Framework 4 Client Profile and/or Net Framework 4 Extended. We'll see.

Don

 

[GHD]

Maybe this is related to Net Framework 4 Client Profile and/or Net Framework 4 Extended. We'll see.

and Net Framework 2.0, 3.0, 3.5 on XP

Moving vertices behaves exactly the same on both XP and W7.

Yes, I saved the edit, compiled then saved the project before reloading the project.

Edit. According to Martin's Environment Checker, I have .NET 2.0, 3.0 and 3.5 on W7.

 

[gadgets]

The attacked update (Version 0.0.19) fixes - or should fix -all processing issues reported to date.

George, I'm confused.

I am running W7 (64 bit) Home Premium with SP1.

Net Framework 4 Client Profile and Net Framework 4 Extended.

PS. I have Net Framework 2.0, 3.0, 3.5 and 4 on XP.

and later

and Net Framework 2.0, 3.0, 3.5 on XP

Edit. According to Martin's Environment Checker, I have .NET 2.0, 3.0 and 3.5 on W7.

Also, I've made a brief web-search on Net Framework 4 Client Profile and Net Framework 4 Extended. The former appears to allow you to run with an abbreviated set of NET 4.0 features while the latter seems to undo what the former does.

I have removed all attempts at updating the picturebox on a custom basis. Whenever I make a change that affects the display, I invalidate the entire viewing area and call for the dialog to be refreshed. The rest is up to Windows.

Is there any way you can run with "pure 3.5 or 4.0 on your Win 7 system?

Since neither Jon nor I (nor anyone else) is reporting the "disappearing display" issues you are experienceing, I'm inclinded to believe the underlying cause of the problem (in part, at least) lies within your system.

Don

PS, George. Are you running Win 7 in XP emulation mode? (Thanks, for the thought, Jon) If so, could you also please give it a try in "native" mode.

 

[GHD]

Is there any way you can run with "pure 3.5 or 4.0 on your Win 7 system?
Since neither Jon nor I (nor anyone else) is reporting the "disappearing display" issues you are experienceing, I'm inclinded to believe the underlying cause of the problem (in part, at least) lies within your system.

Systems and It isn't feasible to remove any of the Net Framework versions.

BTW. Who apart from yourself and Jon are running the GP Editor?

PS, George. Are you running Win 7 in XP emulation mode? (Thanks, for the thought, Jon) If so, could you also please give it a try in "native" mode.

No, I am running native 64 bit W7 but with Aero disabled.

 

[GHD]

Version 0.19 is worse.

I still need to resize the window (on both machines) to see the polygon.

And now it won't compile on either machine



Log file sent to Jon.

 

[gadgets]

The compile error is an (unexpected) side effect of the changes I made to improve the positioning on re-edit. (I forgot to change the compiler.) You'll have a new version by morning (your time).

Don

 

[gadgets]

Updated Verion 0.0.20 attached. It fixes the compile problem introduced in 0.0.19.

Anyone following this thread knows that George has been having some difficulty with the vertex display disappearing from the display area of the editor, and that neither Jon nor I can duplicate the isssue. Since George is unable to reconfigure his system to help isolate the "disappearing display on mouse-click" issue, it would be very helpful if those who have run any recent version of this sofware would report experiencing (or not) similar difficulties.

Don

 

[GHD]

It now compiles (on both systems)



But it is still unusable because the texture mapping is not saved in the ADE project.

From the pic above, it is obvious that the texture mapping is reasonable, however, on reloading I see this on W7:



And this on XP:



As you can see they are both totally different

There is still the necessity to resize the window to see the polygon on both systems.

 

[gadgets]

George, I don't know what to tell you. The texture mapping is saved by ADE, both in a session and across sessions. On my system, the texture mapping is preserved - using your ADE file.

I appreciate that what you are seeing would lead you to believe differently. But, until we find a way to duplicate the issue, I don't know what more I can do about it.

Attached is a messaging verion of 0.0.20. Please capture the data coming into the editor, the data going out without making any edits and the data coming back in again for an object that demonstrates the issue.

As for having to resize the window, I'm letting windows handle everything to do with updating the display after invalidating the entire display after every change that affects the display - including on the MouseDown event. Until I can duplicate the issue, finding what's causing it will be pure luck - but I won't stop looking.

It will be interesting to see whether anyone else reports such issues. (Jon has already confirmed he doesn't.)

Don

 

[gww53]

mostly working so far

Win 7-64 sp1
Ivy 3770
FSX

I've not had any of the display issues described in this thread- and I have only downloaded the first of the "repair" patches. There is a barely noticeable flicker when I drag a polygon. But I've only managed just some basic polygons and lines.I have an immediate display in the gp editor with no manipulation, click, etc. And I have no "blanking" of the display with manipulation.

That's not to say it's all smooth--but I attribute that to me. I've had some problems. On my current project, all was well until about the 5th GP I added, at which point compile attempts locked the computer--no message. The GP bgl had disappeared--just the ADEX bgl remained in my addon/scenerey file-- but the gp polys remained in the ad3; any effort to re-compile led to a complete lock-up (task manager to close adex). Fault finder found no errors. When I deleted the GP from the project ad3, all worked again. I've been adding them back, and have not had a recurrence.

My outlines don't seem to work quite right. Tried repeatedly. See attached pictures. In the GP editor I have a poly with asphalt texture and a red outline. But in FSX, the display is of a red box in the area of part of the outline, and the asphalt without any red outline in another part. Have had similar problems on several outline attempts (concrete around asphalt, etc)

I guess I don't understand the use of the numbers/ground graphics despite multiple re-reads of the instructions, but I've not had much time to experiment. I'm struggling with resizing the polygon (in gp poly edit box or adex) vs re sizing the texture sheet (can't seem to do that) so I'm getting the entire sheet displayed. But that's another topic...not here, not now.

But...I get a display of the poly and texture in the editor with no manipulation required. I hope I've followed the thread and the problem....if not, ignore please!!

Gary

 

[scruffyduck]

It now compiles (on both systems)



But it is still unusable because the texture mapping is not saved in the ADE project.

From the pic above, it is obvious that the texture mapping is reasonable, however, on reloading I see this on W7:



And this on XP:



As you can see they are both totally different

There is still the necessity to resize the window to see the polygon on both systems.

Just to confirm from the ADE perspective what is saved. There is a data object (DTO) that is passed between ADE and the Editor. This contains all the data that is passed from the editor when the object is created. ADE will send that back when the user asks to edit the GP. The DTO is specified by the editor code - in fact we have an API document that Don wrote and is used by both of us to handle data transfer.

This entire DTO is saved in the ADE project file. In fact all the properties displayed in the tool tip are extracted from the DTO and ADE does not duplicate anything. ADE is responsible for setting the vertices only.

 

[GHD]

Since the results are different on each machine, It looks suspiciously like an uninitialised memory problem. I am using the same project file on each machine.

I will delete both the line and polygon and start again.

 

[GHD]

Attached is a messaging verion of 0.0.20. Please capture the data coming into the editor, the data going out without making any edits and the data coming back in again for an object that demonstrates the issue.

I can't see what a .print file will do, the name in the zip is "ADE_GroundPolys.dll.print". Anyway, nothing happens when I load the editor nor when I save.

Might it be better to write to a "log" file?

 

[scruffyduck]

I can't see what a .print file will do, the name in the zip is "ADE_GroundPolys.dll.print". Anyway, nothing happens when I load the editor nor when I save.

Might it be better to write to a "log" file?

George

Move the existing ADE_GroundPolys.dll out of the way to another folder. Copy the one with .print into the ADE main folder. Remove the .print and start ADE again.

 

[GHD]

I have yet another problem, the scroll bars.

If I move the horizontal scroll bar, the picture doesn't change but when I release the mouse button, the scroll bar disappears

Before dragging:



After dragging:

 

[GHD]

OK, this is the sequence:

After select and pressing <Return>



In the editor (after a slight re-size)



Without changing anything (except re-size) and clicking on "OK":



Wouldn't it be better if I were to orient the triangle onto the texture before clicking on "OK"?

 

[GHD]

There is a difference when using the "print" dll.

The picture in the editor on W7 is now exactly the same as on XP and not with the triangle positioned way off to the north-west.

(and there or no scroll bars)

Hmm, it is not exactly the same but similar:

 

[GHD]

I may have an inkling of what is going on (apart from the necessity to resize )

When the dialog has been zoomed-in whilst re-orienting the polygon, the coordinates are beeing saved in the zoomed-in state. When the file is reloaded, those coordinates are being applied in the default window which is in a different zoom state.

Please bear with me, the following is a long sequence since all I can show are screenshots.

Enter the editor:





Move the triangle:



Click "OK"



Compile:



And in FSX.



Note. I didn't zoom-in on the editor display.

Reload the project.



Note the triangle is in the same place as when saved.



Reorient the triangle such that it is over the "1" (I needed to zoom-in)



Click OK and compile:









Reload the project:



Note. The triangle is not over the "1", it has been restored with the same screen coordinates as the zoomed-in state when the prohect was saved.



So, my feeling is that there is a problem in that the reference point for the screen coordinates changes with zoom.


I can just about live with the re-sizing problem but not with the save/load.

 

[gadgets]

I've not had any of the display issues described in this thread And I have no "blanking" of the display with manipulation.

Thanks for that confirmation Gary.

at which point compile attempts locked the computer--no message. The GP bgl had disappeared ... When I deleted the GP from the project ad3, all worked again. I've been adding them back, and have not had a recurrence.

Should that happen again, please send me your AD3 file.

My outlines don't seem to work quite right.

I can see that. I made some changes in the poly triangulation area yesterday. Perhaps I broke something. I take a look.

Don