Jump to content

BimmerCop

Commercial Member
  • Content Count

    1,420
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by BimmerCop

  1. What you mean by instruments looking "crumpled"? I have my P3D setup with WideViewAspect=True and zoom of 1.0 Even with NO MSAA/SSAA, my instruments look sharp and clear at that zoom setting.
  2. You need to set the AI Traffic slider INSIDE the sim (FSX or P3D) to NONE and control how much AI traffic you want by setting it via the slider inside VOXATC Settings. Once you enable VoxATC after loading a flightplan, you will see and AI traffic being controlled by VoxATC.
  3. Oh, I see. In my case, I couldn't care less how my aircraft looks on the outside. I use my sim for flying from within the VC and don't worry much about contemplating the aircraft from the outside. What I am really concerned about is the shimmering of the runway, taxiways and airports/3D objects in general. Especially the runways and taxiways. I guess for my needs, I should just stick with SSAA and MSAA at 4x and leave the nvidia control panel and NI to default, untweaked values. I will try MSAA 8x and SSAA 8x next. Probably tomorrow, I have to hit the sack now. Have a good night, buddy. I will let you know how that goes tomorrow.
  4. Steve, to throw more into the mix and please don't send me to the link! LOL I am currently doing a test by having my nVidia Control Panel and NI P3D settings all default. Factory defaults, no tweaking. Then I went ahead and selected FXAA = OFF and MSAA = 4 within the P3D settings. Finally, I went into the prepar3d.cfg file and made SSAA = 4. The results are awesome! I am getting almost the same image quality with these settings as I was getting with DSR 4x/33% at almost TWICE the FPS I was getting with DSR! Is this even possible? Is SSAA inside the prepared.cfg file the same thing as SGSS 4x? Or do I still need to go with the settings at "The Link" alongside with the settings I posted above? BTW, I am using the new 344.48 drivers...
  5. Steve, I think you need to put that link in your signature! LOL ;-)
  6. Richard, beautiful shots!!! Can you post one from inside the VC with heavy rain coming down and flying above 150 kts? Is the tunnel effect present? I can't stand that effect in P3D. Feels like I'm flying the Millennium Falcon getting ready to go into hyperdrive!
  7. Steve, VoxATC uses the Level-D NavData from Navigraph, and I have the latest (1411 cycle) installed.
  8. Hey guys, thanks for helping me out with this. Steve, the aircraft is the Aerosoft A318/A319. I already uninstalled the RAAS addon that comes with the A318 because I also noticed that one of my previous CTD was caused by RAAS and according to Rob Ainscough, RAAS uses stereo audio which conflicts with P3D. FS2Crew has been notified about this and we are still waiting on them to address that issue. FWIW, I also use VoxATC. Could this addon be calling for that mstext40.dll?
  9. Steve, this is what I was referring to, when I said I wanted to give your settings a try: "How should I now setup my graphics within P3D as far as the built-in FXAA, AF, MSAA, Vsync and FPS limiter settings are concerned?"... Now that I have setup my NI profile, I want to make sure I have the settings within P3D, correctly configured. I know the MSAA setting within P3D should match what I have set inside NI, which in my case is 4x. How about Vsync and the FPS slider? I currently have it set at 30 FPS. Do I need to enable Vsync and triple buffering within P3D? Thanks in advance... PS. Jim, those are terrific shots!!!
  10. This afternoon while on a flight from TFFR to KMCO, I got a CTD and event viewer had this error logged: Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3 Faulting module name: mstext40.dll, version: 4.0.9756.0, time stamp: 0x49246e49 Exception code: 0xc0000005 Fault offset: 0x0000373c Faulting process id: 0x3c8 Faulting application start time: 0x01cfeb0dcdd5b132 Faulting application path: E:\P3D\Prepar3D.exe Faulting module path: C:\Windows\SysWOW64\mstext40.dll Report Id: 3dfb0759-5716-11e4-8a8e-10bf487dc342 I restarted my PC, setup my flight again and 2 hours into the flight, bam! Another CTD and upon viewing of the error log, it once again had mstext40.dll as the culprit. Any ideas on what the issue could be? Is it really an issue with mstext40.dll? Any help would be appreciated before I slam this keyboard. :( CTDs are so frustrating!
  11. Hello Steve, I followed Jim's OP and I must say that the difference in quality to my stock install was day and night! Most of the shimmering was gone, albeit you can still spot some depending on camera angle and such. But me being the compulsive tweaker, I want to give your settings a try as well. I setup my NI settings according to the image you have posted for P3D v2 here: http://www.codelegend.com/graphics/nvidiainspectorsettingsp3d2dx11.jpg How should I now setup my graphics within P3D as far as the built-in FXAA, AF, MSAA, Vsync and FPS limiter settings are concerned? Thanks in advance!
  12. WOW Jim, thanks for taking the time to post all these settings! I really appreciate it, buddy! :-)
  13. Jim, I checked out the link you gave me but it only has NI settings. I'm also interested in P3D in game settings. Can you share those with us?
  14. Thanks Jim, gonna give it a shot because the shimmering is really driving me nuts!
  15. Hi Jim, can you post your P3D in game settings? Thanks, brother!
  16. Sorry for the late reply, but yes. I chose 3840x2160 and haven't looked back. P3D is performing like a charm, now!
  17. Beautiful shot!!! You don't mind sharing your P3D and ASN settings?
  18. I have to say this DSR tweak has made a positive impact on my P3D. I would say, an extremely positive one! Keep in mind that I am using a 46" Samsung LED HDTV with a native resolution of 1920x1080 and I'm sitting about 3-4' from the TV, so this screen size at 1080 does not scream sharpness. Now, I have enabled DSR Factor x4 and the difference is DAY AND NIGHT! Now I can easily read all the VC gauges without any issues. Everything looks very sharp and clean. I also knocked down the AA within P3D to 2X, disabled VSync and set my FPS slider to unlimited. Result? Butter! It looks nothing like before. My TV now looks as sharp as my Dell 24" 1920x1200 monitor! Performance wise, I am averaging 30+ with Rob Ainscough's 4K settings for P3D 2.4, except that I dropped AA to 2X. My CPU is an i7-3770K @ 4.7GHz and my videocard is an eVGA GTX680+ 4GB @ 1.29GHz core/6GHz memory clock.
  19. I have to say this DSR tweak has made a positive impact on my P3D. I would say, an extremely positive one! Keep in mind that I am using a 46" Samsung LED HDTV with a native resolution of 1920x1080 and I'm sitting about 3-4' from the TV, so this screen size at 1080 does not scream sharpness. Now, I have enabled DSR Factor x4 and the difference is DAY AND NIGHT! Now I can easily read all the VC gauges without any issues. Everything looks very sharp and clean. I also knocked down the AA within P3D to 2X, disabled VSync and set my FPS slider to unlimited. Result? Butter! It looks nothing like before. My TV now looks as sharp as my Dell 24" 1920x1200 monitor! Performance wise, I am averaging 30+ with Rob Ainscough's 4K settings for P3D 2.4, except that I dropped AA to 2X. My CPU is an i7-3770K @ 4.7GHz and my videocard is an eVGA GTX680+ 4GB @ 1.29GHz core/6GHz memory clock. Thanks again for posting this, Richard!
  20. Sweet! As soon as I land my current flightt, I will guve this a shot.
  21. Gorgeous shot, Rich!!! Quick question... I have an i7-3770K @ 4.7GHz, 8GB 2400MHz RAM and a GTX680+ 4GB OC'ed to 1.29GHz. Currenty running latest nVidia drivers with P3D 2.4. Can I implement this tweak? PS. My monitor is a 46" Samsung LED @ 1920x1080...
  22. Sorry to revive an old thread, but if I use VoxATC with MTX, do I still need to use the bridge file?
  23. Rob, that was a great video! Thanks for sharing. Quick question though... Do you mind sharing your P3D 2.3 settings with us? A screenshot of each settings window would be awesome. Thanks in advance!
×
×
  • Create New...