Mephic

Do you get those errors before or after loading appropriate preset within Reshade?

The explanation sounds a bit like : "we made a real VAS hog and due to that it's P3d fault it won't work". Reminds me of Concorde. Anyway if they released it for FSX dx9 then I don't see a reason why vas management would be showstopper here. I am on HF2 of 3.4 and apart from my 50 mb of free vas chasing campaign I can't say that this hotfix has some extensive vas issues. Spawned PMDG triple 7 with 35% Mt 6 jet traffic on Flighteam KIAD and sitting there for 1 hour never got over 3.2 gig. There must be something really wrong with the bus. That just convinces me to stick to PMDG and Aerosoft jets.

Do you use latest ReShade? Did you choose Dx10 in installation menu?

Main risk is if you have add on version without backwards compatibility you would have to reinstall older version. Someone stated in hf2 topic he reverted client only I'll try same

And if you revert you get dxgi.dll error again?

I start to think that problem of VAS is somewhere in scenery update, yet they tried to fix it by amending something in client. Reason I think like that is that on my end: 3.35 - no VAS issues went to 3.4 by updating all packages 3.4 - VAS issues went to 3.4 HF 2 by updating client only 3.4 Hotfix 2 - VAS issues but less significant than in 3.4 I am going to reinstall 3.35 scenery, while staying with 3.4 HF2 for client and see what happens. Worst case scenario I break my sim, best case scenario I should have no VAS issues anymore.

Thanks What Windows version are you on? Try to rename dxgi.dll file created by reshade to d3d10.dll (if you are using DX 10 scenery fixer). Make backup of any files you alter!

Just a thought regarding VAS: is there anyone who has VAS issues but updated only client to 3.4 while staying with 3.3 or previous with other modules? (E.g. scenery) Reason why I ask is I saw some post on p3d forum of a person who claims he has no VAS issues but he updated client only when going from 3.3. Maybe this will help to point out the issue

Funny thing is that in case of NGX it's always spot on (n1% matches fmc). So I still think there is just sth wrong with triple 7 profile.

I'm no rw pilot but isn't climb gradient requirement part of charts and are we not able to calculate it? Let's say I need 7% climb gradient and climb at 160 knots so my fpm should be roughly 1120? Now I am not sure how to check if we can meet this requirement (maybe would make sense to set custom way point with minimum altitude restriction and if aircraft couldn't make it FMC would give this info? That's just a guess :-), but yeah Topcat would definitely be better in this area. I just don't get it why it does not match fmc calculations for n1.

So you did not have to uninstall any add on, correct?

It's the coolest thing about this preset - looks best when inside, where you actually spend most of time as pilot

As usual - big thanks to Pe11e for his amazing URP 1.0 Prologue preset. Sim: P3D 3.4 HF2 Addons: 737 NGX Drzewiecki EPKT PTA 2.2 Reshade v3 AS16+ASCA+ENVTEX+REX4+REX WAHD FS Global 2010 Mesh ORBX Global, Vector, Landclass PrecipitFX+NGX immerssion GSX LOWW cruising EPKT1 EPKT2 Leaving Poland Approaching EDDM Safe and smooth <200 FPM landing Proud pilot!

Do we know what in 3.4 actually introduced VAS problems? Client update or scenery update? I updated all modules when going from 3.35 to 3.4 and only client module when going to HF 2. If I would need to revert (although currently I think I'm fine VAS wise, nevertheless I have not tried heaviest scenarios yet) and I would revert client only, would it be an issue?

Fantastic! Thank you. I guess next month I'll get myself 777-300 + TOPER package.

Hi all Is there any new product on the market which allows us to calculate takeoff performance without too much hassle? I have TOPCAT, but that one only works for NGX in my case. 777-200 profile seems to be broken as the outcome is always nowhere near what FMC shows when I enter same values. Anyone tried TOPER? Also, I plan to get 777-300 expansion, so I guess TOPER would cover it too. My only concern is it's not calculating derates, only temps?

What's the fault module name when you crash? You should see it in Appcrashview when you have CTD.

I used their lights patch for EDDL - works great and since Aerosoft does not care about older sceneries, it's our best shot. Try to use post code in 5 digits format to "purchase"

Although be warned, that installation of MyTraffic 6 is a chore as it does not install to P3Dv3 with installer (or at least didn't in my and some other users case). Manual installation is a real pain and when performing it you start to wonder why you put so much money into addon which does not install properly to sim without manual tweaking. Also, from what I've seen UT2 and WOAI have much better models than MT6. I chose MT6 as I supposed it will work out of the box.

Can you record 2 or 3 movies showing this issue on various aircrafts? I find it hard to believe that it's not flight model nor hardware related. Anyway - would help to see how serious the problem actually is. If it is not engine thrust difference, brake lock difference, poor calibration, hardware issue, sh#$%# flight model, then last thing which comes to mind is delete P3D CFG and let it rebuild. Also, what addons do you have installed? Did you try vanilla sim?

Not sure what above post has got to do with this topic. Anyway - Mogwaisoft Shade is your best shot here. You can also try to use DX 10 Scenery Fixer along with Reshade (worked fine in the past as I recall). All in all - you won't get as much eye candy as with P3D but that will be something to start with. On the other hand I would really think twice before investing more in FSX. (not to start any unnecessary discussion here, just a thought depending on your future plans)

First issue (quite severe since I fly NGX) - on first load I always get no snow textures, although I load winter time. If I go to change time option and decide to push it forward e.g. 1 hour snow textures become visible but sim reloads which causes standard issues with NGX. FIXED by modifying texture resolution option in sim to 7 cm (had 15 cm) - WEIRD It's back again. So it's not resolution related, it's just random FIX no. 2 (this time seems to really work) - choose "Use system time for default scenario" option in P3D options screen (general). Found this workaround on P3D forum.

It absolutely is. Adds to immerssion and I think most people don't like reshade because it's a bit harder to set up than PTA plug (load profile) and play. With your readme - it was super easy.

After 1 hour of testing I have to say - I am SO IMPRESSED. You took the sim to next level (again). Best with reshade ON. Fantastic work!

Does fsuipc act before 100% is loaded to sim or 100% is loaded and then it removes? Reason I ask is VAS impact. I think that standard traffic optimizer acts after traffic is injected.