Patch is out

Just curious; is the click zones lock up issue solved when saving a flight?
When adding FSX scenery, are the taxiways and aprons visible now?
Are the lights on FSX aircraft still buggy, eg. not showing?


Best regards
Dag
 
Lionheart said:
All of my aircraft that have XML based MFD screens that use the FS9 GPS gauge technology are now non-functioning in V2.1. 5 Planes down that no longer work in P3D V2.x.


sigh.....
Click to expand...

What's a GPS ? Just kidding Bill . Just had the Piper Pacer up and noticed that . Hay , it still flies like the old classic always has . We'll just have to rough it with the ADF I guess . My kind of flying anyway .:encouragement:

Rich
 
Dino Cattaneo said:
There seem to be changes to the XML parsing rules - specifically, some of my gauges which had minor "mistakes" were still working perfectly in P3dV2 and FSX - but do not work anymore in P3dV2.1.
Click to expand...
Dino, that's the conclusion I have come to as well. Since the "default GPS" (fs9gps.cab) hasn't changed one iota, and all of my "custom" units are based on that same XML script, there is quite likely one or more truly insignificant XML syntax errors (some character missing, or some such) that's stopping the script's evaluation.

What I'll probably wind up doing is redoing the entire XML script from scratch with gobs of testing in situ as I work...

...I just wish there was a way to run XML through a "debug session" like I can with C++ code! :banghead:
 
Bill,

In my case I spotted a couple of lines that were working perfectly in FSX and P3Dv2.0 but did not work in 2.1... reason was just an extra space in the line.

I am sure you know that, but, just in case, keep in mind that adding the following lines to FSX.cfg (or the Prepar3d equivalent) provides a (incomplete and somewht ambiguos) debugger....

[PANELS]
...
GaugeDevDebug=1
 
Something is very wrong. Anyone else experiencing the Right click of mouse bug?? Every time i click my Right mouse key no matter the aircraft the screen reduces and CTD no reason given??
 
CG_1976 said:
Something is very wrong. Anyone else experiencing the Right click of mouse bug?? Every time i click my Right mouse key no matter the aircraft the screen reduces and CTD no reason given??
Click to expand...

When does this happen ? In VC mode, outside view? On my system the right-click always produces the according context menu.

I updated my V2 installation two days ago in the dirty way (just slap it over V2) and had no issues at all. But it was not very altered from the original configuration and had only 2 sceneries installed, Solomons and Tom's Marianas.
The Saitek throttle, trim wheel and Simped rudder work perfectly now, that's new, expecially the trim wheel needed FSUIPC.
After a basic check I saw that many bugs I saw in V2 are gone. The only issue I see are some flickering textures on 2-sided scenery objects (e.g. trees) or sometimes ground poly textures. But that could be a graphic driver issue.
Performance is good, locked at 30 and usually stays there.

I'll check some of the more demanding aircraft now, with custom XML gauges and so forth.

So far I'm quite pleased, I love the lighting effects.


Cheers,
Mark
 
Dino Cattaneo said:
In my case I spotted a couple of lines that were working perfectly in FSX and P3Dv2.0 but did not work in 2.1... reason was just an extra space in the line.
Click to expand...
Thanks for the information, Dino. Evidently they tightened up the parsing syntax rules and didn't bother to tell anyone. That seems like shooting themselves in the foot though, because all of the now "broken gauges" in their product makes them look really bad.

Thanks too for the reminder about the 'debug line' in the .CFG file. I remember adding that in the FSX.cfg years and years ago, but frankly had forgotten about it... :very_drunk:
 
Mark i got it to work finally. I did something in my controller XML and app data area and forgot backup lol. It's all fixed up now and right clickable:biggrin-new:. Now to off to check out the Carenado damage parade lol. Which I heard the 208EX and 850 TBM.
 
Dino Cattaneo said:
I am sure you know that, but, just in case, keep in mind that adding the following lines to FSX.cfg (or the Prepar3d equivalent) provides a (incomplete and somewht ambiguos) debugger....

