Updating to P3D 3.3.3 Issues thread

ejoiner

ejoiner

Charter Member
Hi guys, I am starting a thread to capture any issues people are running into with upgrading to P3D 3.3.3.

I myself did the full uninstall/reinstall. (likely wont do that again after literally reinstalling about 15 orbx scenery sets.)

Main issue I am seeing so far:

Black clouds. Normal puffy white clouds turn jet black as my aircraft approaches them. Once I pass away from the black cloud it turns white again. I am assuming the "black" is an untextured cloud shape? I use REX Essential + Overdrive AND REX Texture Direct. So my clouds are 3rd party. Does not seem to matter whether I set the installed clouds to be DXT5 or 32 bit. Same thing happens. Also this does not appear to me to be shader dependent. It happens with default P3D shaders as well as the "realism shader pack". It also does not appear to be settings driven in the sim as far as I can tell. Clouds in the distance or high above are unphased. its only those clouds within a certain radius of my aircraft that turn black.

I will be posting this on the LM P3D site as well. will report any feedback.

Eric
 
The renewal charge has been sitting in the "prcessing" queue at BofA for four days now...don't have my password yet!!! Not looking good. :biggrin-new:
 
I had the black clouds after just installing the client.msi. I had used realism shader pack. I then read at avsim about a guy that reinstalled the contents.msi with the mandatory contents.cab and proceeded to delete shader cache. Still black clouds. Then, I did another reinstall of the client.msi and voila, clouds are back at their normals. I did delete shader cache after this as well.
A good performing sim got better. I think the ground textures look better.


Sent from my iPad using Tapatalk
 
No issues for me (yet). Reverted the modified shaders back to the originals, then did a client and content update. Deleted the shader cache, installed latest versions of FSUIPC and ASN.
Everything seems fine but I've got a 3.2 backup just in case!
 
DaveWG said:
No issues for me (yet). Reverted the modified shaders back to the originals, then did a client and content update. Deleted the shader cache, installed latest versions of FSUIPC and ASN.
Everything seems fine but I've got a 3.2 backup just in case!
Click to expand...


Yes, it appears the "cure" is to reinstall the client.msi and clear the shader cache. This restores the 3.3 default shaders. Black clouds gone. Guess we will need to avoid 3rd party shaders until they catch up to 3.3 version.
 
Repeating here what I mentioned in the other thread about issues with sceneries created with FSX SDK and involving GPs and layering. There is annoyin flickering observed, probably due to the new zbias related update.

The issue is discussed here at Avsim:

http://www.avsim.com/topic/489577-serious-ground-layering-bug-in-33/

I finally updated to 3.3. I had no issues with clouds shaders cause I have reverted to default shaders before upgrading. Installed client and content and then applied again REX textures and soft clouds with no issues. PTA tool works well with shaders, thanks Dag!

I have observed the flickering issue on runways and taxiway markins in Aeorosoft Kastellorizo X and Flytampa Athens which use custom GP type layered marks. I hope that either LM may look into this and provide a fix or the devs maybe adapt their sceneries.
 
I observe the flickering as well, also on static scenery objects that didn't flicker in 3.2. On my system, the flickering only occurs when one moves the viewpoint or the camera is in motion. I hope they fix that.


Cheers,
Mark
 
Flickering of runway textures in Orbx KRDD also noted. This occurs as Mark mentions when the viewpoint is moved. Haven't explored much lately but KRDD is my home airfield. Haven't noticed this in the previous P3D version as well.
 
It has been reported that the Milviz F-4 Phantoms (E/J/S) are not currently working in P3D V3.3.

Cheers,
 
scotth6 said:
It has been reported that the Milviz F-4 Phantoms (E/J/S) are not currently working in P3D V3.3.

Cheers,
Click to expand...

I can confirm the problem wth the Milviz F-4 all versions and P3D V-3.3. One selects the aircraft and after a few seconds P3D crashes.
 
An update is already under testing for the M/V F-4.

The scenery flickering indeed has to do with viewpoint.
 
The flickering has been around for quite a while, but has dramatically gotten worse in P3D. The original issue was limited to viewing ground polys, especially runway textures, from altitude.

Now, that bug seems to be more prevalent. In my work, I use four layers of textures on a typical asphalt or concrete surface.

1. Base texture
2. Wear
3. Traffic marks
4. Markings and lines.

Typically, those layers should behave normally when placed .01 meter separation, with the first layer at 0.01 M above the background texture. This has all changed, and I need to sometimes place the layers 0.1 M separation to fix the flicker from a distance. The problem then translates to the ground render with the textures now up to the rim of the wheel on an aircraft. Looks horrible.

I've seen the same with buildings. If I design a building with an inner and outer wall, the model will display normally when on the ground at the airport. From the air, as distance increases, the two walls will begin to flicker as if the two planes were superimposed on each other. To fix the flicker the walls need to be about 1 M thick, which looks ridiculous and stupid.

It's really a problem for developers at this point.
 
I found that setting the Antialiasing Transparency to 8x (Supersampling) in the Nvidia Control Panel reduced the flickering, but not eliminated it completely.

[Edit: still flickers heavily from farer away]

What is worse is a serious performance hit, even with clouds turned off. I get fluctuations of fps that go from ca. 15fps to the locked 30fps that feel like someone's stepping on the brake every 2 seconds or so. Didn't have that in 3.2 with the same settings, and I haven't seen 15fps in a long time.


Grrr.

Mark
 
roger-wilco-66 said:
I found that setting the Antialiasing Transparency to 8x (Supersampling) in the Nvidia Control Panel reduced the flickering, but not eliminated it completely.

[Edit: still flickers heavily from farer away]

What is worse is a serious performance hit, even with clouds turned off. I get fluctuations of fps that go from ca. 15fps to the locked 30fps that feel like someone's stepping on the brake every 2 seconds or so. Didn't have that in 3.2 with the same settings, and I haven't seen 15fps in a long time.


Grrr.

Mark
Click to expand...

I experience heavy stuttering like a slideshow for a few seconds then it is smooth as butter. I get this at irregular intervals and it is indeed annoying.
 
You must log in or register to reply here.
Back
Top