EVERY right click does a normal P3D exit.

So this is supposed to happen?

 

 

The shame is that FSX which used to run quite well for me is a stuttery mess lately

 

Do you perhaps get a connection, maybe just a tiny little one?

Yep, see message a couple above yours, solved issue.  RTFM or bad assumption on my part.

 

I caught that Rob and I wasn't directing that last comment at you personally, it just seems from reading on the various forums that people seem generally reluctant to delete the recommended program generated files and it seems to be causing a number of problems. LM should have included a routine in the patch installer that just wiped those files out automatically IMHO.

 

Jim

Has anyone tried SweetFX or ENB with 2.1? 

Did someone try if Qualitywings BAE 146 still works fine in version 2.1?

 

Have been planning to get that aircraft while waiting for the NGX but I also read someone in this thread said the current NGX now works in this new version of P3D. Could someone else confirm that?

I have been using QW BAe with the patch and it works wonderfully. Only two minor issues (for me anyhow):

 

1 - the tires on outside view appear submerged into the tarmac by about 1/4.

2 - flying at night, VC view does not show outside taxi/landing lights

 

Overall, the patch was a disappointment at first. I was getting 1/2 the frame rates. Then I read about getting rid of affinity mask AND maxing out frames and behold: flying out of KJFK with 100% traffic - I even upped the settings to 90%ish - (aside from shadowing) and the frames are up.

 

Seems the VC view takes more of a hit than pre-patch but overall - FANTASTIC JOB LM!

I have been using QW BAe with the patch and it works wonderfully. Only two minor issues (for me anyhow):

 

1 - the tires on outside view appear submerged into the tarmac by about 1/4.

2 - flying at night, VC view does not show outside taxi/landing lights

 

Overall, the patch was a disappointment at first. I was getting 1/2 the frame rates. Then I read about getting rid of affinity mask AND maxing out frames and behold: flying out of KJFK with 100% traffic - I even upped the settings to 90%ish - (aside from shadowing) and the frames are up.

 

Seems the VC view takes more of a hit than pre-patch but overall - FANTASTIC JOB LM!

Thanks for the input!

 

I'm a bit concerned though about the landing and taxi lights not working at night from the v/c view. To me that is an issue of significance not being able to see the ground closest in front of you lit up?

 

 

I'm a bit concerned though about the landing and taxi lights not working at night from the v/c view. To me that is an issue of significance not being able to see the ground closest in front of you lit up?

 

Ya I know what you mean. But right now I have to say the advantages to the patch outweigh the disadvantages. And who knows, perhaps your system's setting may not have that problem. Could be from the various add-ons I'm running that gives me that issue.

Ya I know what you mean. But right now I have to say the advantages to the patch outweigh the disadvantages. And who knows, perhaps your system's setting may not have that problem. Could be from the various add-ons I'm running that gives me that issue.

So you didn't see this issue before the update?

 

Maybe someone else could confirm if they see the same thing after the update?

Do you perhaps get a connection, maybe just a tiny little one?

 

Not really.  P3Dv2 was quite smooth while FSX stuttered a good bit.  Now with v2.1, P3D stutters as well.  

So you didn't see this issue before the update?

 

Maybe someone else could confirm if they see the same thing after the update?

That's a good point: pre-patch, the light was dim but it was there. It would be nice to get other members' input.

That message is misleading (and I wish L-M had taken my suggestion to change it)...

 

...as it isn't your computer's memory (RAM) that's run out of space, it is your 4GB slice of VAS (Virtual Address Space) that's hit the limit!

 

I suggested that they change that message to read: "your computer has run out of virtual address space" as that is precisely what has happened. :Whistle:

 

 

Yeah i'm aware its VAS.. its just odd.. default initial flight that loads.. leave on full throttle.. come back in 10 minutes to have run out VAS space.. nothing was tweaked at that point.. just initial defaults with 2.1.. 2.0 this never occurred for me.

That's a good point: pre-patch, the light was dim but it was there. It would be nice to get other members' input.

I also have no landing or taxi lights with the qw 146. My wheels are also submerged on the runway. I also have this problem with the qw 757.

 

I'm sure quality wings will release a SP soon, at least I hope they do.

I also have no landing or taxi lights with the qw 146. My wheels are also submerged on the runway. I also have this problem with the qw 757.

 

I'm sure quality wings will release a SP soon, at least I hope they do.

Thanks for the confirmation, I think I'll head over to QW's support forum and ask about this.

The patch has been completely trouble free for me.

 

Everything seems a little smoother overall. I'm a happy boy. 

 

Hope you guys having issues can get them sorted out quickly and enjoy some flying time.

 

 

I do keep my FS drive set-up like my C: drive with a Program Files (x86) folder, as generally all I need do is change the drive letter when installing, and everything ends up in the same folder configuration... though I doubt it makes any difference as long as the reg path is intact as far as the patch goes... it worked correctly anyway.

 

Isn't the conventional wisdom to avoid installing P3D in a subfolder of Program Files (x86)?  I've never followed this advise in either FSX nor P3D V2 and I have had no problems w/ anything so far w/ P3D V2.  I have the usual cadre of higher resolution mesh, FTXG, REX4, some nice add ons thru the Estonia Migration Tool.  Anyway I guess the conventional wisdom doesn't apply to every possible configuration, or perhaps the issue just isn't really that critical most of the time.  Or I could just be lucky!