Mario Donick

So, 2 months later -- any news on the update?

The OSM2XP repository does not have data for Australia, but you can still download OSM data for Australia, for example here: http://download.geofabrik.de/osm/australia-oceania/ Download australia.osm.pbf. Then use the OSM2XP converter with these data (it will take several hours to process) and put the resulting folder in your custom scenery folder. Sydney (and the rest of Australia) should not be empty anymore. One thing to remember when using OSM: To avoid OSM buildings interfering with custom airport scenery (this happens sometimes), you sometimes have to edit the airport scenery, for adding an exclusion zone for facades and objects. Open the airport with OverlayEditor, select "exclusions" in the dropdown list on the right side, select exclusion type (at least "facades"), then click the green "+" button in the toolbar and draw a frame where you want to have the exclusion. Then save.

Both videos show mainly OpenStreetMap buildings, which are available for free, as pointed out by chris, via OSM2XP. This tool converts OpenStreetMap data into buildings, which resemble rather good the real form, size and place of the real buildings. The payware sold under the name "Photo Realistic Copenhagen" (or many other cities), available for example at simmarket, is nothing more than this -- OSM2XP buildings.

I have noticed this bug, too and posted it some days ago at the .org. Nobody had an idea about this (except memory problems, which seem unlikely).

Small question: I already used the Corvalis very often since I purchased it. Everytime on the same computer. Today, the activation dialogue showed up again and I had to enter again my x-aviation email address and password. Yesterday there have been 13 Windows updates, so maybe this was the reason? 1. Is this intended? 2. Will this use up activation slots or sth. (so maybe the next time there are Windows updates, I can't activate the plane again?) Thanks, Mario

Okay, thanks for the info. I'll then simply use the 1.3 for the article.

Are we speaking of a few weeks (2, 3) or months (2, 3)? And will there be significant changes to the plane, or mainly under the hood, not so noticeable for the pilot? If this is the case, I may well use the 1.3 and simply add a small note about the update in my article.

When will update 1.4 be available, i.e. what does mean "soon" when you post this in other threads? I may use this plane for a 4-page printed article I write for German "FSMagazin" for which I'm working as freelancer. (For them I also wrote about LES' DC-3, this issue will be available in August 2012). Would be great to have the latest version when writing that article.

Will do. Even if not, this whole thing is not that critical as it seems. Most of the time, it works. Usually, I don't change flight plan during flight, so once I'm in the air, everything is okay, and if I'm not yet in the air, it does not take much time to re-load the plane and start over.

As you can see (when you watch the video in fullscreen at YouTube), I simply enter a flight plan, with occasionally wrong buttons pressed. Simply follow the mouse cursor to see what I enter (you can even read the letters on the MFD) and what else I press. First, enter a flightplan. Works obviously very well, as you can see. After flight plan is entered: 1) close ready pad 2) close FPL window 3) press MAP 4) press TOPO 5) press TERRAIN 6) press TOPO 7) press BACK 8) press DECLTR (4 times!) 9) press FPL at the PFD 10) press FPL at the MFD 11) press inner + knob (several times --> flickers, and this should not happen) 12) open ReadyPad 13) switch to previous waypoint in flight plan (several times, so that in the end the 1st waypoint is selected) 14) press inner + knob (flickers --> this should not happen, instead the leg window should be shown) In the video, you can see me hovering some other buttons, but I only pressed the buttons mentioned in my list. Problem is, that even with these steps, the issue sometimes happens and sometimes not. I just gave it a try again and this time the system was stable. This unpredictability is my main concern: If I knew when the bug is guaranteed to happen, I could avoid any steps leading to it. But I don't know when exactly it happens, so I can just pray that the system stays okay this time.

Hi Cameron, thanks for trying. I've uploaded a video that demonstrates the problem. (Please watch in high res and 720p, to see the details). http://www.youtube.com/watch?v=v3sjWSzOk3k I start with entering several waypoints -- that works okay. I then (about 2:10) switch between some map modes, press the FPL button on the PFD and then return to the FPL on the MFD. Then, the problems start: I can't get the existing waypoints to open (i.e. I can't edit, but I could before!), and I can't enter new waypoints. See the flickering that starts at 2:40 when I press the knob to get the small window open? The window appears, than immediatly disappears. In 2:59 I try to add a new waypoint, but here the window again just flickers (and shows "USS Nimitz", when in XP10). You can see all my steps, so you can tell me what happens.

I can confirm the observation in XP 9.70 (Demo). I basically simply switched forth and back between FPL pages, scrolled up and down between waypoints, opened them, closed them again, then closed the FPL, made some map display adjustments, opened FPL again. What is different in XP 9 in contrast to XP 10: When the windows flashes, in XP 10 is shows "USS Nimitz", in XP 9 it does not show any name.

I deleted my old XP9 installation due to disk space reasons, and because XP10 runs very fine. But I will download the XP9 demo, update it if necessary to 9.70 and try the Corvalis in the demo. The 10 minutes should be enough to show any problems. I'll report back here then.

Okay, here are some more information: XP10, latest beta. Windows 7. Using the Gizmo version delivered with the recent DC-3 aircraft. No other plugins. I can't give you exact steps to reproduce, but simply do the following -- takes less than 5 minutes: Press FPL on MFD, in 2D display, open ReadyPad. Enter some waypoints, but make some deliberate mistakes in pressing the correct buttons, for example forget to press INIT or forget to press the "Direct to" button on the ReadyPad, then try to correct, also mess around with the inner and the outer knobs both on MFD and ReadyPad, also clear the plan and enter a new one, and close the FPL window, then reopen it. At some point, at least for me, the system will get into a state where it does not bring up the window where you can enter the waypoint, but simply flashes it, with the "USS Nimitz" text in it. Currently, the only solution is that the user has to avoid mistakes (which is not possible, as we're humans and simply misplace the mouse cursor sometimes) and better not change the flight plan once it is entered -- changing it may cause the error and make the FMS unusable.

Although this thread is quite old, I want to confirm the problem stated here. For me, this problem happens, when I accidentily press a wrong button (e.g. pressing the outer instead of the inner knob, or pressing a wrong button on the ReadyPad) while going through the waypoint process. Then the page flashes for half a second and disappears. Only reloading the aircraft resets the FMS, but during a flight (where I might change my flight plan) this is not a real option. However, while the page is visible for this small moment, I can see that the aircraft carrier (USS Nimitz) is shown in the page! It would be great if an update of the Corvalis could be released fixing this problem. I want to use the plane for a trip around the world, with many many destinations, and here a stable user interface -- that does not go crazy just because of user's errors -- is important for that.