May 10, 201313 yr Enjoy. :dance: Test just now in Orbx scenery an the test went well no crashes when going through the menu option . I haven't try the flight planning which is the one that actually gives me the crash. I wish they could be an option to setup a flight plan with out going to fsx flight plan all the time . Mr Leny CPU I7 8700K @ 5.0GHz , MOBO -Asus Maximus X Hero (WiFi AC),GPU - GTX1080 TI , RAM - CORSAIR Vengeance RGB 16GB DDR4 3600MHz SSD -Crucial MX500 1TB (P3D Install Only)OS- Samsung 960 EVO 500GB (Window 10 Pro 64)
May 10, 201313 yr Wow this tool is awesome. I had been trying to use ENB with less than stellar results (IMO) especially in relation to the VC being too dark. No such problem with this tool. Running a modified config from Adi's download. Basically kept his custom tweaks to the different options like the Curves setting. Not sure what the extra folders in the official download are for (seemed to contain copies with different sizes of the d3d9.dll) but I just used Adi's files and nothing else. Running lumasharpen, bloom, vibrance, and curves. I thought using liftgammagain (with Adi's settings) was slightly too dark at least for the OrbX NA Blue scenery but I wasn't totally decided and just left it off. My other potential setup seems to be swapping Curves for HDR but I wasn't sure I liked that blown out HDR look on the sky. The lumasharpen is awesome. Moving from default AA to using 4xS and 2xSGSS through Nvidia Inspector really cleaned up the jaggies and VC crawl I had, but also made things fuzzy. Lumasharpen cleans the fuzzy up Screenshots are from over South Africa with default textures + FSGenesis meshes. Here's my default without Here's with my SweetFX settings AMD Ryzen 9950X3D | Asrock X870E Taichi | Gigabyte Gaming OC 4090 w/EK waterblock | Full Custom Loop Cooling | Corsair Dominator Titanium DDR5-6000 | Samsung & WD NVME/SSDs | Phanteks Enthoo 719 | Seasonic Vertex Gold 1200W | Keychron Q5 Max | Corsiar Scimitar Elite SE Wireless | Honeycomb Alpha and Bravo | Logitech Pro Flight Pedals | VKB Gladiator Pro NXT L&R handed | MiniCockpit MiniFCU | Alienware AW34DWF | Asus PG279Q | Win 11 Pro
May 10, 201313 yr Btw, to get the full effect from sfx, you have to resize your images to 720p, then use sharpen edges in photoshop to bring back the lost detail. If you upload to flickr, they will do that for you. This is how all devs are making their images to show off their products in the fsx scene. New:
May 10, 201313 yr What do you mean resize to 720p? Resize them to 720px high x whatever width maintains aspect ratio? Just curious since I assumed you did that on the above image but it shows as 1024x640 when I download it. In my images I was mostly looking to show the overall picture of stock vs. sfx improvement and wasn't worried too much about detail (plus it was about 2am on a work night when I finished and took the shots lol) AMD Ryzen 9950X3D | Asrock X870E Taichi | Gigabyte Gaming OC 4090 w/EK waterblock | Full Custom Loop Cooling | Corsair Dominator Titanium DDR5-6000 | Samsung & WD NVME/SSDs | Phanteks Enthoo 719 | Seasonic Vertex Gold 1200W | Keychron Q5 Max | Corsiar Scimitar Elite SE Wireless | Honeycomb Alpha and Bravo | Logitech Pro Flight Pedals | VKB Gladiator Pro NXT L&R handed | MiniCockpit MiniFCU | Alienware AW34DWF | Asus PG279Q | Win 11 Pro
May 10, 201313 yr My images are downsized to 1280x800. Flickr free account limits that size to 1024, but it remains looking the same because it's not as much as the 50% cut from 1080/1200p. In photoshop, when you enter either the height or width of an image (in the image resize window) it will auto-calculate the H/W.The whole post was a general comment on taking pics and really showing off sfx, because if your shots get blurred it defeats the purpose of sfx. Since lots of forums won't display images in width higher than 1024-1200, it's pointless to to keep it at full-size. Resizing also saves valuable file size and makes for easy uploading. :Peace:
May 11, 201313 yr Ah ok got it. Thought it was directed at my images lol. Yeah I always run through a bit of sharpening when downsizing images. Habit from processing photos that I take. The whole post was a general comment on taking pics and really showing off sfx, because if your shots get blurred it defeats the purpose of sfx. AMD Ryzen 9950X3D | Asrock X870E Taichi | Gigabyte Gaming OC 4090 w/EK waterblock | Full Custom Loop Cooling | Corsair Dominator Titanium DDR5-6000 | Samsung & WD NVME/SSDs | Phanteks Enthoo 719 | Seasonic Vertex Gold 1200W | Keychron Q5 Max | Corsiar Scimitar Elite SE Wireless | Honeycomb Alpha and Bravo | Logitech Pro Flight Pedals | VKB Gladiator Pro NXT L&R handed | MiniCockpit MiniFCU | Alienware AW34DWF | Asus PG279Q | Win 11 Pro
May 11, 201313 yr On the first four shots I'm using AA @ 16x and Transparency AA @ 4x. Works great, no fps impact on my setup. Rest of the shots are using the settings that are currently in my sig. could you post your sweetfx settings please.. Love it Manny Beta tester for SIMStarter
May 11, 201313 yr http://www.guru3d.com/files_details/sweetfx_shader_suite_download.html Installed, but had to remove it due to FSX not starting.
May 11, 201313 yr @ If fsx doesn't start it's because you deleted the original shortcut which has compatibility set to xp sp2... or if you removed it at some point from the shortcut. Make sure it's there and re-try (should work). You're missing a "big deal" if you give up and remove it that easy.
May 11, 201313 yr @ If fsx doesn't start it's because you deleted the original shortcut which has compatibility set to xp sp2... or if you removed it at some point from the shortcut. Make sure it's there and re-try (should work). You're missing a "big deal" if you give up and remove it that easy. Luckily I backed up the d3d9 file before I added SweetFX, after removing SweetFX from the FSX folder, I re-entered the original d3d9 file so I'm sure thats what was causing the issue. I'll try it out later and use the d3d9 file thats there instead of replacing it with the one in SweetFX.
Create an account or sign in to comment