Jump to content

Sign in to follow this  
Aviators

Prepar3D v2.5 Development Update

Recommended Posts

Guest tymk

 

 


It does appear LM are moving configuration items around (SimObject for example now has it's own .cfg and isn't part of the Prepar3d.cfg, effects folder shaderHSLS.cfg and more) and making for a more modular future where they can update independently of 3rd party ... however, it's a two way street, 3rd party will have build their products to be less version dependent also ... but this seems to be the direction LM are moving and it'll benefit 3rd party also but they will need to make some adjustments.

 

Has this caused any issues with third-party product installation during your testing? In other words, will updated versions of any of the major add-ons be required for re-installation in 2.5?

 

Tym

Share this post


Link to post

What puzzles me is why the ATC window was released as opaque in the first place. It was transparent in FSX, so why change it? Or has the ATC window in ESP always been opaque?

 

They said something about the transparent ATC window not being compatible with Windows XP, and that it would not be a problem with Vista and 7. Since 2.x is not compatible with XP anyway, I have no idea why they're not bringing it back.

 

EDIT: Complete explanation: http://www.prepar3d.com/forum-5/topic/transparent-atc-window/#post-28022

Share this post


Link to post

 

 


I assume you mean SimObjects shadows?  I'm not seeing that problem in any of my aircraft with SimObjects cast/receive unchecked I still see VC shadows.  Is there a specific aircraft this is happening with?

 

 

Hello Rob,

 

thanks for the response.

 

Have a look here:

http://forum.avsim.net/topic/454659-lost-my-cockpit-shadows/

 

 

 

I have only cockpit shadows, when I set "object shadows" (the slider) at least at the lowest stage,

This is with all addons, standard and 3rd party and for 100% reproduceable

 

When I set the "object shadows" slider to zero, the VC shadows are gone.

Share this post


Link to post
Guest

 

 


In other words, will updated versions of any of the major add-ons be required for re-installation in 2.5?

 

Any 3rd party product that ties themselves to P3D versions will need to be updated (same as before) ... Orbx Object Flow, FSUIPC, maybe Virtuali (haven't enabled that yet).  Not all product are tied to versions, you'll have to check with the vendor.

 

As far as ATC window transparency ... by accident when I was using one of my A2A products, setting their configuration window transparency also affects the transparency of the ATC window -- probably not intended.  Now I have not tested this in a while (many versions ago 2.1 I think) so I don't know if that still operates this way.  But if we're getting down to requests for ATC window transparency, then I'd consider that good progress.

 

 


Has this caused any issues with third-party product installation during your testing?

 

I only have one product where SimObject.cfg will be an issue and it's not a product designed for P3D ... Ultimate Traffic 2 requires a SimObjects entry in the Prepar3d.cfg ... on a re-install, this will have to be put in the SimObject.cfg.  So any existing product adding SimObject entries will need to be adjusted.  There are also other developer related changes that I need to explore and see how they are impacted and/or if they are impacted, specifically Windows permissions.

 

 

 


If I am not mistaken, I read somewhere it was made opaque for performance reasons.

 

That would make sense, transparency requires pixel compares from a foreground window with a background window -- not too bad if the background window is static, but when it'a rendered window in real time I can see the performance impact there.  If you notice Windows 8.x also hides the Aero transparency look and feel because it does have a performance penalty.

 

Cheers, Rob.


 

 


When I set the "object shadows" slider to zero, the VC shadows are gone

 

I believe this is by design ... if you set this value to Zero you should not get any shadows listed under Object Type regardless of checked or unchecked ... as you are defining the shadow distance to 0.  

 

But I'll test the scenario you listed in your link to see if I can replicate.

 

FYI, getting a new build today with many more fixes and will test tonight.

 

Cheers, Rob.

Share this post


Link to post

 

 


I believe this is by design ..

 

would be sad as it was definitely not the case in 2.3

 

 

thanks for your great work for the community!!!!

Share this post


Link to post
They said something about the transparent ATC window not being compatible with Windows XP

 

Was it not compatible with XP in FSX??? :huh:

Share this post


Link to post

Don't you think the current ATC window that blocks so much of your view is annoying? A transparent ATC window has been promised since 1.3 and we still don't have it.

 

I followed Chaotic's link above, and in November 2013, LM said this:

 

"Hopefully this will be enabled in a point release."

 

That's far from a promise.

Share this post


Link to post

Was it not compatible with XP in FSX??? :huh:

 

Sorry about that, I didn't remember what Beau said well. I edited my post with the link where he says the transparent ATC window actually caused a big performance hit in Windows XP and 7 with Aero disabled (I don't remember anything like that in FSX though).

