P3D v3.3 now available

http://www.prepar3d.com/product-overview/

 

Strangely the changelog is giving a 404 message as of this moment, but I'm sure they're waking up in L-M land.

Thanks for the alert. I was able to view the change log on the LM site without issues.

Thanks for the alert. I was able to view the change log on the LM site without issues.

 

Change log viewable

http://www.prepar3d.com/SDKv3/LearningCenter/what_is_new/new_v33.html

Just a heads-up:

 

Active Sky Next has been updated and is now compatible with v3.3.

 

http://www.hifisimtech.com/forums/showthread.php?6207-ASN-Open-Beta-5-P3D-3-3-support!&p=31073#post31073

Guys I never updated the P3D before, I started with 3.2

 

The way it seems to me is that this is not an update, but a whole sim I am installing over again. What's going to happen to all my add ons??

 

Please explain.

Simple - do NOT run the SETUP.EXE or it will overwrite all your stuff.

 

Download the CLIENT.MSI, CONTENT.MSI and CONTENT.CAB

 

UNinstall ONLY the client and content.

 

Reinstall with what you downloaded

 

go fly

 

The majority of your add-ons will be fine

 

Shouldn't take more than 10 minutes.

 

Vic

Got it, thanks Vic.

Also delete the shaders folder - it will rebuild.

 

C:\Users\\Appdata\Roaming\LockheedMartin\Prepar3d V3\Shaders

 

do NOT delete the shadersHLSL folder in the Prepar3d root folder!

 

Vic

So does anyone have any benchmarks yet or major issues to report on this update?

 

Oddly enough, I reinstalled GSX for the first time in I don't know how long for P3D, and that thing runs like a champ and makes me want to fly more than I already am. Of course, this is all with 3.2 so I am looking for strong evidence that upgrading to 3.3 is worth it.

regenerated the Shaders folder, visuals improved but the vas is horrible.

Will try a test flight.

It's a catastrophe, I no longer have a P3D (((((((((((((((((

not usable.

 

and I didn't keep my 3.2 download so I can't get that back.

I downloaded the update but have not installed it....my v3.2 is doin good...my FSX Gold is fantastic.....with FSRecorder.....I am not going to ruin or delete FSX....it is always there for me..

It is always advisable to wait about a month before updating to allow all developers to get their products inline with the new patch. Also, you only need to uninstall the client and install the new client with this patch.

It is always advisable to wait about a month before updating to allow all developers to get their products inline with the new patch. Also, you only need to uninstall the client and install the new client with this patch.

 

Next time I sure will.

I tried the notorious EDDFv2 approach with ifly 747, it actually did well, seems like it is better at re-generating VAS (a VAS rollercoaster, it drops low, then regenerates a lot...) Will be trying JFK-MEM now.

Anyway, wish I kept the 3.2 that I got to work after 1/2 year of struggle.

 

How do I go back to 3.2? where are the old installers?

Next time I sure will.

I tried the notorious EDDFv2 approach with ifly 747, it actually did well, seems like it is better at re-generating VAS (a VAS rollercoaster, it drops low, then regenerates a lot...) Will be trying JFK-MEM now.

Anyway, wish I kept the 3.2 that I got to work after 1/2 year of struggle.

 

How do I go back to 3.2? where are the old installers?

 

The old installers are ALWAYS removed when the new installers appear at the L-M. The only version supported is the latest. Unless you backed up your P3Dv3.2 files and folders or the installer you are now stuffed.

Lesson to be learned about waiting, reading, watching and letting others do the fault-finding, to be sure.

 

At no point have we EVER said or suggested that you should `upgrade` to 3.3.3. You did that all on your own.

 

 

FWIW, I see VAS reduction in 3.3 over 3.2. I also see a number of minor issues relating to addon software. NO addons were `lost` by updating the Client and Content files. Haven't yet had sufficient testing time to be able to review in detail but performance in cloudy environments seems to have improved a notch (1-2 fps) at first glance.

I believed people want the latest and newest of P3D, and that every new P3D upgrade is a awesomely welcomed by simmers.

 

Actually not bad, we have to move forward anyway. There are at least two big improvements and I find it a huge leap forward:

VAS regeneration, the 3.3 does that breathtakingly. Of course right now the 3.3 is VASy-low, so the "minus" and "plus" neutralize each other (actually the VASiness is greater then VAS regen capability). But if LM to correct the VAS-drain with a patch, the new 3.3's capability to regenerate VAS will practically make this sim an OOM-proof (I may be using the wrong terms here but you get the point). EFFDv2 inside iFly 747 VC, 450-550MB, changing the time of day or change the aircraft, fall to 180MB!!, the next 2 seconds it is 500mb again. Repeat it, 180MB, 550MB next 2 seconds.

Yesterday flew NGX KJFK to new KMEM. 600MB over NY, 1000 MB in cruise and descend, then down to 800 and 600 with KMEM in sight, then up to 800 again after landing. I just hope the 3.3 low VAS problem and the capability to regenerate VAS can exist independently and not part of one story, so I can hope the low VAS problem can be fixed and the regen capability can stay, would like to here the specialists...

 

Another thing is 3.3 does better job and cloud display on sunny days with ASN. I was not happy with 3.2 cloud display, it was scarce and flat and FS98tish )))) So this is very good (although may have to do with the wat ASN operates).

But performance over the big cities is lower with 3.3, the Kaby Lake will take care of it.

Now LM needs to do a VAS patch and start working on increase of LOD radius keeping the performance where it is.

