Sign in to follow this  
Nemo

2.3 -> 2.4 update report

Recommended Posts

Following Robs  recommendation the update went smoothly. Thanks Rob!

 

Product version (see p3d.exe details is 2.4.11570.0; 09/24/2014).

 

FSUIPC 4936c (current version) OK

ASN SP1 beta5 - does not work

ORBX Modules  OK

AS TwinOtter extd.  OK

 

 

Cheers,

Harry

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Same response here, followed Rob's guide.  What is it with ASN that makes it very version specific?

Share this post


Link to post

Same response here, followed Rob's guide.  What is it with ASN that makes it very version specific?

ASN "hooks" into the guts of P3D. I believe it is hard coded to specific addresses which can change when a new version is recompiled. Actually, depending on what they change, FSUIPC can have the same issues for the same reasons. the product dll's need to reference addresses which are no longer valid.  I am sure Pete and Damian can provide a better explanation but that is the gist of it.  :)

 

Vic

Share this post


Link to post

Everything good with Robs procedure.

 

FSdreamteams addon manager refuses.

 

 

I'm unsure about the cloud size fix, LM provided a few weeks ago (GetScreenQuadPositions( quad, width*0.5, height*0.5 ): removed it and clouds got very big again and frames dropped down to the half. So I assume, this fix should be left in?

But the bugfix list says this have been fixed!?

Share this post


Link to post

ASN "hooks" into the guts of P3D. I believe it is hard coded to specific addresses which can change when a new version is recompiled. Actually, depending on what they change, FSUIPC can have the same issues for the same reasons. the product dll's need to reference addresses which are no longer valid.  I am sure Pete and Damian can provide a better explanation but that is the gist of it.  :)

 

Vic

 

Okay that makes sense thanks for the insight.  Just checked the support forum looks like they already have internal testing with 2.4 and should have it out in a couple days!

 

One odd thing, maybe cause I have Dino's latest F-35, I get an "F-35 Initialization Error" on start and I have no aircraft.  I went ahead and loaded the A36 saved it off as my default flight.  I did notice also that I couldn't start my port engine on the F-22 only the starboard but will try again now that I have a default flight file that has a valid aircraft.

 

Otherwise all my other addons (tons of them) seem to be just fine.

Share this post


Link to post

Since v 2.4 update, I am no longer working

 

spending too much time on P3DV24

 

:drinks:

Share this post


Link to post

My update worked flawlessly too, thanks to Rob's instructions.

Share this post


Link to post

Mine also but those simconnect files were not in the documents folder. On my V2.3 install (and 2.2) simconnect WAS NOT installed by default.

Share this post


Link to post

Thank you Rob, first smooth update following you instructions. Finally running in wonderful 4K on the Cobra Curved Display at 60Hz with all settings maxed out and its beautiful. They defo fixed all the cloud issues averaging around 30FPS maxed out.

 

Thanks again!

Share this post


Link to post

Everything good with Robs procedure.

 

FSdreamteams addon manager refuses.

 

 

I'm unsure about the cloud size fix, LM provided a few weeks ago (GetScreenQuadPositions( quad, width*0.5, height*0.5 ): removed it and clouds got very big again and frames dropped down to the half. So I assume, this fix should be left in?

But the bugfix list says this have been fixed!?

 

 

I think the idea was to remove the cloud size fix before the 2.4 upgrade.

Then the upgrade would apply it's own fix.

Is this what you did?

 

gb.

Share this post


Link to post

what is the "date modified" on the new cloud file from a 2.4 fix?

Share this post


Link to post

 

 


Finally running in wonderful 4K on the Cobra Curved Display at 60Hz with all settings maxed out and its beautiful.

 

Must look amazing!

 

gb.

Share this post


Link to post

I think the idea was to remove the cloud size fix before the 2.4 upgrade.

If that was the case then Rob would of included this in the instructions. I patched no problem by following the instructions. I notice the cloud.fx file was not reset to default with the patch process...are we to manually edit it back to default?

 

The only thing not working in 2.4 is my F1 GTN750 gauge. Off to the F1 forum...

Share this post


Link to post

the new cloud.fx contains the "quad" fix.

 

Vic

Share this post


Link to post

John, I actually deleted the cloud.fx  file (based on the posts in the other thread) and let patch recreate the file.

 

One other thing I noticed is the "fresh" new p3d.cfg also defaults the ground_shadow_texture_size to 2048 (I thought Rob mentioned it would now default to 512)...

Share this post


Link to post

Everything good with Robs procedure.

 

FSdreamteams addon manager refuses.

 

 

 

 

I'm unsure about the cloud size fix, LM provided a few weeks ago (GetScreenQuadPositions( quad, width*0.5, height*0.5 ): removed it and clouds got very big again and frames dropped down to the half. So I assume, this fix should be left in?

But the bugfix list says this have been fixed!?

 

Just download the add-on manager. That will get it to work

Share this post


Link to post

Good to know it's working well for many of you ... there will always be exceptions given the vast difference in Hardware/software and 3rd party add-ons.

 

 

 


If that was the case then Rob would of included this in the instructions.

 

I mentioned changes to those files in my original post ... there are several changes that folks may have made to the \ShadersHLSL files ... later on in the thread Jim Robinson brings up the specifics about how to make sure patch will update those core LM files that folks may have updated  (i.e. Cloud.fx and others).

 

From my original post:

 

 

