KrisJ

The settings i listed above are ASN. In P3D v3 i have detailed clouds set to ON and maximum density set. In REX 4 TD w/SC i have 2048 size set for upper level clouds.

Jim, is your question to me? If so i do not understand what do you mean by "where are all of the settings quoted above". Kris

ASN with latest beta. Default settings except maximum upper visibility (115), max cloud draw (120) and enhanced overcast coverage (on). Rgdrs, Kris

On sunday i made egll epwa flight crusing at 33000. Somewhere over Germany around noon (GTC) i climbed to 35000 to omit a building cumulonimbus that definitelly reached 34000.

361.43 Do you use nVidia inspector?

1. Download latest beta for ASN from their forum and install it. 2. Download scenery.msi installer and 6 cab files from Prepar3D website and reinstall it. 3. Restore original textures via REX interface (i assume you made the backup). 4. See if you have your clouds back. This is what i did and it restored them. 5. If you have it you can now play with REX. Rgdrs, Kris

Try different drivers, also some older ones but not older that P3D. Each time you change drivers do a "clean install" - you will find guides in the Internet. Does it happen only with PT Tu154?

No problem. If you describe the problem with resizing crash maybe i will be able to help. What is the error message? What if you switch to full screen? Kris

I have it fully working In P3D v3. I am using FSX version 1.3 plus 1.3.1 patch. Obviously we are talking about Tu154b2, not the M version as PT has never built Tu154M for FSX. I am using oryginal installers only. No migration tools needed. Make sure your default saved flight is some simple GA aircraft parked with all systems off and view is set on 2D (PT Tu154b2 must load into 2D view to properly initialize systems). Let me know if it works. Kris

Thanks for prompt response Vic!

Hi, Question. If i have Windows on C drive and P3D v3 on other drive and I make Windows reinstall after formatting C drive will i need to: 1. Completly reinstall P3D and all addons? 2. Reinstall just P3D and addons will work? 3. Do nothing and P3D and addons will work as it sould? So its a question about Windows registy impact of P3D v3 installation and of addons for it. An advise will be appreciated! Regards, Kris

I will. For sure.

I installed final release version and replaced dxgi only (from 0.18 - just checked it) and it works (effects are applied). So its true.

I think it is early 0.19 beta that works for me. But every system is different. Try the last pre-final beta. If it crashes try the previous one and so on untill you get the one that works for you. Its just a matter of changing dxgi dll, you dont need to replace whole package each time.

Kyle, one of the pre-release beta versions of Reshade/ SFX 2.0 works. The only issue i have is that it minimise FSX to desktop each time IT refreshes the effects. It happens more or less once per hour of flight. This is not CTD and i am able to maximise the FSX bacik to full screen easily.

Ok, thanks anyway!

Got it. Is there any thread you can point me to where a discussion is held and maybe a solution described?

Steve, i think SweetFX 2.0 doesnt have injector dll file. It puts some .fx files and dxgi.dll into FSX main directory and SweetFX folder. Unless i am unaware of somerhing?

Hi, i am looking for help. I posted it also on SweetFX forum but maybe you Steve already know the problem and resolution? Basicaly the question is: is will SweetFX work with Fixer (v11)? So far i have been using succesfully SFX 1.5 + FlightFX. No issues and great visual experience. Now i decided to move to SFX 2.0 and i cannot start FSX up. It crashes few seconds after launching fsx.exe. My system: W7 64bit, GeForce GTX970, FSX Acceleration, DX10 mode, Steve's DX10 Fixer, nVidia inspector. Any advise how to fix it would be highly appreciated. Kind regards, Kris

Hi, i am looking for help. So far i have been using succesfully SFX 1.5 + FlightFX. No issues and great visual experience. Now i decided to move to SFX 2.0 and i cannot start FSX up. It crashes few seconds after launching fsx.exe. I tried both d9 dll and dxgi one. I deleted App data/Roaming/Microsoft/FSX folder and recreated it. I run fsx.exe in admin mode. Nothing helps. My system: W7 64bit, GTX970, FSX Acceleration, DX10 mode, Steve's DX10 Fixer, nVidia inspector. Any advise how to fix it would be highly appreciated. Kind regards, Kris

Hi, since switching to DX10 my WOAI aircraft are sometimes invisible. I can only see their lights (nav, beacon, strobe, landing). This happenes randomly. But when happenes they do not appear theough entire game sesssion. It makes me thinking about switching to some commercial traffic addons as i wont come back to DX9 anymore since i have Steve's fixer. However any help will be appreciated. Rgdrs, K

Thanks mjr. What you say probably refers to my Tu134 problem. As in case of Il18 i can see from various screenshots in the web that glass transparency issue can be solved. And I guess that is a matter of proper texture file conversion. The question is which ones? Or maybe the solution is different?

Steve, I read the thread. It is said there to create an Alpha template and save it as a DXT5.bmp. But I cannot locate which texture file should be converted (Yes, the windshield one but cannot see it anywhere in the texture folder). Can you point me to the right ones? Legacy settings: all ticked What do you mean by diagnostic? The Diagnostic says that: - Legacy A/C self shadow is set - Legacy A/C Force shadow is set - 8bit fix is on - HD shadows is set. In the Legacy section the reflections are enabled.

Steve, it did not help... See linked image: https://drive.google.com/file/d/0B_GJOP5eUxOSdkJWYVREcTJ0MjA/view?usp=sharing Any idea why?

No... :unsure: Will do it now and try. Thanks!