TheBoom

Lol, not sure why you're quoting a 3 month old post but nevertheless I use my PC for plenty of things other than P3D. That's where hyperthreading usually comes useful. FYI.

This would probably vary from system to system but 4.2ghz to 4.7ghz netted me about 6-8 fps. Which made the difference between smooth and laggy experiences. You will see a bigger difference with higher settings/loads with overclocking. The more stress you put on it the more gains it shows. However if you run low to medium settings then it's not worth the trouble.

Could you elaborate on that? Curious. Sorry I haven't been here a decade yet.

Doesn't the autogen effect become very obvious at LOD high?

I have the same exact system config and that seems like very moderate settings. It's a shame that VAS usage just keeps increasing at the same settings with v3.

Yes I meant FTX global. I will skip the scenery update for now.

Thanks. Will probably update everything in that case. Edit : Scratch that. I just remembered I would have to reinstall all addon scenery if I did that. The only scenery change is some fix for those with 32 bit Windows isn't it?

Hi all, kinda out of the loop since I gave up flying for a while after multiple problems in 3.2. Considering getting back into it now. Can anyone tell me if I should update all 3 installers to 3.3.5 or would client only do? Also apart from objectflow is there anything else that needs to be updated to work correctly? ASN and REX? Thanks in advance. Regards,

What they don't show in the video are the blurries under the aircraft :wink: . Kidding aside, the two "new" simulators in the market are far from promising so I'll have to agree P3D is still the future, period.

I was considering this before I got Track IR, but a major downer is that it doesn't work with Ezdok.

1) Remove AM, or use one that uses all cores 2) Increase FFTF 3) Reset NVI profile to default 4) Increase TextureMaxLoad

Too many threads depicting the same issue lol. I offered someone a few suggestions on a another similarly titled thread. Worked for me. If you could roll back a page and find the thread you could see them.

Thanks will give it a go. I was adjusting HDR Brightness, maybe I should have been adjusting the Bloom levels instead.

I know he doesn't but I'm wondering if turning down the HDR brightness would offset the effect of the terrain brightness tweak in the tool. Seems to be the case though.

Thanks, but I seem to have fixed the blurries and had problems with VAS instead, so I went up instead to 32 and it seems better.