|
Post by davniyson on Aug 7, 2013 0:39:26 GMT -5
Hi, thanks again for your help. The reason that I wrote a simulator - overspeed. I'll try to test a different plane with event name "Test"
|
|
teson1
Commercial Pilot
Posts: 243
|
Post by teson1 on Aug 7, 2013 17:23:10 GMT -5
Understand. Man- that PA-20 is sensitive to overspeed Crashes seem to have been immediately after exceeding 160 KIAS, at 165-168 kts ... Flights with your new plane go much better ! You're doinga hard day's work of true bush flying. Good job !
|
|
|
Post by kronzky on Aug 8, 2013 10:08:43 GMT -5
Looking at your flight paths, I actually don't see why we shouldn't allow them "in competition". Even with the realism settings unreadable, a crash would still be obvious, and we can also see the fuel consumption and weather situation from the Duenna logs. The only thing that cannot be detected is if you had "close encounters" with the ground, e.g. flying through tree cover. But since that wasn't the case, I think we should fully allow your runs. (Just stay well off the ground, and you should be fine.) If somebody else has concerns about this, feel free to post it here, or contact me via PM.One more thing you could try though, to help out Duenna a bit: - First, find the location for your P3D application data. It will be something like this:
C:\Users\{yourUserName}\AppData\Roaming\Lockheed Martin\Prepar3D where "{yourUserName}" is the user name you use on your computer. (Just click your way through the directories, and it'll be obvious.)
- Then, start up P3D and Duenna.
- In Duenna, click the "Settings" button, and in the field that says "FS9.CFG (when non-std)", enter the path you found, followed by "Prepar3D.CFG. So it'll look similar to this:
C:\Users\{yourUserName}\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG
This is what mine (with the username "Kronzky") looks like:
|
|
|
Post by davniyson on Aug 8, 2013 11:32:04 GMT -5
Okay, I'll try) I want to ask. Does it make sense to fly past months competition?
|
|
|
Post by kronzky on Aug 8, 2013 11:37:05 GMT -5
You can certainly fly them (there are some nice routes in there), but they won't count for points anymore (you only get points within the active month).
|
|
|
Post by davniyson on Aug 8, 2013 12:02:06 GMT -5
I tried what you suggested. It did not help, unfortunately. While I will fly without it. ))
|
|
|
Post by kronzky on Aug 8, 2013 12:15:58 GMT -5
I tried what you suggested. It did not help, unfortunately. While I will fly without it. )) Yes, Duenna will still be red, but there will hopefully be more real information in the log file, if you use the correct CFG path.
|
|
|
Post by kronzky on Aug 10, 2013 23:21:32 GMT -5
Looks like in your last flight, with the correct path defined, Duenna is now able to read the realism settings (even though it complains that CrashDetection is "NOT GOOD", despite it being set to 'True'): Info: Specified Configuration-File: C:\Users\DSN_home\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG Info: REALISM/CrashDetection: 'True' (NOT GOOD) Info: REALISM/StressDamage: 'True' (OK) Info: REALISM/UnlimitedFuel: 'False' (OK) Info: Weather/LoadWeather: '0' (NOT GOOD) Info: REALISM/CrashTolerance: '1.000000' Guess we're getting closer! Update: I've done some further testing today, and it looks like, if the CFG path is correctly pointed to the P3D AppData folder, then Duenna will correctly interpret the settings for crash detection, crash tolerance (even though it always has a "NOT GOOD" comment for the crash detection, no matter what it's set to), stress damage and unlimited fuel. It will also reset the autopilot, if that option is set. Weather will always be yellow, as P3D isn't set up for internal weather downloads, but since that can be verified via the Duenna wind log, that shouldn't be too much of a concern. P3D and Duenna both detect overspeeds, and the plane will crash if the appropriate realism setting has been activated. So it looks like we can definitely go full steam ahead with P3D!
|
|