While its amazing that patches are coming fast, meaning LM is really on the ball and determined to get this right, but the problem I see is always waiting for installers from 3PDs. I dont understand why they cant make installers that are more flexible. As in can be installed in p3d V2.X so it covers at least the next versions up until 2.9.  Perhaps its not feasible?

Arent 3PDs annoyed by always making another installer? Qualitywings just put out the 757 installer for 2.3 just a couple weeks ago

 

It's rather ironic that the "dead end" nature of FSX is actually one of its strengths. No new versions or updates means that addon developers (and customers) don't have to worry about compatibility issues with different iterations. Unfortunately (or fortunately, depending on how you see it) we are always going to have to deal with new versions of P3D. Maybe I will feel a lot better about the situation when I have successfully used Rob's update procedure :smile:

 

 

 

I dont understand why they cant make installers that are more flexible. As in can be installed in p3d V2.X so it covers at least the next versions up until 2.9.

 

For a moment I thought you were joking but it seems you are serious... ^_^ Obviously (I would say) it's not about the INSTALLERS. You can be sure that every current version of ASN, FTX, A2A, whatever, will be able to install into P3D 2.9 (if we ever get that version). But it's not about the installers, it's about new options and alterations in P3D itself that will make the addon ITSELF incompatible with P3D. And obviously (I would say) no developer, heck, not even LM, knows right NOW what will be new or altered in version 2.5 or 2.6 or 2.7... they can't look into the future! ^_^

 

Imagine (repeat: imagine, because this won't happen!!!) that version 2.5 would bring 64 bit support (again, imagine!!!). Now you can be sure your current plane installer will be able to install itself into P3D. No problem! But will it work? NO WAY! So it's not about the developers being dumb and not being able to create future proof installers: it's about the content of P3D and the addons.

Why this backup?

 

C:\Users\Rob\AppData\Local\Lockheed Martin\Prepar3D v2

 

 

I fairly certain Orbx, HiFi, Virtuali will have updates out pretty quick once released. These are the only products I used/have that needed updates ... and Orbx products still worked I just had to click the "Run Once" button during startup.

 

Good to know. For me that means I will only have to wait for an ASN update.

 

 

 

As far as glass VC in the A318 ... not exactly sure what you are looking for here, but here is a screen shot during the day with default weather (warning large image 3840 x 2160): http://robainscough....ff5bfaf3616.jpg

 

Thanks for the screenshot. Well, I also don't know what to look for but Aerosoft said at the release of the A318/319 the P3D version would not show glass on the screen, unlike the FSX version, and it turned out to be a bug in P3D that would be solved in version 2.4. However, when I look at your video and screenshot, it looks the same as on my PC... I think you should be able to see reflections and so on. I will ask on the Aerosoft forum if they know more about this already.

 

 

I would say don't use your existing tweaked shaders but backup and tweak the new ones instead because there may be other changes we don't know about.

 

Very good point Jim, thank you... I'll do it this way, just in case.

Hey guys, easy, easy - sometimes it looks to me as the fox burgled into the hen house. No need to panic or getting too much nervous. It's not a matter of life and death. The patch will work fine as the last ones also did.

Spirit

I have always felt that Friday evening GMT is the preferred time to release new software.  Not so great for tech support but a great time for the user.  Just saying.

 

Tim

QW C32A

Hey guys, easy, easy - sometimes it looks to me as the fox burgled into the hen house. No need to panic or getting too much nervous. It's not a matter of life and death. The patch will work fine as the last ones also did.

Spirit

Oh, the irony, the wonderful irony I like it!

 

Mike

 

 

Does 2.4 include the CFG entry for "AlwaysFullLoad=1,"

 

No, and I'm not 100% sure it was needed ... some aircraft seem to stick around in memory while others don't.  No harm in adding it and it does seem to help with some aircraft when switching but not always.  There was a fix in v2.4 (see change list at beginning of this thread) that indicates a .BGL fix that was source of memory leak.  But as always, OOMs are still possible with enough 3rd party content loaded and high graphics settings.

 

Jim, thanks for info, appreciate it.

 

 

Hopefully they are having tremendous input and communicating with LM on issues, or what could be done better.

 

Yes they do, and LM fix items requested -- what they fix is up to them.  The bridge/pylon issue unfortunately is not going to be fixed any time soon, LM are aware and the issue and it's on the table, but to fix it would introduce considerable core code changes with a high potential of side effects (i.e. breaking a lot of compatibility).

 

If I were LM, these types of changes I would table for a "new" product (like a 64bit product) ... but I'm NOT LM so I'm not speaking for them only presenting a possible thought process based on my development experience.

 

Cheers, Rob.

 

 

It's just that installing P3D from scratch again is not an option for me, because it would take a HUGE amount of time to reinstall all of my addons again (and they all seem to work in P3D at the moment). I guess that I will just have to bite the bullet, and keep my fingers crossed that I don't mess up

 

That's why I provided this process so that you don't have to wipe everything and re-install.  But so you are aware, this patch process is not likely to change any time soon for reasons I outlined.  But, where one finds a weakness/need ... some creative 3rd party devs make take up the challenge (like EMT) but they would need to know A LOT about 1000's of 3rd party products to make the patch process transparent to the user.  However, I'm certain such a product would sell well ... EMT is used by many.

 

Cheers, Rob.

Rob,

 

I had another look at your procedure, and it isn't as complicated as I had thought. I was probably daunted by the wall of text! I have already found the four folders that you suggest need to be backed up, so that will not be a problem.

• General fixes to terrain shadow artifacts

 

Nice that they're finally fixing the terrain shadowing issues. I only ran v2.3 for about 10 minutes before I discovered this bug that made the sim unusable. Went back to P3D 1.4 which has working terrain shadows. Even though they are calculated by the CPU, at least they work properly.

Txt, I prefer an update without troubles.

 

Regards

Loek

Txt, I prefer an update without troubles.

 

Regards

Loek

Why this backup?

 

C:\Users\Rob\AppData\Local\Lockheed Martin\Prepar3D v2

You don't need to save it. It has the compiled shaders folder. Just delete everything in the Shaders folder.

Txt, I prefer an update without troubles.

 

Regards

Loek

Txt, I prefer an update without troubles.

 

Regards

Loek

You can say that again!

thank you for the update. 

it is possible to install  p3d 2.4 fully again (not patch)

thank you

 

thank you for the update. 

it is possible to install  p3d 2.4 fully again (not patch)

thank you

 

 

I believe it would only be a patch but not sure as no one really knows yet