But given that these are FTX objects/textures I don't see how this is an LM issue? Just as with DX10 under FSX (even with Steve's DX10 Controller) there are still issues with various objects/textures from 3rd party vendors that can only be resolved by the 3rd party vendor (or one can edit the offending file if one is comfortable doing so).

 

Well, Orbx refused to do anything about the DX10 problem too where FTXG showed you black boxes where the lights were and you had to buy Steve's fixer to get those black boxes out of the sim. Since this is a very similar issue and probably related problem, this is also why I presumed Orbx won't work on it themselves. Forgot too mention that in my earlier post. ^_^

 

I just asked about this on the Orbx forum why they don't react to the posts about this and if it's Orbx's or LM's problem to fix.

Zoomed in, they look a lot like the "square moon" and "square strobes" some have reported.

 

If it is the same issue, it's definitely in LM's camp to fix.

 

 

If it suspected to be FTX, why not get rid of it and have a more stable usable platform until the point whoever figures it out?

 

Because default textures suck big time...? ^_^ It's already a shame I can't use any of my addon planes but having to fly above default textures is asking too much LOL

 

I was planning on installing some FTX regions because they don't have that FTXG light problem (different system) but I read about regions not working well and looking odd so I also don't dare to do that. Maybe it's best to simply stop flying at ALL and wait for the patches to arrive. And by that I mean REAL patches that solve REAL bugs.

 

 

Maybe it's best to simply stop flying at ALL and wait for the patches to arrive. And by that I mean REAL patches that solve REAL bugs.

 

That's basically what I'm doing.  I'm using P3D - but mainly for tests (settings, bug hunts, trying out addons for compatibility).  What I'm not doing is setting up fully developed, point-to-point, suspension-of-disbelief flights with weather, accurate routing, ATC and such.  I'm looking forward to when I can do that.  But it is not this day.  

The default textures in v2 look great..  I don't need FTX, FTX needs me.. Priority #1 (after the core) - Plane variety.. After that I can still land on runways and look at scenery.. Albeit not as detailed but this is a flight simulator.. Not a scenery simulator.. Nice scenery is and always will be a bonus, not a requirement. 

From what I have read, it seems that some fixes work some of the time, and some people report not having the problem at all.

 

Given the inconsistencies with the problem / solutions, could this be something else related to a particular set up or addons like a weather engine. Can someone who does not see the problem share their setup / addons info?

 

I have been planning to get FTXG, but the pics above will keep me far from it if there is no workaround.

 

 

Since this is a very similar issue and probably related problem, this is also why I presumed Orbx won't work on it themselves.

 

Hmmm ... the only reason I could see Orbx NOT fixing the problem is because it would break DX9 FSX and they don't want to make two separate build sets for P3DV2 and FSX DX9??  I'm guessing ... I can't find any info from Orbx indicating exactly what the problem is?  Is that available somewhere?

 

But in the mean time, why can't you turn on Volumetric Fog if that solves the problem? 

Well, after having various problems with OOMs I reinstalled P3D, no OOMs and then installed FTXG and got OOMs. Without FTXG I could not force an OOM if I wanted too (no matter how hard I tried) and with FTXG I had an OOM within two minutes. Now I am not saying that FTXG should be fixed but there clearly is a problem with P3D 2.0 and add ons so SOMETHING needs fixing badly. I never ever had an OOM with FSX.

 

Take note though that I do have FTXG still installed but I am using medium settings all over to keep VAS as low as possible to avoid OOMs. It's my theory that something is causing memory spikes that overload the VAS but if you keep VAS low to start with that overload will stay within limits. (I have no degree in VAS theoretics though LOL) I am really looking forward to LM's update, I have to say.

 

BTW I think that FTXG on its own raises VAS by around 500 MB or something like that. I remember P3D 2.0 default gave me VAS of around 1.7 after startup and with FTXG in that same situation it was around 2.1 or so. Of course this does depend on the location.

 

 

 

 

The only thing that has been fixed is the installer (causing some default textures to not be overwritten). As far as bugs and P3D compatibility goes NOTHING has been fixed yet…

 

Standard FSX DX9 with 8xSSAA roughly same settings as the rest of the tests in the first screenshot. The rest are P3D.

 

 

But in the mean time, why can't you turn on Volumetric Fog if that solves the problem? 

 

Because right now, from the standpoint of performance, that's like tying an anchor around your neck and then jumping off the boat and trying to swim.  Totally kills performance in cloudy or overcast conditions.  It's possible that ATI cards do better with this, and I'm thinking about a switch, but for the moment, for NVidia users, volumetric fog is one of the surest ways to cut your framerates in half or worse.  Sad but true.  

 

EDIT: Rob, I recall (and see from your profile) that you're a Titan user.  It's likely your Titan is handling volumetric fog better than my 680.  Cvearl is among the most convincing advocates for the superiority of ATI performance in P3D V2.  I'm listening.  

Edited December 13, 201312 yr by Alan_A

Because right now, from the standpoint of performance, that's like tying an anchor around your neck and then jumping off the boat and trying to swim.  Totally kills performance in cloudy or overcast conditions.  It's possible that ATI cards do better with this, and I'm thinking about a switch, but for the moment, for NVidia users, volumetric fog is one of the surest ways to cut your framerates in half or worse.  Sad but true.  

 

EDIT: Rob, I recall (and see from your profile) that you're a Titan user.  It's likely your Titan is handling volumetric fog better than my 680.  Cvearl is among the most convincing advocates for the superiority of ATI performance in P3D V2.  I'm listening.  

That's odd because I see no change in fps or smoothness with the volumetric Fog activated. I was using OPUS this morning and PNW was fogged in and I still had by 28-30 fps. I do not have ftxg, so maybe the degradation has something to do with ftxg.

 

Bob

 

Bob

 

 

That's odd because I see no change in fps or smoothness with the volumetric Fog activated.

 

Here's one thread about it.  Earlier there was this one, where Jean-Paul (in post #29) first suggested that volumetric fog might be the issue.  But you raise an interesting point - I wonder if there might be an interaction between FTXG and the fog setting.  I'm tempted to uninstall FTXG, just to test.  I'll try to report back later if I get the opportunity.  If someone else gets to it first, please feel free to chime in.  

 

 

for NVidia users, volumetric fog is one of the surest ways to cut your framerates in half or worse.  Sad but true.  

 

Interesting ... I'll have to try and test volumetric fog On/Off again -- I tested this early on (day 1 of release) and didn't notice a difference with Volumetric fog on or off ... and I've done plenty of video's with lots of clouds/ligthening ... cloud draw distance will make a slight impact -- going from 80mi to 110mi I get about 2 fps hit.  But will give it another test tonight.

My brief time with it I never noticed the fog doing much of anything on performance.. 

 

I'm itching to repurchase it just to tinker but... Resisting....Spending...Money....

I am absolutely staggered and amazed at the amount of posts, I mean dozens of them, where guys are having problems with P3D. It's not just one or two small things, I mean we are talking big deals, loads of threads, someone somewhere can't get the darn thing to work acceptably. For crying out loud, what were all the bloody beta testers doing for all this time that so many of them let so many issues through the loop? I'm not talking about just this one issue but all the issues that so many are reporting.

But Howard. its the greatest thing since flowing water. According to some.