falcon409
SOH-CM-2022
Here you are!View attachment 13353
London-Melbourne 2014: P3D
- Thread starter MM
- Start date
spokes2112
Charter Member
Falcon,
Thanks for the files. The picture was big enough.
What is still weird is that I just seen your report from the OH-6A flight. Once again it toggled realism on take off. I looked at all the offsets that Duenna accesses in FSUIPC. Not one would have this effect. There is a whole bunch of stuff that Duenna takes care of that is not provided by FSUIPC, such as sim type (EX from report, Flight Simulator: BLANK). Maybe some of the monitoring facilities in FSUIPC are blocked by Duenna or it takes care of it on it's own, maybe by simconnect? (Will test later) One would be the FSUIPC equivalent offset 0830.
Just some tests for anyone wanting to use P3D and have the P3D path setup in Duenna.
1. A weird and undocumented setting that worked in FS02, not FS9/X, but yet in the ESP(10 equivalent)/P3D SDKs is the following.
I noticed this setting in Falcon's prepare3d.cfg listed as (under [Realism]) OnCrashAction=1. There are some comparisons in FSUIPC v3.999 against 4.xxxx which I wont get into but changing this "may" have an affect. With P3D closed, modify the setting with 0 or 2 and then run P3D then finally a Duenna test flight.
2. Another test would be to try each of the above OnCrashAction numbers with Duenna in both the Auto Baton Pick-Up and the Manual Baton Pickup mode.
If willing to test, please use an airplane, a short (uncrashed) flight & use "enable online flight tracking". That way I can look at separate report .txt(s)
If this doesn't get it down pat then we're stuck as is unless Johannes can change the program. The weather type reads will never work as is because the .flt file is in XML. (needs program mod)
Good Luck..
Thanks for the files. The picture was big enough.
What is still weird is that I just seen your report from the OH-6A flight. Once again it toggled realism on take off. I looked at all the offsets that Duenna accesses in FSUIPC. Not one would have this effect. There is a whole bunch of stuff that Duenna takes care of that is not provided by FSUIPC, such as sim type (EX from report, Flight Simulator: BLANK). Maybe some of the monitoring facilities in FSUIPC are blocked by Duenna or it takes care of it on it's own, maybe by simconnect? (Will test later) One would be the FSUIPC equivalent offset 0830. Just some tests for anyone wanting to use P3D and have the P3D path setup in Duenna.
1. A weird and undocumented setting that worked in FS02, not FS9/X, but yet in the ESP(10 equivalent)/P3D SDKs is the following.
I noticed this setting in Falcon's prepare3d.cfg listed as (under [Realism]) OnCrashAction=1. There are some comparisons in FSUIPC v3.999 against 4.xxxx which I wont get into but changing this "may" have an affect. With P3D closed, modify the setting with 0 or 2 and then run P3D then finally a Duenna test flight.
2. Another test would be to try each of the above OnCrashAction numbers with Duenna in both the Auto Baton Pick-Up and the Manual Baton Pickup mode.
If willing to test, please use an airplane, a short (uncrashed) flight & use "enable online flight tracking". That way I can look at separate report .txt(s)
If this doesn't get it down pat then we're stuck as is unless Johannes can change the program. The weather type reads will never work as is because the .flt file is in XML. (needs program mod)
Good Luck..
SkippyBing
Charter Member
I started knocking up a separate programme last night to check P3D settings. Obviously that may not be needed know but I'll still keep working on it in case we need something extra.
As a quick test of what I've done so far, could someone with P3D run the attached file? It should open a DOS window which will tell you where the Prepar3D.cfg file is and what the relevant realism lines read, if you could get a screen grab of that and post it I'd appreciate it.
If that works I can add code to do the check after P3D has started and then monitor the realism settings in game* and if the user crashes via SimConnect. I should also be able to get it to check the nearest airfield's TAF at regular intervals which should at least indicate if the weather is static or not.
*Oddly SimConnect won't inform you if all the realism settings change but it covers if Crash Detection is turned on and if Fuel is unlimited.
https://dl.dropboxusercontent.com/u/84961803/P3D Marshall.zip
As a quick test of what I've done so far, could someone with P3D run the attached file? It should open a DOS window which will tell you where the Prepar3D.cfg file is and what the relevant realism lines read, if you could get a screen grab of that and post it I'd appreciate it.
If that works I can add code to do the check after P3D has started and then monitor the realism settings in game* and if the user crashes via SimConnect. I should also be able to get it to check the nearest airfield's TAF at regular intervals which should at least indicate if the weather is static or not.
*Oddly SimConnect won't inform you if all the realism settings change but it covers if Crash Detection is turned on and if Fuel is unlimited.
https://dl.dropboxusercontent.com/u/84961803/P3D Marshall.zip
falcon409
SOH-CM-2022
Here's the screenshot!
View attachment 13362
View attachment 13362
SkippyBing
Charter Member
Ed,
Thanks for that, it's always nice to see you haven't programmed something that only works on your own machine!
I'll carry on with my current plan in case we need it as a cross check.
Skippy
Thanks for that, it's always nice to see you haven't programmed something that only works on your own machine!
I'll carry on with my current plan in case we need it as a cross check.
Skippy
flyon
Charter Member
I went ahead and updated my P3D with REX Essential+OD tonight, and took a test flight in the Panther to see if this would affect the realism settings. It didn't. It ran and loaded up as it did last night without REX -realism red, and wx yellow- then it goes all green upon takeoff. Upon landing at the destination (which should be a green landing), the Duenna reverts back to the red-yellow wx-realism colors again.
At this time I'm really not sure if the REX is injecting the weather though, I need to do a lot more homework on setting it up properly. The textures do look better though. I will say that the winds seemed a bit more unpredictable, but that's not really a good gauge to go by now.
At least by from what REX showed me in the weather startup screen, they are showing accurate conditions for the areas I looked at, so that's at least a good start there anyways.
Pics from the flight tonight. As I go along in practice, I will post the links as I go, so that you guys can take my txt files and compare notes as Spokes did here earlier today.
That's a good idea, maybe you guys will stumble onto something and get a fix by doing so. Or maybe not. Can't hurt to try though.
I also linked the system txt file, maybe that will help out too, idk.
Also pic'ed here are Ed's and my realism settings, if Ed's are still the same after tonight. There are a few differences.
Maybe try to duplicate my settings and see what happens, it can't hurt at this point, right?
http://fs-duenna.com/flights/ShowFlight.php?detail=flight&value=IbMSvgZHLIMB6TUUQ4kZB3sUhk
View attachment SystemLog.TXT
View attachment FlightLog_22-48-34.TXT
At this time I'm really not sure if the REX is injecting the weather though, I need to do a lot more homework on setting it up properly. The textures do look better though. I will say that the winds seemed a bit more unpredictable, but that's not really a good gauge to go by now.
At least by from what REX showed me in the weather startup screen, they are showing accurate conditions for the areas I looked at, so that's at least a good start there anyways.
Pics from the flight tonight. As I go along in practice, I will post the links as I go, so that you guys can take my txt files and compare notes as Spokes did here earlier today.
That's a good idea, maybe you guys will stumble onto something and get a fix by doing so. Or maybe not. Can't hurt to try though.
I also linked the system txt file, maybe that will help out too, idk.
Also pic'ed here are Ed's and my realism settings, if Ed's are still the same after tonight. There are a few differences.
Maybe try to duplicate my settings and see what happens, it can't hurt at this point, right?
http://fs-duenna.com/flights/ShowFlight.php?detail=flight&value=IbMSvgZHLIMB6TUUQ4kZB3sUhk
View attachment SystemLog.TXT
View attachment FlightLog_22-48-34.TXT
spokes2112
Charter Member
Use the Duenna "Settings" page and use the "FS9.cfg (when non-std)" field to enter in the whole path to "prepare3d.cfg".
Locations -
Prepar3D v1: %APPDATA%\Lockheed Martin\Prepar3D\prepare3d.cfg
Prepar3D v2: %APPDATA%\Lockheed Martin\Prepar3D v2\prepare3d.cfg
%APPDATA% is usually something similar to - C:\Users\USER NAME\AppData\Roaming
Save settings then restart Duenna.
_______________________________________________________________________________________
By using the above you will get a green realism (Forget the WX yellow/red, will never work at this time) at baton / start up. During the Duenna run the text file will throw an error but also at the same time show it as being ok. On baton release Duenna will still throw an invalid flight.
1st example, P3D without the path entered. Notice it is looking for FS2002.cfg and thinks it is running FS2002.
Errors:
16.10.2014 01:35:43z ERROR: FS9.CFG is not readable: Can't open 'H:\Lockheed Martin\Prepar 3D v2\FS2002.CFG' for reading: 53 - File not found
16.10.2014 01:35:43z AT S 36* 03.9' / E 146* 58.0' at 543ft (YMAY/0.8nm) GS:65kts, IAS:73kts, VS:1ft/min
16.10.2014 01:35:43z STATE
16.10.2014 01:35:43z AIRCRAFT Navajo Black Gold Panther (Colemill) / Counter 2
16.10.2014 01:35:43z
16.10.2014 01:35:43z ERROR: Realism-Settings are not valid!
16.10.2014 01:35:43z AT S 36* 03.9' / E 146* 58.0' at 543ft (YMAY/0.8nm) GS:65kts, IAS:73kts, VS:1ft/min
16.10.2014 01:35:43z STATE
16.10.2014 01:35:43z AIRCRAFT Navajo Black Gold Panther (Colemill) / Counter 2
16.10.2014 01:35:43z
Info: Looks like FS2002
Info: Configuration-File: H:\Lockheed Martin\Prepar 3D v2\FS2002.CFG
Info: REALISM/CrashDetection: '0' (NOT GOOD)
Info: REALISM/StressDamage: '' (NOT GOOD)
Info: REALISM/UnlimitedFuel: '' (NOT GOOD)
Info: Weather/LoadWeather: '0' (NOT GOOD) <---- DISREGARD BECAUSE IT WILL NEVER WORK UNLESS DUENNA IS MODDED.
Info: REALISM/CrashTolerance: '0'
Example 2, P3D with the path entered. Notice it is a whole bunch better.
Errors:
15.10.2014 17:26:19z ERROR: Realism-Settings are not valid!
15.10.2014 17:26:19z AT N 33* 42.8' / W 96* 40.0' at 759ft GS:2kts, IAS:1kts, VS:165ft/min
15.10.2014 17:26:19z STATE
15.10.2014 17:26:19z AIRCRAFT Bell47G FSX NO DOORS / Counter 1
15.10.2014 17:26:19z
Info: Specified Configuration-File: C:\Users\falcon409\AppData\Roaming\Lockheed Martin\Prepar3D v2\prepar3D.cfg
Info: REALISM/CrashDetection: 'True' (NOT GOOD)
Info: REALISM/StressDamage: 'True' (OK)
Info: REALISM/UnlimitedFuel: 'False' (OK)
Info: Weather/LoadWeather: '0' (NOT GOOD) <---- DISREGARD BECAUSE IT WILL NEVER WORK UNLESS DUENNA IS MODDED.
Info: REALISM/CrashTolerance: '1.000000'
_______________________________________________________________________________________
On a programming note I believe Duenna is using an internal hook to get a "running account" of crash detection. I monitored all FSUIPC reads and writes from Duenna (during a full flight) and in no case (FS9 or FSX) did it use offsets 0830, 0832, & 0833. It does not access SimConnect. This hook it seems is reading the wrong data as Duenna reads the value as if being on/off ground. It triggers - ERROR: Realism-Settings are not valid & (NOT GOOD) on takeoff, while when the baton is first picked up it reads the .cfg file and gives REALISM/CrashDetection: 'True'. For an easy "Marshaller" all one needs to do is monitor FSUIPC offset 0832 (1 byte Crash detection: 1=Crash detection is on, 0 = off ) if it changes from 1 to zero, timestamp it and report it as invalid. 0832 was tested in FS9 & FSX. According to the FSUIPC4 offsets status document it is mapped but needs confirmation for P3D.
_______________________________________________________________________________________
Could someone do another test please? Use the configuration path trick (above) and then turn all the realism settings to the opposite of what's needed?
Crash Detection = OFF
Stress Causes Crash = OFF
Crash Tolerance Slider = Full Left
General Flight Model = Full Left
Unlimited Fuel = ON
Restart P3D then do a complete, short Duenna flight. Of course it will be invalid LOL! And post the text file. The reason for this is that it is known that with the path trick it is picking things up IF they are correct. Next is to find out if it picks up all requirements if they are incorrect. Just in case Duenna is looking at something other than what it should. Thanks in advanced.
Last edited:
srgalahad
Charter Member 2022
Something to ponder while testing. Duenna can throw a fit with helicopters when using the auto-arm function depending on a set of conditions - Auto-arm threshold is (I think) 45/50kts and "airborne" is > +5 ft so if one lifts off before 50kts airspeed is reached, it senses that you somehow started while airborne and throws an error (Team SOH had a problem with a leg this way in FS9 a few years ago). Very slow aircraft like the Cub can have the same issue. Better to use something a bit more 'traditional' like a C182.
Some users have reported getting away with it in helicopters while others get the error (wind? rate of climb?).
Of course if you manually start Duenna before moving in a heli. there are no errors (or should not be)
Some users have reported getting away with it in helicopters while others get the error (wind? rate of climb?).
Of course if you manually start Duenna before moving in a heli. there are no errors (or should not be)
flyon
Charter Member
10-4 on the helos...and why I tried to use a default P3D plane this time around (see next post).
The same 'no helis' theory also applies to the previously mentioned FSFS.
Like any military planes, helis won't work in FS Flying School either. The program will run, but it functions poorly overall when using them -but that's another topic...
When I was on a heli kick a while back, I used the ND EC 135 and the FSX default Agusta Westland EH 101 with Duenna before. It worked OK.
No hiccups whatsoever. A slight exception to the rule.
(Or, better yet, maybe I just got lucky -guess I should have played either the Powerball or MegaMillions lotteries that day...lol)
Or perhaps myself and my pc falls into the users "getting away with it in helicopters" category? Don't know this lately, as I'm off the helos nowadays.
flyon
Charter Member
My bad for missing the 2002 thing. Sorry 'bout that.
Got my REX for P3D figured out tonight, so I went ahead and ran the test you requested with a short flight in the P3D default Carenado A36 Bonanza, from KPIT Pittsburgh Intl., to KAGC Allegheny County Airport.
Went through all of that -then found out I didn't have the "FS9.cfg (when non-std)" set correct AFTER I did that flight. Smooth move of the day candidate I was there...
Reset, with the same plane (different paint...lol), but at CYTZ to CYYZ. Now with the correct FS9.cfg (when non-std) path:
Everything went as expected, and I believe the Duenna has run on previous P3D flights recently the same exact way.
Pics of what I seen, my adjusted realism settings pic, and the validation flt, system txt files of this last CYTZ to CYYZ flight tonight:
For now, I'll go and reset my settings back to crash detect, etc., unless you want me to try out some other settings.
I get it that it probably won't change things, nonetheless I'll keep plugging away at it. Might, or might not luck into something doing so -never know until you try.
View attachment FlightLog_20-16-17.TXT
View attachment SystemLog.TXT
http://fs-duenna.com/flights/ShowFlight.php?detail=flight&value=mGCEURjPaKp0l9r66OWN2uVWkNM
spokes2112
Charter Member
Great! Thanks everyone!
1st. I am sorry for not calling y'all by name. It's been a while since the last voice/RTWR committee discussion. So forgive me by using your "callsign".
2nd. When testing please use an aeroplane. SRGALAHAD's post here describes exactly why using a different type of "air" vehicle may throw off testing.
FLYON - Thanks for the test, unfortunately you did not provide the correct path to "prepar3D.cfg" ( A PM has been sent by "MM" ) so the test is void. One thing to consider as you have mentioned & I have noticed too. Even when you start duenna with some red/yellow boxes they will show all green once you take-off. The reason is on purpose.
Just to reiterate the paths are: Simpler, a Win7 OS example, use Windows Explorer if different OS. Use Windows Explorer regardless, to confirm the path to "prepare3d.cfg"
ED (falcon409) - Again, Thanks for the test! If you're up to it would one more test be too much?
Get everything up to Duenna standards EXCEPT for "Stress causes damage" (Unchecked) . Use a nice little aeroplane like the Christen Eagle again and do a quick flight from T/O to landing (not crashed). Remember to restart P3D after making the changes. Everything turned out as expected
from your previous test except for "Stress causes damage". So this should be the last test by isolating only that setting. The following are the settings required.
Crash Detection = ON
Stress Causes Crash = OFF
Crash Tolerance Slider = Full Right
General Flight Model = Full Right
Unlimited Fuel = Off
Just a little inside. I hope you all do not mind me hijacking this topic. I am a fixing, finding out how things work type of person. One of my hobbies is FS as there is a whole bunch that could be done in any aspect. Many others have proved that on their own behalf. I do not have P3D v2 because my little "mouse wheel powered" computer cannot handle it. ( I did have P3D v1 for a 2 month stint ) In any case I try to keep up what's new by looking at the newest SDKs from Lockheed Martin & follow the FSUIPC forum religiously. My hope is, at least for the mean time, keep Duenna as our primary tracking program. And hopefully Johannes, once contacted, may use some of this testing as a reference to update his wonderful program.
1st. I am sorry for not calling y'all by name. It's been a while since the last voice/RTWR committee discussion. So forgive me by using your "callsign".
2nd. When testing please use an aeroplane. SRGALAHAD's post here describes exactly why using a different type of "air" vehicle may throw off testing.
FLYON - Thanks for the test, unfortunately you did not provide the correct path to "prepar3D.cfg" ( A PM has been sent by "MM" ) so the test is void. One thing to consider as you have mentioned & I have noticed too. Even when you start duenna with some red/yellow boxes they will show all green once you take-off. The reason is on purpose.
Just to reiterate the paths are: Simpler, a Win7 OS example, use Windows Explorer if different OS. Use Windows Explorer regardless, to confirm the path to "prepare3d.cfg"
Code:
Prepar3D v1 = C:\Users\[COLOR=#FF0000]USER NAME[/COLOR]\AppData\Roaming\Lockheed Martin\Prepar3D\prepare3d.cfg
Prepar3D v2 = C:\Users\[COLOR=#FF0000]USER NAME[/COLOR]\AppData\Roaming\Lockheed Martin\Prepar3D v2\prepare3d.cfgED (falcon409) - Again, Thanks for the test! If you're up to it would one more test be too much?
Get everything up to Duenna standards EXCEPT for "Stress causes damage" (Unchecked) . Use a nice little aeroplane like the Christen Eagle again and do a quick flight from T/O to landing (not crashed). Remember to restart P3D after making the changes. Everything turned out as expected
from your previous test except for "Stress causes damage". So this should be the last test by isolating only that setting. The following are the settings required.Crash Detection = ON
Stress Causes Crash = OFF
Crash Tolerance Slider = Full Right
General Flight Model = Full Right
Unlimited Fuel = Off
Just a little inside. I hope you all do not mind me hijacking this topic. I am a fixing, finding out how things work type of person. One of my hobbies is FS as there is a whole bunch that could be done in any aspect. Many others have proved that on their own behalf. I do not have P3D v2 because my little "mouse wheel powered" computer cannot handle it. ( I did have P3D v1 for a 2 month stint ) In any case I try to keep up what's new by looking at the newest SDKs from Lockheed Martin & follow the FSUIPC forum religiously. My hope is, at least for the mean time, keep Duenna as our primary tracking program. And hopefully Johannes, once contacted, may use some of this testing as a reference to update his wonderful program.
spokes2112
Charter Member
Ed,
If you're around and have the time can you hook up on SOH Teamspeak? I'm on now.
Roman
17OCT14 1430 UTC
If you're around and have the time can you hook up on SOH Teamspeak? I'm on now.
Roman
17OCT14 1430 UTC
falcon409
SOH-CM-2022
Noticed something when I was looking over the info on the map. The airport designator they show is F39. . .I'd never seen that before so I went checking. Apparently that's the FAA designator. . .ok! The ICAO code is KGYI which is North Texas Regional Airport. There was a name change in 2008 from Grayson County to the current North Texas. I've made that name change for the scenery I'm doing and even added a control tower Freq. as the default AFCAD only has Unicom. Just a HU in the midst of all these numbers flying around, lol.
flyon
Charter Member
No worries about names or screen names on my end. You can all me anything you want, just dont call me late for dinner...lol
Yet another clerical error on my part. Sorry, I'll get it right next time around. Probably later tonight.
spokes2112
Charter Member
Ed,
Noticed that too when tracking you on google earth. Duenna's built in airport database is old (FS9) - No worries, we know where you are! LOL - THanks a bunch for the testing today.
Mike, if you are online I am up on the SOH TS & Avsims TS which ever you prefer. Will be up until about 10:30 central / 11:30 your time. Geepers ! just missed you again.
Noticed that too when tracking you on google earth. Duenna's built in airport database is old (FS9) - No worries, we know where you are! LOL - THanks a bunch for the testing today.
Mike, if you are online I am up on the SOH TS & Avsims TS which ever you prefer. Will be up until about 10:30 central / 11:30 your time. Geepers ! just missed you again.
SkippyBing
Charter Member
Not sure if it's still needed but I've made some modifications to my program.
It now dumps the P3D settings to a txt file on completion of the flight, along with any instances when the crash detections was turned off, the fuel was set to unlimited, or you crashed. Additionally it logs the flight, every second below 2000' AGL and every 10 minutes above, and checks the nearest weather report every 30 minutes which should indicate if the weather is dynamic although you can't guarantee the source.
It needs to be started after you start P3D, but before you enter the flight itself. If you forget reloading the aircraft should start it logging, text will appear in the DOS window. It will create the final text file once you exit P3D, in the same place you have the program itself, so possibly easiest to extract it to the desktop.
If someone could test and upload the flight log that'd be useful to see if it actually works for anyone else. Try changing the realism settings etc. as well.
The one problem so far is it tends to hand when it's finished rather than exiting cleanly, but that doesn't seem to affect the actual output.
View attachment P3D Marshall.zip
View attachment 15-19-46z - Prepar3D Flight Log.txt
It now dumps the P3D settings to a txt file on completion of the flight, along with any instances when the crash detections was turned off, the fuel was set to unlimited, or you crashed. Additionally it logs the flight, every second below 2000' AGL and every 10 minutes above, and checks the nearest weather report every 30 minutes which should indicate if the weather is dynamic although you can't guarantee the source.
It needs to be started after you start P3D, but before you enter the flight itself. If you forget reloading the aircraft should start it logging, text will appear in the DOS window. It will create the final text file once you exit P3D, in the same place you have the program itself, so possibly easiest to extract it to the desktop.
If someone could test and upload the flight log that'd be useful to see if it actually works for anyone else. Try changing the realism settings etc. as well.
The one problem so far is it tends to hand when it's finished rather than exiting cleanly, but that doesn't seem to affect the actual output.
View attachment P3D Marshall.zip
View attachment 15-19-46z - Prepar3D Flight Log.txt
spokes2112
Charter Member
SkippyBing,
Absolutely BRILLIANT! One thing that would be nice, especially for upcoming RTW races. Could you include FSX connections (SP2/Accell) & P3Dv1 too? The reason is that who knows if the Jeppesen servers will ever go belly up, many, including myself, feel it's inevitable . The racers would have to revert to an external program for WX and this would validate the WX with better precision than just seeing if the wind has changed via the duenna tracking. One other thing, following a slew toggle might be a good thing to follow as Duenna will invalidate the flight after one. No need to keep logging right?
Sorry, no other input, no P3D.
Roman
Absolutely BRILLIANT! One thing that would be nice, especially for upcoming RTW races. Could you include FSX connections (SP2/Accell) & P3Dv1 too? The reason is that who knows if the Jeppesen servers will ever go belly up, many, including myself, feel it's inevitable . The racers would have to revert to an external program for WX and this would validate the WX with better precision than just seeing if the wind has changed via the duenna tracking. One other thing, following a slew toggle might be a good thing to follow as Duenna will invalidate the flight after one. No need to keep logging right?
Sorry, no other input, no P3D.
Roman