Me again. Two points, 1: The Realism box goes red even though the relevant boxes have been ticked. Anyway I did my flight. I went to check them afterwards, all OK. When I restarted Duenna Realism box was green!
Maybe this helps:
With FSX and P3D, duenna only has access to configuration values from the previous flight. Weird, but true. So it's best to make one flight with the sim configured correctly (realism, weather, etc.), so that when the race starts, the thing will read these settings correctly.
I did notice that there was another error reported in the text file, that duenna could not access the sim's configuration file. Not sure what that's about, but if you're getting "green duennas" I wouldn't worry about it. Everything else looks ok.
MB: GIGABYTE GA-X299 UD4 PRO ATX
CPU: Intel(R) Core™ Processor i9-10900X Ten-Core 3.7GHz
MEM: 64GB (8GBx8) DDR4/3000MHz Quad Channel
GPU: RTX 3080 Ti 12GB GDDR6
OS: Win 10 Pro 64bit
HP Reverb G2
Ron,
It looks like at the time of duenna starting up something had blocked access to your FSX.cfg. The blocking and the red boxes, because the cfg couldn't be read, happened all at the same time. Why? Absolutely no clue.
One other problem you may have had is a loss of internet connection too. Notice where you ended up in this upper google map. Lat 0 Lon 0 - Not a big deal as the the duenna output showed correctly.Code:Errors: 12.08.2015 22:22:34z ERROR: FS9.CFG/FSX.CFG/Prepar3d.cfg is not readable: Can't open 'C:\Users\Ron\AppData\Roaming\Microsoft\FSX' for reading: 76 - Access to the path 'C:\Users\Ron\AppData\Roaming\Microsoft\FSX' is denied. 12.08.2015 22:22:34z AT S008* 42.4' / E160* 40.9' at 34ft (AGGA/0.2nm) GS:5.086130101291kts, IAS:2.921875kts, VS:0ft/min 12.08.2015 22:22:34z STATE 12.08.2015 22:22:34z AIRCRAFT P-51D 'Bad Angel' / Counter 2 12.08.2015 22:22:34z 12.08.2015 22:22:34z ERROR: Realism-Settings are not valid! 12.08.2015 22:22:34z AT S008* 42.4' / E160* 40.9' at 34ft (AGGA/0.2nm) GS:5.086130101291kts, IAS:2.921875kts, VS:0ft/min 12.08.2015 22:22:34z STATE 12.08.2015 22:22:34z AIRCRAFT P-51D 'Bad Angel' / Counter 2 12.08.2015 22:22:35z
Thanks gents. Regarding the access to the fsx.cfg aspect, I did enter the path to it in the box but I don't recall doing it in a previous installation of Duenna. Is it obligatory?
EDIT: I've just noticed that there is a new file next to the .cfg. FSX.cfg.tmp. I'm guessing that Duenna makes a copy then reads from that. That would explain much.
Unless you're using P3D, the latest duenna version from Johannes Mueller is perfectly up to the task, and may be something worth considering.
http://johannesmueller.com/fs/web/duenna/
MB: GIGABYTE GA-X299 UD4 PRO ATX
CPU: Intel(R) Core™ Processor i9-10900X Ten-Core 3.7GHz
MEM: 64GB (8GBx8) DDR4/3000MHz Quad Channel
GPU: RTX 3080 Ti 12GB GDDR6
OS: Win 10 Pro 64bit
HP Reverb G2
Excellent! All that's left is to light the tires and kick the fires...
MB: GIGABYTE GA-X299 UD4 PRO ATX
CPU: Intel(R) Core™ Processor i9-10900X Ten-Core 3.7GHz
MEM: 64GB (8GBx8) DDR4/3000MHz Quad Channel
GPU: RTX 3080 Ti 12GB GDDR6
OS: Win 10 Pro 64bit
HP Reverb G2
One last thing.(Promise) In the rules about realism Unlimited fuel=Unchecked Crash detection=enabled Realism sliders=Full right and Aircraft stress causes damage=enabled. Nowhere is collision with aircraft mentioned (that I could see) I don't have that enabled and get a green Duenna realism box. Am I good to go?
MB: GIGABYTE GA-X299 UD4 PRO ATX
CPU: Intel(R) Core™ Processor i9-10900X Ten-Core 3.7GHz
MEM: 64GB (8GBx8) DDR4/3000MHz Quad Channel
GPU: RTX 3080 Ti 12GB GDDR6
OS: Win 10 Pro 64bit
HP Reverb G2
Bookmarks