01-03-2016, 04:24 PM
Dan - thanks for your patience with this one (it's driving me mad, LOL!).
Well ... this is *very* odd! I checked my P3D setting: it had been switched to "enable" (collision detection). Is it possible that my original settings in more_option.cfg switched it?
When I edited the cfg file, I checked the P3D setting - and it was as it should be ("disabled"). However - I had a few FSP resets/crashes (due to some weirdness with my A2A C182 - and it looks like somehow that re-enabled the setting. Most odd.
So ... it really does look like this has been resolved (YAY!).
The moral of the story is make sure you check the P3D setting AGAIN (as Sam said) *after any changes to the more_option.cfg* (!!)
Adam.
Well ... this is *very* odd! I checked my P3D setting: it had been switched to "enable" (collision detection). Is it possible that my original settings in more_option.cfg switched it?
When I edited the cfg file, I checked the P3D setting - and it was as it should be ("disabled"). However - I had a few FSP resets/crashes (due to some weirdness with my A2A C182 - and it looks like somehow that re-enabled the setting. Most odd.
So ... it really does look like this has been resolved (YAY!).
The moral of the story is make sure you check the P3D setting AGAIN (as Sam said) *after any changes to the more_option.cfg* (!!)
Adam.
![[-]](http://www.fspassengers.com/forum/images/collapse.png)