Share this post


Link to post
Guest tymk

 

 


I only have one product where SimObject.cfg will be an issue and it's not a product designed for P3D ... Ultimate Traffic 2 requires a SimObjects entry in the Prepar3d.cfg ... on a re-install, this will have to be put in the SimObject.cfg. So any existing product adding SimObject entries will need to be adjusted. There are also other developer related changes that I need to explore and see how they are impacted and/or if they are impacted, specifically Windows permissions.

 

Thanks, now I get a clear idea... I wasn't sure if this only affected add-ons that need to write to the main .cfg or others as well. Looks like there's nothing to worry about.. :wink:

 

Tym

Share this post


Link to post

 

 


Fixed an issue that would prevent effects from visually displaying if the effect was at a low level of detail distance

 

Hi Rob, could you please confirm if this has any bearing on the invisible AI traffic strobe lights?

 

Sorry if I missed it somewhere else in the thread...

Share this post


Link to post
Guest

 

 


Hi Rob, could you please confirm if this has any bearing on the invisible AI traffic strobe lights

 

Not sure what you mean, the AI traffic I've encountered have working strobe lights?  I have several video's showing working strobes ... unless I'm not understanding you correctly ... is there a specific circumstance where they don't?

 

Cheers, Rob.

Share this post


Link to post

May not be true in this case but I've found that a LOT of light problems come from the video driver and the settings in Nvidia control panel. A while back I had large blocks of light blinking at night - ultimately changed an anisotropic setting and all was well. Several other light related problems fixed with a driver change.

 

I see strobes on AI too. I think we can assume that the P3D's are the same, so you might start looking at drivers and settings.

 

Vic

Share this post


Link to post

Not sure what you mean, the AI traffic I've encountered have working strobe lights? I have several video's showing working strobes ... unless I'm not understanding you correctly ... is there a specific circumstance where they don't?

 

Cheers, Rob.

 

Hi Rob, I've had this issue with both WoAI and MyTraffic. I don't get any visible strobe effects on AI aircraft unless I'm right up next to it (the effects are still quite subdued). I'd say the effects disappear when I'm 50-100m away, the result being that AI strobe lights are all but invisible most of time. It's a lonely place at night...!  

 

Just wanted to add that the MyTraffic dev also confirmed this issue on his forum - he alluded to "longer tracking of visual elements".

http://forum.simflight.com/topic/77753-prepar3d-night-lights/

 

 

May not be true in this case but I've found that a LOT of light problems come from the video driver and the settings in Nvidia control panel. A while back I had large blocks of light blinking at night - ultimately changed an anisotropic setting and all was well. Several other light related problems fixed with a driver change.

 

I see strobes on AI too. I think we can assume that the P3D's are the same, so you might start looking at drivers and settings.

 

Vic

 

Hey Vic, I've tested with with/without DSR, FXAA and various AF settings (I'm currently running 8X in-sim). I also don't use Nvidia Inspector. Could you please clarify what anisotropic setting you changed in the control panel? 

Share this post


Link to post

From what I've read in the P3D forums, all Nvidia drivers after 337.88 have some problems with lights in the sim. Might be worth it to try and downgrade unless your GPU is too new to work with those older drivers.

Share this post


Link to post
Guest