[PANELS]
...
GaugeDevDebug=1
Click to expand...
Dino, in P3D you can also add this line in the Prepar3D.CFG file to create a .txt file listing all of the errors:
Code: 
[MAIN]
ContentErrorLogging = 1
After unloading the aircraft, a file will be saved here:
x:\Users\UserName\Documents\Prepar3D v2 Files\ObjectLoadErrors.txt
 
n4gix said:
Dino, in P3D you can also add this line in the Prepar3D.CFG file to create a .txt file listing all of the errors:
Code: 
[MAIN]
ContentErrorLogging = 1
After unloading the aircraft, a file will be saved here:
x:\Users\UserName\Documents\Prepar3D v2 Files\ObjectLoadErrors.txt
Click to expand...


Thanks for that, Bill.
 
I tried to load back V2.0. Uninstalled 2.1, (had to in order to run the installer for 2.0), then ran the 2.0 installer, back to the same folder, and the MFD gauges are still inoperative.

Something else must have loaded that is separate from the sim that is the new parser for XML. Any idea's?




Bill
 
It is strange Lionheart as P3DV1.4 is unaffected. So something between 2.0 and 2.1 is the theory?
 
new install 2.1

Hey guys reporting in just did a full install 2.1 cleaned 2.0 and all reg entries and sim connect off before I did the install.
no problems so far
AI is not changing skins
MFDs all working no xml problems in the Lionheart moonys or Dino Cattaneo's f-35
no right click crashes
will report back more.

nothing is installed not even fsupic
no other versions of fsx or p3d are installed.
 
This just posted by Beau, team member at P3D;


Models missions and gauges all use the same scrip evaluator. We added some script validation code to help with scripted actions in mission creation, but it appears that the error messages are being logged internally even when content error reporting and gauge debugging options are not enabled in the cfg. There may have been one or two new checks added as well, but we haven't gone through it with a fine tooth comb just yet. If the xml validates, but some scripts have errors, the system can get in a state where the same error string is created and logged over and over again eventually leading to OOMs. I would suggest turning on gauge debugging in the Prepar3D.cfg and either fix the errors or avoid using any content that pop up alerts until the next patch. We're sorry about the legacy content effected by this. A silver lining may be that add-on developers might be motivated to go back and clean up scrip errors.

Beau Hollis
Rendering System Lead - Prepar3D® Team
Click to expand...


So it looks like we will need to modify our planes to work with V2.1. The changes in code will cause errors (we can no longer use certain symbols) and there is no leeway for code errors in script.

This is odd as my gauges either work or don't in the past. I run my ModelDef file through browsers and they can find a single error, one space is missing and the entire file crashes.


sigh.....
 
CG_1976 said:
It is strange Lionheart as P3DV1.4 is unaffected. So something between 2.0 and 2.1 is the theory?
Click to expand...

Yes. They have a new 'scrip evaluator'.

There are many OOM's occurring now. Many people are getting crashes like crazy. The sim is not running over 10 min's without an OOM. (This might be with heavy scenery and settings, but this is what tons of people are reporting over at P3D forums). SO they are now saying that errors in scripts are causing error overflow stacks via XML coding errors in planes, etc.

Note that this wasn't happening in 1.4 and wasn't so bad in 2.0.
 
n4gix said:
Dino, in P3D you can also add this line in the Prepar3D.CFG file to create a .txt file listing all of the errors:
Code: 
[MAIN]
ContentErrorLogging = 1
After unloading the aircraft, a file will be saved here:
x:\Users\UserName\Documents\Prepar3D v2 Files\ObjectLoadErrors.txt
Click to expand...

Its funny. I loaded this into V2.0 thinking it would produce the 'errors' list on one of my planes that do not work in V2.1 and there are no errors except missing Mission Metadata. (Default flight, loaded my own plane up into it). No other errors. But again, this is V2.0. I had reverted my installation back. I have the previous version parser.




Bill
 
Well that's not terribly surprising, Bill. After all, the change in the parser was made for the v2.1 release. I see no point whatever in not keeping v2.1 installed so I can clean up the errors in my scripts.

Even though those same "errors" didn't visibly cause problems in v1.4, v2.0 or even in FSX, they may well have simply been being "masked" by the way VAS usage wasn't as critical as it is with v2.1... :ernaehrung004:
 
You must log in or register to reply here.
Back
Top