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?

Has anyone flown PNW with Orbx and do you still see those trees with building textures? Has that been fixed?

 

Hmm...

I am having a minor problem with assigning Buttons on my X-52! Had the same problem in V2.0

I think its button 27 and 28. They are two of the three on the Throttle base.

I like to the one with up arrow for incremental flap retraction and the one with the down arrow

for Incremental flap deploy.

 

I typically don't bother with the Control setup in FSX and use FSUIPC but I plan to wait for the

FSUIPC update for V2.1 Before I install.

 

It seem the that V2.1 recognizes both of these buttons as button 24

So I assign one and then when I try to assign the other is says that

button is already assigned!

 

Maybe I am doing something wrong but I recall reading better

compatibility for the X52 on the fix list.

Aint that always the case?

 

Now is that with the updater or the full (re)-installer?

 

Always something isn`t it... 

 

And yes, that is a FULL re install! 

 

 

This is of course one of the many reasons LM recommends deleting these files, not sure why folks don't heed that advice?
 
Jim

 

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

I am having a minor problem with assigning Buttons on my X-52! Had the same problem in V2.0

I think its button 27 and 28. They are two of the three on the Throttle base.

I like to the one with up arrow for incremental flap retraction and the one with the down arrow

for Incremental flap deploy.

 

I typically don't bother with the Control setup in FSX and use FSUIPC but I plan to wait for the

FSUIPC update for V2.1 Before I install.

 

It seem the that V2.1 recognizes both of these buttons as button 24

So I assign one and then when I try to assign the other is says that

button is already assigned!

 

Maybe I am doing something wrong but I recall reading better

compatibility for the X52 on the fix list.

FSUIPC has already been updated for P3D2.1

 

You can get the new version from their website

FSUIPC has already been updated for P3D2.1

 

 

 

You can get the new version from their website

 

WHAT! That was quick! :lol:

In that case let the addons begin.

 

Speaking as a simmer who had big issues with V2.0 right out of the box (granted mostly my own fault),

I am blown away by the update. Using Arwen's setting with the default flight no addon's in the VC I am getting 50fps and up

and it is smooth as glass. I have been playing with it all day and but for that one OOM with EVERYTHING MAXED OUT

it has been plan sailing and smooth as glass.

 

Time to install FSUIPC and Stick an Addon into the mix. :lol:

 

Made a video but I am not going to upload it because it suffers from video capture induced stutters which makes it pointless.

Looking forward to ShadowPlay compatibility.

I typically don't bother with the Control setup in FSX and use FSUIPC but I plan to wait for the

FSUIPC update for V2.1 Before I install.

 

 

I thought that the present version of FSUIPC 4.929 is the one that is compatible with P3d 2.1:

 

http://forum.simflight.com/topic/76269-you-must-use-fsuipc-4929-or-later-with-prepar3d-version-21/

 

4.928 also worked more or less with P3d 2.1, but it occasionally caused CTDs.

FSUIPC 4.929 it is then!

thanks for the help! :Big Grin:

If it gave a version warning then you are not using 4.929, and it wil not work properly and may cause crashes.

Oddly enough I didn't encounter any problems with the previous version, but since shutting down P3Dv2.1 I went ahead and installed 4.929 anyway, just to be on the safe side. I may simply have not tried using all of the functions available, so didn't hit any of the problematic "hooks"... B)

Regarding OOMs...while I haven't done comprehensive testing, 2.1 seems to have fixed the problem of "phantom OOMs" when the VAS counter showed 1 GB or more of free VAS. I can now fly in large cities with both autogen sliders set to very dense and not trigger an OOM. With v 2.0, I would get an OOM within 3-4 minutes. 

Installed clean full 2.1.. with only ftxg+v and rex4 textures as i did with 2.0...

 

With 2.0 i was getting 41-43 fps in fraps, with unlimited frames and the settings i have in my thread here.  (using fsmark07 test)

 

I started off with no tweaks to prepar3d.cfg and only got around 30.53 ..

 

So i thought.. ok, ill add in the tweaks to cfg as i did before and got a nice jump.. NOPE..

 

Fps with cfg tweaks only rose to 31.53.. somewhat studdery..

I'm using the same NI settings (in that thread linked) as before too..

 

Rather unhappy so far with a loss of nearly 11-12 fps all things held equal. 

 

Hopefully its something simple that needs adjusted..

I bought a month developer license so I could test 2.0 out.  Had trouble from the start.  It ran well enough on my system with pretty good settings, but I got OOM anytime I tried to fly in Orbx AU.  I'm certainly not going to fly default scenery!!  But I thought I'd wait for 2.1 and see if that got fixed.  Well, I didn't get OOMs while flying today, but there are so many other problems created now.  I'm having trouble with joystick assignments.  Some aircraft that worked before no longer do (but these are not officially supported aircraft...of course, almost none are).  I seem to have lost performance on the same settings, and there are stutters now where it used to be smooth.  

 

I don't think I'll be getting the full license.  Not sure I see this working out.  It must be frustrating for LM as well, and I suspect they aren't making a lot of profit on this.  

 

The shame is that FSX which used to run quite well for me is a stuttery mess lately (after a recent reinstall to fix incessant crashes that cropped up somehow after years of adding too much stuff to the program probably).  I've set it up just the same as before, in a much leaner version, but it sure isn't working.  I'm getting pretty frustrated with these simulation software packages I've spent a fortune on over the years.  

...come back to a message "your computer has run out of available memory" (which is crazy as i have 16GB and only about 5GB was in use, total after load)..

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:

 

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:

 

Maybe it's not that easy (or even possible) to change if it's a Windows message rather than a message from P3D?