For those of you with Strobe light issues, what GPU and driver version are you using?

 

Also, be aware that if you revert back to an older driver using nVidia's uninstall/re-install process, you will be left with component version mismatches.  This caused some strange issues for me and caught me out ... so per other's recommendation I used the DDU tool to remove the nVidia driver via safe mode ... tool here: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html .

 

Cheers, Rob.

Share this post


Link to post

 

 


Hey Vic, I've tested with with/without DSR, FXAA and various AF settings (I'm currently running 8X in-sim). I also don't use Nvidia Inspector. Could you please clarify what anisotropic setting you changed in the control panel?

 

There's a link to my current settings in the SLI thread here. IIRC, I changed it to application controlled at 16x - I had previously used enhance application.

 

Vic

Share this post


Link to post
Guest tymk

 

 


I don't get any visible strobe effects on AI aircraft unless I'm right up next to it (the effects are still quite subdued). I'd say the effects disappear when I'm 50-100m away, the result being that AI strobe lights are all but invisible most of time. It's a lonely place at night...!

 

I have the same issue. The strobes are there, but very 'anemic', so they tend to get completely overpowered by nav lights even at short distances, plus they're virtually invisible from further away. I remember LM did some experimenting with effect sizes in the recent point releases, and it seems that the strobe effect was not made consistent with other effects. A quick'n'dirty fix is to edit fx_strobe.fx in the effects folder (make a backup first) and double the values in all "X Scale=x.xx, x.xx" and "Y Scale=x.xx, x.xx" lines.

 

Tym

Share this post


Link to post

I avoid "fresh installs" whenever I can, now that I know that LM only allows a certain number of them.  Once the limit is reached, you have to get with them and get their blessing to re-install P3D, probably prove to them you paid for it, yada, yada.  I don't need the hassle.

 

1. I emailed just before Christmas to reset one of my P3D licences from an old computer that no longer functions. The response was very professional...and took eight minutes! Nothing was reuired other than a 1-2 line email.

 

2. Under normal circumstances, just uninstall via windows and your licence will then be automatically reset. Easy!

I'm looking forward to 2.5 at this point and have no qualms about knocking off my entire installation to bring 2.5 in. (*I'm horsing around with FSX:SE right now, and I immediately started to miss the cloud shadows and more rich visual experience P3D brings to the table.)

 

Thanks to all,

-Greg

 

P3D doesn't look much different to FSX - until you go back to FSX! I didn the same as you, reinstalled FSX recently in the form of FSX SE. There's some planes I'd like to fly again in FSX, but to be honest I just don't enjoy that sim any more due to the lesser-uality visuals.

 

Also, I noted a few comments earlier about having to reinstall photoscenery and how difficult this is. I have quite a bit of photoscenery (I think I have all the commercially available photoscenery apart from France VFR, some Vero FS and two megascenery regions (Germany+UK). I just bought a new 4TB drive just for photoscenery and it is almost full already!

 

Photoscenery is the easiest thing in the world to 'reinstall' bewteen updates. When performing the original install, always put a region in its own folder, then add manually via the scenery library. You need to only activate specific folders of photoscenery anyway as you fly it otherwise load times become extreme (and I have the photoscenery that I commonly use on a 1TB SSD).

 

This means that the photoscenery that you installed in FSX 5 years ago is still fully usable in P3D v1/v2/vX.

 

The additions that I use with photoscenery - such as Aerosoft night environment, Open VFR, mesh - are also all added and rmeoved in the same way so no need for reinstall.

 

That means that the only things that need to be reinstalled with a full update like v2.5 are the planes, Orbx and a couple of other random addons such as UTX.

Share this post


Link to post

CB, the link doesn't seem to work.

The link works very well for me.

Spirit

Share this post


Link to post

CB, the link doesn't seem to work.

I suppose you have to be registered with the ORBX forum.

 

Regards, Michael

Share this post


Link to post
Guest
This topic is now closed to further replies.
Sign in to follow this  
×
×
  • Create New...