by Hawk » Thu Feb 23, 2012 12:59 am
Thank you very much tat!
I downloaded the new version (the one you made that works for OS X 10.5–10.7) and enabled the 64-bit option but a few seconds after everything loaded (i could see the cockpit, runway, etc) it crashed. I guess it's my machine, because the previous download (2.6 r314 for OS X 10.6–10.7) was not 64-bit right? Could you please clarify that for me.
Anyway, when I started it again with 64-bit disabled it also crashed as it finished loading, but I just started it once again (with 64-bit disabled) and now I'm playing it since it did not crash again.. that makes me think that maybe it's just a "first-time-run" bug that happens once for each 32-bit and 64-bit version, and I should try 64-bit again since that would be ideal I think.
Also, I've noticed with this new version (in 32-bit) that when I switch to the next view from cockpit view—so to Helicopter view—my FPS goes from 60 to 15 and stays there even when I switch back to cockpit view. I'm guessing it's because of the new 2.6 feature that only loads the parts of the aircraft into memory that are visible. However, in the previous version (2.6 r314 for OS X 10.6–10.7) I could switch to that view and still have 60 FPS. Maybe, though, it's because I'm playing it in 32-bit mode now and the previous version (for OS X 10.6–10.7) was indeed 64-bit(?) and if I tried running it in 64-bit now it might not crash and this performance drop would be gone? I will try it later and update you.
I should mention though that even in the previous version (2.6 r314 for OS X 10.6–10.7) it seemed like when I was cycling through all the views once, one of the other views caused the frame-rate to drop (to around 15fps as well), which doesn't quite make sense if the reason for this is because of the loading of the rest of the aircraft model (and if I didn't just imagine that and the FPS drop was merely a coincidence and caused by something else. I can install r314 again and verify if it is the case and, if it is, which view is sparking the drop in frame-rate, if you want me to.
P.S. Can you or somebody else test if print("test"); in a Nasal script works? I can't see any output anywhere on the screen, in the nasal console, or in the terminal when I launch fgfs manually with ./fgfs.sh from Terminal.app. I need this to do some simple debugging of a script I'm editing. For example in data/gui/dialogs/display.xml at the start of the /PropertyList/nasal/open element. But typing it into the nasal console and clicking Execute doesn't do anything either.
Update: I just tried 64-bit again and it didn't crash this time. I guess it really was a "first-time-run" issue. Then I switched to another view and fps dropped to 15. Then I quit and when I started it again (in 64-bit) and I was able to cycle through all the views and get 60fps on each of them! I made the same experiment with the 32-bit version and the same thing happened. I can get every view @ 60fps! As with the crashing, this must be another "first-time-run" problem.
Update 2: After some more flying (in 120kts winds!) I switched to helicopter view (from cockpit view) and the frame-rate dropped to 15 again. I don't know why it happens sometimes and other times it doesn't. This was in the 64-bit version of FG 2.6 r319.