Reunion 1.1 for p3dv4 crashes

[Aviator_1979]

Does the moderator know where i can find the FSDG scenery configurator for p3dv4, i added the sode entries in the programdata but now i have to disable "docking jetways" in p3d4. i have them for fsx and p3dv3 but not in p3dv4. This all for Reunion.
Thanks you

ps can i manually disable FMEE_Jetways_LIB to FMEE_Jetways_LIB.off (thats how i see it in fsx)

[horst18519]

You should find it in the FSDG folder (in Prepar3D v4 Add-Ons) or via the Windows Start Menu.

[Aviator_1979]

Its not there i searched everywhere, i think because i have fsx-se prepar3dv3 and prepar3dv4 on the same pc. i did it manually now.

[liveopenskies]

Hello,

I have purchased FMEE and P3D v4 crash when i use pmdg 777, i uninstalled FMEE and try to load pmdg 777 and all works fine. I tried a second reinstall for FMEE and CTD is back, when FMEE is installed i cant use pmdg 777 on any airport, got instant crash at load screen.

Need help please, any fix ?

[horst18519]

Did you mean you get an instant CTD when trying to start P3D as soon as you install both the PMDG 777 and FSDG-Reunion? We're not aware of such an incompatibility. If you're sure it's related to the combination of those 2 addons please disable the add-on.xml (rename) in the FSDG-Reunion folder to test if you get to the loading screen. I'm not sure if the B777 also includes some add-on.xml; if so you can try the same with that file.

[liveopenskies]

Did you mean you get an instant CTD when trying to start P3D as soon as you install both the PMDG 777 and FSDG-Reunion? We're not aware of such an incompatibility. If you're sure it's related to the combination of those 2 addons please disable the add-on.xml (rename) in the FSDG-Reunion folder to test if you get to the loading screen. I'm not sure if the B777 also includes some add-on.xml; if so you can try the same with that file.

I have no problem before i install FMEE, all worked fine, since i installed it and when i use pmdg 777 my p3dv4 instant crash when i press OK to load scenario. No problem with default aircraft with FMEE.

FMEE + PMDG 777 = instant crash on all airport
PMDG + FMEE not installed = all works fine
FMEE + default p3d aircraft = works fine

Im in flight actually, will try later.

[horst18519]

I would have to look at your addons.cfg file.

[liveopenskies]

I would have to look at your addons.cfg file.

Where i can find it ? (dont remember the path)

[AFR6752]

I researched this crash and it is caused by a bug in p3d. p3dv4.1 should fix it, a library indexing bug caused by too many scenery addon entries.

[liveopenskies]

I researched this crash and it is caused by a bug in p3d. p3dv4.1 should fix it, a library indexing bug caused by too many scenery addon entries.

So need wait 4.1 to use FMEE ? ...waisted my time...

[AFR6752]

I researched this crash and it is caused by a bug in p3d. p3dv4.1 should fix it, a library indexing bug caused by too many scenery addon entries.

So need wait 4.1 to use FMEE ? ...waisted my time...

A temporary work around might be to only use scenery.cfg entries and not addon.xml files

[horst18519]

For Reunion that is not a solution, but maybe for the 777 or some other addon - I guess there are quite a lot in your list you could disable.

[liveopenskies]

I have no problem with P3D v4 so i dont think its coming from PMDG 777, got 200h flight since i turned to p3d v4 and 0 problem, yesterday purchased and installed FMEE then CTD.

Rename add-on.xml no make p3d CTD but FMEE scenery NOT add in the scenary library, need to do it manually but still remain the same, FMEE default p3d scenery only visible.

[horst18519]

Does it work if you remove some other addons? If the culprit is the total number of entries in the add-on.cfg then removing any other entry should also fix that problem. You can also re-sort the areas in the add-on.cfg. Then it's probably not Reunion but that other last area in the cfg that causes that issue.

[liveopenskies]

Does it work if you remove some other addons? If the culprit is the total number of entries in the add-on.cfg then removing any other entry should also fix that problem. You can also re-sort the areas in the add-on.cfg. Then it's probably not Reunion but that other last area in the cfg that causes that issue.

Why should i remove my other addons as my p3d worked perfectly before installing FMEE ? I dont have many airport sceneries addons install yet, (arround 5-6). I have installed your FIMP and no problem with it, dont know why FMEE bothering my p3d.

[horst18519]

To see if the P3Dv4 bug mentioned above is the reason for your crashes.

I researched this crash and it is caused by a bug in p3d. p3dv4.1 should fix it, a library indexing bug caused by too many scenery addon entries.

How many entries do you have in your add-ons.cfg?

[liveopenskies]

To see if the P3Dv4 bug mentioned above is the reason for your crashes.

I researched this crash and it is caused by a bug in p3d. p3dv4.1 should fix it, a library indexing bug caused by too many scenery addon entries.

How many entries do you have in your add-ons.cfg?

Here my add-ons.cfg

[Package.0]
PATH=C:\Users\Live Open Skies\Documents\Prepar3D v4 Add-ons\FsDreamTeam CYVR
TITLE=FsDreamTeam CYVR
ACTIVE=true
REQUIRED=false
[Package.1]
PATH=C:\Users\Live Open Skies\Documents\Prepar3D v4 Add-ons\FsDreamTeam Addon Manager
TITLE=FsDreamTeam Addon Manager
ACTIVE=true
REQUIRED=false
[Package.2]
PATH=I:\Program Files (x86)\12bPilot\SODE\P3Dv4
TITLE=SODE
ACTIVE=true
REQUIRED=false

[horst18519]

Not the one in ProgramDate/... but from the same folder as the Prepar3Dv4.cfg (AppData/Roaming/...). That is the one that P3D updates whenever you add an addon using an add-on.xml.

[liveopenskies]

Not the one in ProgramDate/... but from the same folder as the Prepar3Dv4.cfg (AppData/Roaming/...). That is the one that P3D updates whenever you add an addon using an add-on.xml.

from : C:\Users\Live Open Skies\AppData\Roaming\Lockheed Martin\Prepar3D v4

[Package.0]
PATH=C:\Users\Live Open Skies\Documents\Prepar3D v4 Add-ons\Flightbeam - KSFOHD
ACTIVE=true
REQUIRED=false
[Package.1]
PATH=C:\Users\Live Open Skies\Documents\Prepar3D v4 Add-ons\FSDG
ACTIVE=true
REQUIRED=false
[Package.2]
PATH=C:\Users\Live Open Skies\Documents\Prepar3D v4 Add-ons\FSDG-Mauritius
ACTIVE=true
REQUIRED=false
[Package.3]
PATH=C:\Users\Live Open Skies\Documents\Prepar3D v4 Add-ons\LatinVFR Miami Int'l KMIA P3dv4
ACTIVE=true
REQUIRED=false

[horst18519]

That is all? There certainly is a reason for an index overflow.
Did you contact PMDG on this?