Jump to content

InTheAir

Frozen-Inactivity
  • Content Count

    390
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by InTheAir

  1. Quite amazing indeed. Release day will be glorious..
  2. I was giggling while reading RSR's post from both amusement and giddiness! Not sure what that sounded like, glad nobody was around to hear it.
  3. InTheAir

    Sunset descent

    NICE! What a beaut.
  4. I was having this same question pop up the other day, thanks for clarifying Pete!! To the OP.
  5. Thanks for the banner image Ryan. This is exactly how to do it, remove all tags and only use the link to the image. http://downloads.precisionmanuals.com/images/forum/Boeing777_Banner_Pilot.jpg Another way to do it is to click the banner and click save... It'll open in a new window, Right-clk the image and "Copy" then you can paste it into the Signature edit area. This image was added by the same method, Copy then paste,
  6. I'll always be a Boeing guy but I have to say I really like the A350.
  7. That's something else, I've never heard of that. Have you tried visiting the SweetFX authors forum thread to ask there? Best advice I can give is to troubleshoot sweetFX settings to see if they are the culprit. Do that and also try starting with a fresh Nvidia Inspector profile. Enable each tweak one by one until you find the one responsible... assuming you get it to work without the FPS hit.
  8. Thanks for the update Capt. Robert. This is a very cool feature and I will make full use of it's awesomeness! :t0106:
  9. Did you install SP1C for both the base and expansion? https://www.precisionmanuals.com/pages/downloads/updates.html
  10. Happy to hear you had a successful test flight Ryan. I don't mind the screen shots, keep em coming if you ask me!
  11. There are a couple things you can do. 1. backup all NV Inspector profiles you have modified and install NVidia drivers "Clean" resetting all profiles during installation. Then modify the profile. I did this recently and it works great... 2. Delete your "MS Flight Simulator X" NV Inspector profile (back up if you want) and create a new profile, name it FSX then click the "Add Application to Current Profile" button and add FSX to it. This way, when new drivers are installed it will not cause issues.. (Shouldn't anyway) Now make all the Inspector tweaks. Anti-Aliasing should always be "unchecked" in FSX graphics settings in order for the NV Inspector Anti-Aliasing settings to work. My settings aren't the best, they work for me and can probably be improved. Going to play around with some other settings to see if anything else can be done. These settings may not work for everyone so play around with the Aliasing setting until you get a good balance of what looks good to your eye.
  12. For anyone interested. here's my latest SweetFX files and settings (Using NV drivers 320.49) http://virtual-aviation.org/main/images/jonp/avsim/fsx_settings/vaejonp-Latest_SweetFX-1.4-%5BGuru3D.com%5D.zip For this version, SMAA is disabled, HDR and some other stuff was tweaked. After some recent testing (my eyes aren't what they used to be) SweetFX's SMAA made the edges worse when coupled with my NV Inspector settings. Let me know what you think if you use this. Here's a shot with all FSX graphics sliders maxed except Autogen is at "Very Dense" and ground scenery shadows enabled..
  13. The higher frequency is more important when overclocking. I'm not an OCing expert by any means but can say from experience. I personally wouldn't get either of the choices you have. I have i5 3570K @ 4.4Ghz on air with this RAM and mobo comb: G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 2400 (Cas Latency 10) (Timing 10-12-12-31) GIGABYTE GA-Z77X-UD3H For the overclocking, all I did was manually configure the RAM voltage and select a profile built-in to the BIOS then bump up the CPU multiplier till I hit 4.4Ghz. Been very stable. I can't recommend G.Skill RAM enough. I've used it in every build of mine and friends for the last 6 years or so.
  14. I've been using Vroute Premium for a while now and like it's features. You can try the free version to see if it's for you. $30 if you decide to buy. http://www.vroute.net/ http://www.simroutes.com is a free website that has a large database of FP's as well as the ability to generate your own and they can be downloaded for most any aircraft including PMDG.
  15. Flew into Denver a month ago, nice airport. Will be picking this up for sure.
  16. Go to the REX forums and register and search for a solution, if you can't find one start a new topic. Their support is very good and is the best place for help with REX.
  17. I don't have P3d yet so I cannot test this. I can say however that in FSX if Anti-Aliasing is enabled in graphics settings SweetFX will not work (using SMAA). It'll load but will not modify the shaders. By default I believe SweetFX uses SMAA, that could be where the issue is. Try copying over the d3d9.dll for FXAA and see if that works.. Located here: FSX\SweetFX\dlls\FXAA DX9 dll\.
  18. Same here. I think I made very similar changes to you and get good results. The biggest frame killer for me was ground scenery shadows after making the necessary tweaks to both sceneries. AlaskaModels2 is the "Environmental Preset" I loaded in the Ultimate Alaska setup tool which gives great performance. This is with MyTraffic 2013 (@ 50%), Alaska Airlines NGX B737, REX OD/HD 2048 textures, Alaska X, and Anchorage X: (frames anywhere from 22-27) and they get better during taxiing and departure. At the gate in the NGX VC FPS will dip down to 17 which is fine with me while parked.
  19. Are you using FXAA or SMAA SweetFX dll's? Make sure you have the correct dll's. If you're using SMAA try switching to FXAA. Bummer it's not working for you.
  20. If SweetFX is causing the CTD it's more than likely related to a SweetFX configuration error. Could be several things. - Check that all files associated with SweetFX are in your FSX folder - Make sure the "SweetFX_preset.txt" file (Where the settings file name is defined) points to a "SweetFX_settings.txt" file Example SweetFX_preset.txt file: #include "SweetFX_fsxDAY_settings.txt" Then I have a settings file named appropriately.
  21. With a GTX680 2GB my NvidiaInspector AA setting is at 32xS [Combined: 2x2 SS + 8x MS]. FSX looks insane. The card gets used for many other things as well. To each their own.
  22. While time stands still for the anxious customers, it fly's by for the busy developers. Maybe a little slack is deserved. I like anyone would enjoy RSR and team to be chatting our forum ears off but that would take away from their development time. Imagine that there are easily 12+ hr development days possibly more than 5 days a week.... Maybe a little time for family and friends and a life plus other business ventures... Some of you all need to be a little more realistic is all I'm trying to say. Real people equals real lives and that's probably enough about that. I have faith in this team, period. If it happens to take another year because they figured out how to incorporate the Oculus Rift or something... I'd still patiently wait but that's me. :-P haha
  23. Ryan, Nice build for your friend. I also have a CM HAF case and would buy another for my next build. Amazing quality IMO. With the prices of SSD's coming down it only makes sense to have a couple now a days for the best performance. Spinner drives are such a huge bottleneck. OCZ VERTEX4 256GB Boot drive with Win 7 64 Ultimate Mushkin MKNSSDCR 240GB dedicated for FSX Not the highest quality SSD's but have been fast and flawless so far. I'm planning on adding a sata III card soon seeings how my Z77 board only has 2 of those ports.
  24. 1) Needs a very large investment, something I do not believe kick starter would be able to generate. 2) Everything that is FSX plus true scalable multi-core support, 64bit, and GPU utilization. 3) See #2 plus a built-in multiplayer environment that is user friendly and caters to all types of flyers. Kudos to the Outerra development team, I wish them well in their endeavors.
×
×
  • Create New...