LOL, just having some fun there.  Your posts are always appreciated.

 

Jeff

VAS usage is reduced.

 

 

I dread to raise the "V" word (or acronym!), but are people consistently seeing a VAS usage decrease? After a client only update, I reran a 'VAS challenging' flight, but one that I could always complete, from Flytampa CYYZ to FSDreamteam KORD in the PMDG NGX. This time the free VAS started off lower in CYYZ, and did not seem to increase as a result of VAS recovery by P3D, if anything the opposite. With only 500M free over Michigan, there was no way that I was going to be able to land at KORD without an OOM. So I bailed out, and have reverted to 3.1.

 

A sample size of one person, I know, but I would be interested in whether my experience is atypical. 

After a client only update, I reran a 'VAS challenging' flight, but one that I could always complete, from Flytampa CYYZ to FSDreamteam KORD in the PMDG NGX. This time the free VAS started off lower in CYYZ, and did not seem to increase as a result of VAS recovery by P3D, if anything the opposite.

 

Was that comparison made ceteris paribus? I mean with the same scenario, weather, date and time, traffic, route, pace etc.?

Was that comparison made ceteris paribus? I mean with the same scenario, weather, date and time, traffic, route, pace etc.?

 

More or less. Same time of day, so same AI generated, same route, a slightly later date with weather much less cloudy the second time, so clouds wouldn't be a factor.

 

I was running OpusFSI's pre-3.2 version for the cameras only (they have just now released a 3.2 version), which might have been a factor, although not an obvious one.

I've upgraded to P3D v3.2 using the client only installer. All is well, but I've noticed that the PRO-ATC X in flight menu cannot be called up in my PMDG 737 ngx & 777 products. The flight plan loads ok, but when I press "1" on the keyboard to access the PRO-ATC X in flight menu, nothing happens...the menu does not display. I've searched the forums and couldn't find any ideas. Have any other users experienced this problem? I don't know whether this is a PMDG, PRO-ATC or P3D issue.

I've upgraded to P3D v3.2 using the client only installer. All is well, but I've noticed that the PRO-ATC X in flight menu cannot be called up in my PMDG 737 ngx & 777 products. The flight plan loads ok, but when I press "1" on the keyboard to access the PRO-ATC X in flight menu, nothing happens...the menu does not display. I've searched the forums and couldn't find any ideas. Have any other users experienced this problem? I don't know whether this is a PMDG, PRO-ATC or P3D issue.

 

You have to update content as well. Same problem as with GSX and SODE.

You have to update content as well. Same problem as with GSX and SODE.

Thanks for the quick response.....So obviously I download the content.msi. Must I also download the individual cont1.cab file also?

I also updated now and on my machine (R9 390; i6500k) I got bad Micro stutters (had them befor but not this Bad). I ended up playing with my in-Game settings and figured out that switching off the "scenery Shadow Cast"- slider fixed this problem/decreased the micro stutters. Now I don't have any shadows from mountains or something like this but for me it is a nice to have setting but i am also OK not using it.

 

Also since the update I am not abel anymore to open up the ASN in-game menu. Did someone else discovered this problem? My ASN is updated to the last beta build.

Anyone know if asn has been updated? Can't find it on their site.

 

Thanks

Anyone know if asn has been updated? Can't find it on their site.

Thanks

You have to go to there support forum. Fortunately you don't need to sign in to be allowed to download it.

Anyone know if asn has been updated? Can't find it on their site.

Thanks

http://nimbus.hifitechinc.com/laser/ASNext_P3D_Update_B5913.zip

Thanks for the quick response.....So obviously I download the content.msi. Must I also download the individual cont1.cab file also?

Yes.

Pete try this may help not seeing a lot on the subject

 

http://forum.aerosoft.com/index.php?/topic/99376-mega-airport-heathrow-xtended-texture-problem/

 

Yes. Actually I've gone through most of the references for Aerosoft Heathrow on both Aerosoft and Orbx support forums. So far nothing works.

 

Thanks anyway,

Pete

Try putting EGLL above all Orbx library entries.  Also, did you run the Vector configuration tool and execute and apply airport exceptions?

 

EGLL is now at the top priority. No difference. UK2000 Heathrow is fine, it's just that the Aerosoft one is twice as fast and allows me to set AI traffic to a realistic level (ie high).

 

After scanning, the Vector config too lists a load of airports it will make exceptoins for, including a huge number of obscure US ones which is odd as I only have European airport addons! But it doesn't list EGLL, and you can't make it accept EGLL by typing it in the box above the list -- that box seems only to be a filter for the list.

 

Thanks anyway,

 

Pete

Don't know if you saw the thread/post that suggests moving or deleting the CVX_FTX_EU_ENG_EGLL_Grass.BGL file.

 

Might help.

 

Yes, but I am not using Orbx FTX England. Tried it when it first came out, but didn't find it made things much better than the Global landclass and textures when flying airliners, which is all I do, and it gave immense problems anyway with most UK2000 airports and I had no patience to go through every one.

 

Incidentally, I've even tried with none of the OLC EUR layers active and it's no dfferent, so it's not a file in those.

 

Pete

http://nimbus.hifitechinc.com/laser/ASNext_P3D_Update_B5913.zip

 

Thank you

Pete -  if you have any traffic programs like MyTraffic - disable their specific bgl and see if that helps.

 

 

Vic