I believed people want the latest and newest of P3D, and that every new P3D upgrade is a awesomely welcomed by simmers.

 

Actually not bad, we have to move forward anyway. There are at least two big improvements and I find it a huge leap forward:

VAS regeneration, the 3.3 does that breathtakingly. Of course right now the 3.3 is VASy-low, so the "minus" and "plus" neutralize each other (actually the VASiness is greater then VAS regen capability). But if LM to correct the VAS-drain with a patch, the new 3.3's capability to regenerate VAS will practically make this sim an OOM-proof (I may be using the wrong terms here but you get the point). EFFDv2 inside iFly 747 VC, 450-550MB, changing the time of day or change the aircraft, fall to 180MB!!, the next 2 seconds it is 500mb again. Repeat it, 180MB, 550MB next 2 seconds.

Yesterday flew NGX KJFK to new KMEM. 600MB over NY, 1000 MB in cruise and descend, then down to 800 and 600 with KMEM in sight, then up to 800 again after landing. I just hope the 3.3 low VAS problem and the capability to regenerate VAS can exist independently and not part of one story, so I can hope the low VAS problem can be fixed and the regen capability can stay, would like to here the specialists...

 

Another thing is 3.3 does better job and cloud display on sunny days with ASN. I was not happy with 3.2 cloud display, it was scarce and flat and FS98tish )))) So this is very good (although may have to do with the wat ASN operates).

But performance over the big cities is lower with 3.3, the Kaby Lake will take care of it.

Now LM needs to do a VAS patch and start working on increase of LOD radius keeping the performance where it is.

 

No you need to wait until addons have been verifieid as v3.3-compliant and stop being the author of all of your own misfortunes. Repeatedly

 

What you say above has almost no relationship with actuality. And to repeat myself: What did I say about `knowledge`..?

Huray!!!!!!! I found the 3.2 on 1 od my drives. Ohhhh boooy.... did a lot of flying with 3.3 and: ooohhh boooy.

I might have had a wrong impression on VAS (I had no OOMs anyway), but the scenery is all killed and I had many depressing scary thoughts about how I will be living 3.3.

 

I like and I want progress, I left FSX and went to technically fresher XPlane 64 and P3D, but a radical cut-off like the 3.3 is noooo way, nnooooooooooo........ I shall first let the medical industry to learn how to grow legs that can run faster, only then I will let the doctor to amputate my present legs ))))))

But I do like seeing P3D evolving, still will stick to 3.2 till add on industry catches up.

LM is moving P3D forward. Years ago they announced that they would eventually discontinue support for products made using the old F2002 SDK. In this release, they have, by design, taken that step. Some users who are heavy into scenery still using that method will find that their scenery will have a flashing issue. The developer of the UK2000 series has acknowledged that he took the "easy" way out in the past but that he plans to update all the UK scenery using the current P3D SDK - this could take about a year according to him.

 

I have had NO issues of any kind with either scenery or VAS and I have noticed that VAS recovery seems better in 3.3. This is by simple observation not an accurate testing procedure.

 

Vic

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=119535

Has anyone flown in P3D v3.3 with the latest LClookup conversion done by ORBX? I started to get OOMs in P3D v3.2 after doing the conversion of my scenery. Now, I don't know if it's shear coincidence or not, but I was rather surprised by these OOMs, since I hadn't had any since the upgrade to v3.2. I did download 3.3 a couple of days ago, but have yet to install (waiting on fixes from 3rd party devs). V3.2 had worked extremely well for me in that I could fly anywhere without any VAS issues, hence why I think I narrowed it down to the ORBX conversion.

Has anyone flown in P3D v3.3 with the latest LClookup conversion done by ORBX? I started to get OOMs in P3D v3.2 after doing the conversion of my scenery. Now, I don't know if it's shear coincidence or not, but I was rather surprised by these OOMs, since I hadn't had any since the upgrade to v3.2. I did download 3.3 a couple of days ago, but have yet to install (waiting on fixes from 3rd party devs). V3.2 had worked extremely well for me in that I could fly anywhere without any VAS issues, hence why I think I narrowed it down to the ORBX conversion.

 

Quite a few complaints about OOMS with 3.3 on P3D Facebook group, LM forum, and Avsim.

Quite a few complaints about OOMS with 3.3 on P3D Facebook group, LM forum, and Avsim.

 

I did see the postings at LM about the VAS issues and LM stated that they were releasing a fix, correct?

 

I haven't seen the other information on the other sites though, but I asked here hoping to get a little insight to any individuals setups, flights and results.

I don't doubt that some users have VAS issues - fortunately the majority do not or we would have the type of outcry that occurred when UK2000 ceased to function properly.

 

And, sorry, I've done enough tech support through the years to learn that you really can NOT believe what a user tells you when he's complaining. It's always a clean install, they have never "just" added something, etc.

 

When the overwhelming majority of users are posting VAS issues, THEN I might believe that there is an issue - until then, with very few exceptions, it falls into user error.

 

Vic

I don't doubt that some users have VAS issues - fortunately the majority do not or we would have the type of outcry that occurred when UK2000 ceased to function properly.

 

And, sorry, I've done enough tech support through the years to learn that you really can NOT believe what a user tells you when he's complaining. It's always a clean install, they have never "just" added something, etc.

 

When the overwhelming majority of users are posting VAS issues, THEN I might believe that there is an issue - until then, with very few exceptions, it falls into user error.

 

Vic

 

Guess you are wrong, because they found the problem with teh VAS issues that many were having. http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=119535&sid=caee731c7132fbf43b9c68bfd73705fd&start=30#p137392