P3D v3 Closes to Desktop with no warning after V4

[Angelo Cosma 61]

Hey guys, I have changed nothing to my P3D V3 install, since installing V4. Now after adding a couple sceneries to V4 FSDT, V3 Will just close to desktop with no warning or error. Not sure why or what to check. Rebooted PC and tried from a clean boot, AV off, default plane. Still closes, scratching my head. 

[penta_a 429]

maybe it's just expressing its jealousy of the new sim ;-)

 

[Griphos 138]

Are the FSDT installers for v4?  If they are for v3 and you redirected them, that could be your problem.  The installers may have changed things in v3.4 also. 

[Angelo Cosma 61]

I should mention I can see fsdt KLAX load for example right to the point where say AI would populate and then ita gone. This happens at default airports as well. 

I changed absolutely nothing and was working fine prior to v4.

[Griphos 138]

Again, you didn't answer my question.  I suspect that if you just tried to install FSDT into v4 without dedicated v4 installers, then they made changes to configs in v3 as well, and this would bugger your sim and produce the kind of crash you're describing.  

[Angelo Cosma 61]

I used whatever installers were available yesterday.

[Griphos 138]

Well, I think you need to find out what version the installers were for. You don't seem that interested in the details for someone asking for help.  Not sure how you expect help from others without detailed information. 

Obviously the problem is very likely caused by that install, as that is the only thing you say you changes on your system. You might try using Windows uninstall to see if that process might reverse any config edits. Otherwise, you'll have to dig into the configs themselves and look for problems. 

I don't have any FSDT stuff, so can't help with what to look for. 

[odourboy 1,289]

I suspect this is your issue:

 

[Angelo Cosma 61]

4 hours ago, Griphos said:

Well, I think you need to find out what version the installers were for. You don't seem that interested in the details for someone asking for help.  Not sure how you expect help from others without detailed information. 

Obviously the problem is very likely caused by that install, as that is the only thing you say you changes on your system. You might try using Windows uninstall to see if that process might reverse any config edits. Otherwise, you'll have to dig into the configs themselves and look for problems. 

I don't have any FSDT stuff, so can't help with what to look for. 

3 hours ago, odourboy said:

I suspect this is your issue:

 

Isn't that geared toward V4 configs only?

 

4 hours ago, Griphos said:

Well, I think you need to find out what version the installers were for. You don't seem that interested in the details for someone asking for help.  Not sure how you expect help from others without detailed information. 

Obviously the problem is very likely caused by that install, as that is the only thing you say you changes on your system. You might try using Windows uninstall to see if that process might reverse any config edits. Otherwise, you'll have to dig into the configs themselves and look for problems. 

I don't have any FSDT stuff, so can't help with what to look for. 

Sorry for the vaguery. The installers are the most current version as it gives you the option to install into V3 or V4. Since my V3 already had said scenery I just ticked v4. 

It is my assumption that that is what caused the issue since that is really the only other thing I did other than installing v4 itself.

[odourboy 1,289]

Quote

Isn't that geared toward V4 configs only?

I actually mis-read your OP regarding problem, but given that the V3 versus V4 encoding of .cfg files is different, maybe you contaminated yourV3 scenery.cfg or something when you ran the V4 FSDT installer?