NOTE: If you’ve made any changes to files in …\ShadersHLSL you may need to edit and re-apply those changes (and delete your shaders).  Some of the ShadersHLSL files have change and the prior process to update these could reference wrong line numbers - so proceed with caution.

 

Jim Robinson brought this to my attention and was discussed here: http://forum.avsim.net/topic/452190-prepar3d-v24-patch-will-be-released-monday-92914/?p=3083665

 

If you don't have the original LM files, then backup and then delete your Cloud.fx file and the patch will create a new one.  This same process can be applied to other files in the ..\SharderHLSL folder tree that may have been modified.  Thank Jim R. for testing this and his information.

 

Cheers, Rob.


 

 


Just download the add-on manager. That will get it to work

 

Yes, the new Virtuali Add-On manager works fine - however be aware the "setup_addonmanagerX.exe" properties is showing the same file version "2.9.0.24" but the file is actually smaller and NOT the same as the prior "2.9.0.24" Add-On manager.  Not a big deal, but for those of you like myself that manage versions it did throw me for a loop until I noticed the file size was different.

 

Orbx DLL's will update automatically.

 

Cheers, Rob.

Share this post


Link to post

Update Successful!  and its great to have the shadows behaving...the scene is so nice.....  

Share this post


Link to post

The question arises in my head: Why would a installer replace all the necessary files in the update process by new ones and leave one behind? Could it be that the cloud.fx is not part of the updated files? And that those tweaks are still valid? :rolleyes:

 

 

regards,

Share this post


Link to post

The cloud.fx IS updated and the tweak IS included.

 

Vic

Share this post


Link to post

Please post the contents of the updated Cloud.fx for comparison...thanks!

Share this post


Link to post

The question arises in my head: Why would a installer replace all the necessary files in the update process by new ones and leave one behind? Could it be that the cloud.fx is not part of the updated files? And that those tweaks are still valid? :rolleyes:

 

I think it has to do with the save date/time of the file, in my case I had made some changes to Clouds.fx on Sept 23 and it appears the new v2.4 Clouds.fx is dated Sept 18th so the installer apparently doesn't overwrite files that are newer than the ones contained within the patch installer. Those tweaks are still valid, it appears LM fixed the cloud scaling problem GetScreenQuadPositions( quad, width*0.5, height*0.5 ); using the exact tweak they posted for us to do manually. They didn't change GetPointDiffuse( Out.diffuse, position, spriteCenter.xyz ); to GetPointDiffuse( Out.diffuse, position, groupCenter.xyz ); however.

 

That last tweak (for cloud contrast) was on line 313 of Clouds.fx in v2.3, it is now on line 311 indicating something else was changed in Clouds.fx. For that reason it's recommended that you update to the new v2.4 version of the file.

 

If you forgot to return your Clouds.fx to it's v2.3 original state or didn't make a backup before you applied the v2.4 patch you can just delete or move Clouds.fx from the ShadersHLSL folder and reinstall the patch. Same goes for HDR.hlsl in the ShadersHLSL\PostProcess folder which is the one we did the HDR transition time tweak in and also the "toning down the bloom" tweak.

 

Rain.fx is another one we tweaked (reducing the opacity of the rain) but the patch will not replace this one. That must mean the file wasn't updated in v2.4.

 

Jim

Share this post


Link to post

Hi Folks,

 

Anyone care to inform us how 2.4 runs, is it any better than 2.3 or is this just more cosmetic.

 

Has the intermittent scenery stutter been address as I see there were some rendering changes.

 

I have removed p3d completely from my system as I was just getting very frustrated with the stutters...not Vsynch...so before I do a complete reinstall just wanted to get some feed back...otherwise it could be a very long wait until I use it again..

 

With thanks

Share this post


Link to post

 

I think it has to do with the save date/time of the file, in my case I had made some changes to Clouds.fx on Sept 23 and it appears the new v2.4 Clouds.fx is dated Sept 18th so the installer apparently doesn't overwrite files that are newer than the ones contained within the patch installer. Those tweaks are still valid, it appears LM fixed the cloud scaling problem GetScreenQuadPositions( quad, width*0.5, height*0.5 ); using the exact tweak they posted for us to do manually. They didn't change GetPointDiffuse( Out.diffuse, position, spriteCenter.xyz ); to GetPointDiffuse( Out.diffuse, position, groupCenter.xyz ); however.

 

That last tweak (for cloud contrast) was on line 313 of Clouds.fx in v2.3, it is now on line 311 indicating something else was changed in Clouds.fx. For that reason it's recommended that you update to the new v2.4 version of the file.

 

If you forgot to return your Clouds.fx to it's v2.3 original state or didn't make a backup before you applied the v2.4 patch you can just delete or move Clouds.fx from the ShadersHLSL folder and reinstall the patch. Same goes for HDR.hlsl in the ShadersHLSL\PostProcess folder which is the one we did the HDR transition time tweak in and also the "toning down the bloom" tweak.

 

Rain.fx is another one we tweaked (reducing the opacity of the rain) but the patch will not replace this one. That must mean the file wasn't updated in v2.4.

 

Jim

 

Jim is absolutely right. That's why I always first make a backup copy and rename it to  "???.fx.original" before I make changes to the "???.fx" file. When I pepare for the update I delete "???.fx" and rename "???.fx.original" to "???.fx". This procedure makes sure that the timestamp of the original file is not changed.

 

Harry

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this