P3d v4.3

[ErichB 3,642]

10 minutes ago, Christopher Low said:

Since that will take me well into 2019, I suspect that P3D v5 will be on the horizon at that stage

I'm glad that ended well.... :)

[HighTowers 1,434]

Gotta hand it to those die hard 32 bit simmers for hanging on so long.  It was like being caged in concrete box with no where to go. OOM management drove me nuts and so glad to be rid of it never to be seen again. It does amaze me though how many continue to ask for the same features that are only now coming to v4 only because 64bit allows it to be possible, yet they continue to ask it it will be avail for FSX/P3D 32bit. 

I only have middle of the road hardware, but even if on the lower end, I would still go to v4 to take advantages of the extra tech and features, and just scale back settings until its acceptable. At least your not chained by a 4gb limit, and you have an ongoing developing sim.  My 2cents worth. 

[jabloomf1230 2,445]

3 hours ago, ErichB said:

What exactly would this mean?  A new terrain engine? 

It was unclear what Adam Breed meant in his answer given in that interview. It could mean anything from adding the Vulkan API to adopting an entirely new rendering engine. Breed also stressed the importance of backwards compatibility, which usually refers to the sim's file formats like BGL, MDL and AIR, but it has been possible for both LM (and also DTG and MS) to retain the file formats while making major improvements in rendering.

[Vali 83]

No CTDs, no more stuttering and under 30 fps with DL even on high end specs will be a good start for 4.3(  I know that fps depends also by addons a lot but.. still :D)

Edited June 11, 2018 by Vali

[nealmac 260]

On 6/8/2018 at 9:29 PM, Bobsk8 said:

60FPS with all sliders to the right, maybe????

With mediocre hardware? Sounds good to me 😅

[ErichB 3,642]

1 hour ago, Vali said:

No CTDs, no more stuttering and under 30 fps with DL even on high end specs will be a good start for 4.3

Unless they fix the clunky terrain engine(for one) unlikely 

[Ray Proudfoot 8,950]

2 hours ago, HighTowers said:

Gotta hand it to those die hard 32 bit simmers for hanging on so long.  It was like being caged in concrete box with no where to go. OOM management drove me nuts and so glad to be rid of it never to be seen again. It does amaze me though how many continue to ask for the same features that are only now coming to v4 only because 64bit allows it to be possible, yet they continue to ask it it will be avail for FSX/P3D 32bit. 

I only have middle of the road hardware, but even if on the lower end, I would still go to v4 to take advantages of the extra tech and features, and just scale back settings until its acceptable. At least your not chained by a 4gb limit, and you have an ongoing developing sim.  My 2cents worth. 

Remind yourself how many crashes you had when you first got v4 assuming you were an early adopter.  Compare that to the relative calm of v3. 😀 

I can’t recall the last time I ran out of VAS with v3.4. I just keep the sliders at reasonable levels and that has the added benefit of boosting frame rates. Yes, in v4 you’re not going to run out of VAS but push those sliders too far and it’s not going to be an enjoyable experience. FPS has always been the highest priority in FS in order to simulate flying.

There was nothing wrong in asking whether the GSX module would be 32-bit compatible. I guessed it wouldn’t so wasn’t disappointed.

[WotanUK 289]

9 minutes ago, Ray Proudfoot said:

Remind yourself how many crashes you had when you first got v4 assuming you were an early adopter.  Compare that to the relative calm of v3. 😀 

I can’t recall the last time I ran out of VAS with v3.4. I just keep the sliders at reasonable levels and that has the added benefit of boosting frame rates. Yes, in v4 you’re not going to run out of VAS but push those sliders too far and it’s not going to be an enjoyable experience. FPS has always been the highest priority in FS in order to simulate flying.

There was nothing wrong in asking whether the GSX module would be 32-bit compatible. I guessed it wouldn’t so wasn’t disappointed.

I never understood this argument, i read a few people on the forums insisting that they never got VAS issues with v3.  I used to have what i believed were very reasonable settings in v3 and even then using the FSL A320 at UK2000 EGLL with the ORBX stuff enabled i would very nearly hit 4Gb without actually doing anything.  That was with LOD (the setting that seemed to matter the most) at 6.5 and Vector with pretty much everything switched off.

Of course i could use the default aircraft and airports with no issues at all.

I didn't have any major issues with the first release of v4, in fact i would say that it's been the most stable release from LM i have used (i never purchased v1).

[hvw 402]

>>Remind yourself how many crashes you had when you first got v4 assuming you were an early adopter.  Compare that to the relative calm of v3. <<

None, Ray. None at all.

 

Hans

[Guevorkyan 69]

I haven't been tweaking in V4 the amount I've had in V3 or V2.

P3D4 is as stable as a continental plate.

Edited June 11, 2018 by Guevorkyan

[jason99vmi 157]

Yeah P3D v4 is pretty hard to OOM or CTD.   Even if you push the sliders to extreme it is hard to crash.  Are CTDs still possible yes because of 3rd party addons but that is with any version of P3D when you throw stuff in.   

3.4 was really stable for me but when the last few months running 3.4 and v4, 3.4 was OOMing on every approach.  So i finally deleted all of 3.4.  DCS now occupies its space 🙂

[WotanUK 289]

1 minute ago, jason99vmi said:

3.4 was really stable for me but when the last few months running 3.4 and v4, 3.4 was OOMing on every approach.  So i finally deleted all of 3.4.  DCS now occupies its space 🙂

Absolutely, i remember the approaches after a couple of hours then suddenly you would get the error and that was hours down the drain.  I came very close to quitting the hobby after a few of these.

[Bobsk8 12,681]

42 minutes ago, Ray Proudfoot said:

Remind yourself how many crashes you had when you first got v4 assuming you were an early adopter.  Compare that to the relative calm of v3. 😀 

I can’t recall the last time I ran out of VAS with v3.4. I just keep the sliders at reasonable levels and that has the added benefit of boosting frame rates. Yes, in v4 you’re not going to run out of VAS but push those sliders too far and it’s not going to be an enjoyable experience. FPS has always been the highest priority in FS in order to simulate flying.

There was nothing wrong in asking whether the GSX module would be 32-bit compatible. I guessed it wouldn’t so wasn’t disappointed.

I had a VAS crash with version 3.4 for the first time, since I installed it, last week. I fly about 10 flights a week, so about 500 flights a year for over 2 years,  for a VA. I would consider that pretty reliable. 

Edited June 11, 2018 by Bobsk8

[Christopher Low 5,353]

I used to suffer OOMs quite a bit in earlier versions of P3D, but v3.4 appears to be very stable on my PC.

[Ray Proudfoot 8,950]

32 minutes ago, WotanUK said:

I never understood this argument, i read a few people on the forums insisting that they never got VAS issues with v3.  I used to have what i believed were very reasonable settings in v3 and even then using the FSL A320 at UK2000 EGLL with the ORBX stuff enabled i would very nearly hit 4Gb without actually doing anything.  That was with LOD (the setting that seemed to matter the most) at 6.5 and Vector with pretty much everything switched off.

Of course i could use the default aircraft and airports with no issues at all.

I didn't have any major issues with the first release of v4, in fact i would say that it's been the most stable release from LM i have used (i never purchased v1).

If that is the highest LOD setting then that’s the problem. I kept it to High I think. Don’t know what number that refers to.

With FSL Concorde at Aerosoft EGLL I can get 20fps on approach with around 100 Ai running. There was enough VAS to land at 3rd party KJFK too.

Maybe you need to redefine reasonable settings?  But my guess is the LOD was the problem.