fly_edds

I'm not a fan of these "good driver - bad driver" discussions, as they're mostly related to (demanding AA + other) settings in Nvidia control center, which will be resetted when a new driver is being installed. So forget about this, it's nearly always wasted time - but it can for sure help to improve peformance

Hi, I think your cloud.fx has been corrupted by a faulty REX4 update. You can fix it by downloading the default P3D3.2 cloud.fx file: http://www.mediafire.com/download/05t68smuyy7s5v6/Cloud.fx Copy it to Prepar3D v3\ShadersHLSL and overwrite. Hopefully this will help you... (as it did for me)

Hi, I have some advice for Kaspersky users. -In settings, go to "Performance" (not sure how it is named in the english version exactly) -Scroll down to the buttom, you can specify prepar3d.exe here. Kaspersky will pause now everytime you start the prepar3d.exe process and resume when the process terminates!

Any idea what that means exactly? I'm still having the hope that Aerosoft lights will be fixed someday... Maybe they have fixed the bug that default lights lost the bloom inside of a specific radius around the aircraft?

Hi, I thought DSR would be much more demanding on the GPU than SGSSAA? Maybe I'm wrong... When I use 8xMSAA + 4xSGSSAA the load on my 970 (4Gb) is almost always at 100%. I would expect a similar load when using DSR. Or is it a bug of P3D? What do you think? I've noticed that even 2xSGSSAA can be a massive performance killer.

Hello Jarkko, your forum activity and invest of your spare time is much appreciated! Nearly all other forum moderators are very inactive in the last weeks/months, have you heard anything from them? Especially Shells and rjord disappeared a long time ago... Thanks!

Last post is only 3 days old and they have to be approved manually. Maybe moderators are busy elsewhere or people are finally satisfied and don't have problems anymore (me included :smile:) Vectored approaches will hopefully be improved as announced by alpha117, we will see how it develops...

Yeah, it's that easy (C:\ProgramData\Lockheed Martin\Prepar3D v2\scenery.cfg)

@suvo Scenery Config Editor is working in P3D, using it every day.

Here's a little comparision I've done in P3D 2.4 (PMDG 737 NGX, AS Heathrow Extended, FTX Global, ASN) LOD 4.5 3.18 LOD 2.5 3.04 Difference ~140 MB VAS High res cockpit 2.97 Low res 2.77 Difference ~200 (!) MB VAS Scen. complexity sparse 3.11 Scen. complexity normal 3.18 Difference ~ 70 MB VAS Road traffic 30 2.71 Road traffic 0 2.66 Difference ~50 MB VAS Summarized: Turn down LOD and TML, use 512/1024 clouds. Building density sparse and (as a compensation) vegetation density max is also helpful. Use low res cockpit textures if possible. (Would be very helpful for the 777, PMDG :rolleyes:) Lowering scenery complexity might also help, especially on huge airports, but lowering it below normal can induce scenery problems.

Hi! In case you didn't know, you can easily "import" your old Sweetfx settings to ReShade/SweetFX 2.0. The values are nearly the same. At least my old SweetFX profile looks absolutely the same in Reshade. You can download my settings here: http://www.file-upload.net/download-10140147/SweetFX_settings.txt.html

So far it's stable on my system. No crashes and massive frame drops when accessing the menu anymore. (menu bar as well as right-click menu) But I'm unable to undock gauge windows (Feelthere Map gauge in my case) without loosing half of the framerate I had some hope that "ReShade" would also fix this...

Just opened my prepar3d.cfg after a very long time and... ooops...what do I see? TEXTURE_BANDWIDTH_MULT=1800 :huh: I will return to a value of around 200 (GTX970) Maybe I've finally found the source of those annoying micro stutters on my rig, so thanks anyway!

Hi Matias, at first I want to say thank you for this very helpful tool! I have a little idea for (possible) future versions: Maybe you can add an option to generate the sample file without the "//"? In the past I let them all active, so I didn't had to activate/deactivate the airports I want before flying. I've never seen any performance loss. But I've written a little batch-file which removes all //, so it's no problem at all Sebi

I've forwarded them the complete correspondance with FSPS (dev of Fiber Accelerator), including the "OK" for a refund. I've tested the free trial - some hours after purchasing, FSPS extended the free trial from 5x5 mins to 5x60mins.

Sorry, missed it. But once again, that doesn't matter. I'm complaining about their way dealing with customers. And they should also know that I'm getting into trouble now when asking FSPS to reactivate the serial. sh.. happens seems to be the perfect phrase for me now hehehe

Thanks Gartro, maybe I'll try the AU store in the future. Hi Howard, I think that's a different thing. Fiber Accelerator has an online check and can only be used on one PC at any given time. Beside that I've contacted them already 2 days after purchasing and i think it's not asked too much to get at least an simple answer. It's not the right place here to discuss that...

Hi, I'm just reviving this thread because I'm totally disappointed by Pcaviator.com. I've bought Fiber Accelerator about two weeks ago. Of course I've tested the 5x5 min demo before buying, but nevertheless I was disappointed after some flights. I contacted FSPS support and they gave their "okay" for refunding and deactivated my serial. But the final decision is on PCaviator's side. So I've contacted their support several times 9 and 6 days ago via support(at)pcaviator.com and orders(at)pcaviator.com, but I didn't got the smallest answer until now. Two possibilities: a) Their support is totally overloaded or b ) They don't see the necessity to give at least a short answer on my refund request. Now my serial is deactivated and cannot be re-activated because I cannot prove FSPS that they really haven't refunded me... It's somewhat annoying and disappointing... -_- Any ideas what I can do? (apart from waiting or calling them) Anyway, they've already lost a customer who has bought a lot of software... P.S. I'm also wondering if others have experienced similar problems with pcaviator.com in the last weeks/months? Thanks, Sebi

Regarding to my recent critic about the product and the permanently change between unlimited and locked FPS I've found this posting by BD in another forum: So it's not Fiber Accelerator's fault, my FPS settings were simply too high.

Hi Pete, I forgot to mention an important thing, the vsync. It is set to 1/3 refresh rate, and the FPS inside of FSX are fixed at 20. In any other case (unlimited or limited using an external program) I have noticed heavy micro stutters. Maybe I've mixed these to problems together and maybe the one thing doesn't have anything to to with the other thing... Possibly the frame rate higher than 20 (instead of my usual fixed 20) + 1/3 vsync caused the recent problem. I'll have to experiment and when I found a fix for the microstutters, I'll perform a flight using fiber accelerator again. And yes, my framerate is much lower when locked internal, but that's the only way to eliminate the microstutters/FPS-jumps. Maybe I should open an additional thread for that. Sebi

Okay, first test flight: Looks like fiber accelerator is switching the FPS-limit inside FSX between the fixed value and unlimited each minutes. The problem is the following: When FPS are set to unlimited, i get a variance between 20 and 30% (instead of lower than 10% when using a fixed value). All I can say now is that I will not buy it until there's an option to deactivate that.

http://www.thefsps.com/Programs/FSXFA/Fiber_Demo.zip

Hmmm...for me it's working very well. Aerosoft's Mega Airport Duesseldorf (one of the biggest framekillers!), very bad weather (Active Sky), PMDG 777. FPS locked @25 Without Fiber Accelerator: Frames: 1102 - Time: 60000ms - Avg: 18.367 - Min: 13 - Max: 20 With Fiber Accelerator: Frames: 1480 - Time: 60000ms - Avg: 24.667 - Min: 19 - Max: 26 I'm a little bit impressed, but I would like to know in realtime, which parameters the program has changed. I couldn't see any visual difference... Sebi

Sorry! I meant that the "buffer" for the remaining flight is always about 0,5 GB. I'm already monitoring the VAS using Processexplorer.

Hi guys! That's ridiculous. My FSX is always freezing on longhaul flights after 7 to 8 hours inflight. I can 100% reproduce that. Normally I'm not doing anything on my PC when the freezing occurs. It's not an OOM problem, the VAS is at ~3,5 GB on each flight. Here's my setup: PMDG 777, FTX Global, Active Sky Next, FS Real Time, Pro-ATC/X, Ezdok, kACARS (flight tracking for my VA). FSX is running in DX10 + Steve's DX10-Fixer. My specs: Windows 7 64bit, GTX770, i5 4670k @4,4GHz, 8GB RAM. All in all it's not a big problem cause I'm using FSUIPC's auto-save-feature on each flight, but these freezes are simply annoying. Here's the error log: (Not really informative, I think?) I'm wondering why it is always freezing after such a long time...maybe some kind of memory/bufferoverflow? I'm very thankful for any ideas! Kind regards, Sebi