Wanthuyr Filho

Is FSUIPC registration necessary for assigning and calibrating a steering wheel/tiller hardware controller?

What about the DIRT parameter, anyone has noticed any difference whatsoever?

Isn't the 70 setting the most natural one, i.e., closer to zoom=1? Did anyone find a way to make a value other than 50 the default one?

As for the pagefile, it's a theoretical "thing". In practice I've learnt that P3Dv4 had OOM at least once when I used to have the pagefile disabled, even though the rig had 32 GB of RAM. Not to mention Windows memory management is a strange thing, sometimes it seems to go to the pagefile even if there's plenty of RAM free space, anyway, I just leave it on. As for the rolling cache I've been for months having it disabled, but I've regularly been seeing strange autogen behaviour during final approach, and talking to a friend of mine he suggested that I try the rolling cache, so a few days back I turned it on again and will observe for the next weeks.

Is it possible to connect the GSX provided GPU to the 737 PMDG?

I haven't tried the A320 yet, but should be the norm to make good smooth landings, most RL landings are pretty smooth, and that doesn't mean floating. Used to fly the FSLabs A320 on P3Dv4.5 for years in a row and I consider the latest version quite precise in this regard. Earlier versions had a kind of delay on the controls which used to make things complicated. As for the 737, I've been flying the -800SFP lately and I feel like it has an excess of lift on short final. If one comes Vref+5 it's likely to float if one wants to make a smooth landing, even if cut the throttles earlier. Also I miss this heavy nose feeling on the 737 as the throttles come to idle, opposed to RL.

This is interesting because many of us were already able to use DLSS even with older drivers.

Now that is strange. I have no idea what might be preventing it from showing up, sorry.

You know it should be on the AA setting, right? And you've updated the simulator successfully?

Alright, I've set it to 200 and will see the difference on next flight. I am at native 4k too (55" screen). Thanks.

By increasing sharpness you mean that AMD setting (all the way to 200)? Thanks.

I don't know if this is really the case, but DX12 for me (3080 Ti) causes the airport pavement textures to fail and not draw (patches of it).

4k screen users should opt for which technology? I've selected DLSS and get these blurries on B-737 display units (where digits change rapidly for example). Selecting any other modes would make FPS worse?

Is it possible to make it behave like it does in P3D? The main complaint is that it vanishes and prevents me from keep clicking the CDU buttons, for instance. So that I have to move it slightly, it will reappear and only then I may continue clicking. P3D if memory serves me right it keeps showing as long as one keeps clicking or moving it. Also, is it possible to diminish the size of the pointer and/or make it look like the "normal" Windows pointer? Thanks in advance!

I agree the "shake" visuals are lacking especially for ground roll and touchdown, it's not realistic enough. With addons such as ChasePlane one could fine tune the settings to make it so real.

I've installed AIGAIM for FS2020 and have the same issue, no planes flying around. Loaded at KLAX and I can see some planes on the ground (weird airlines though) but nothing moving.

Unless Orbx updates their products to the new standard, apparently leaving the default ones is the best option.

I don't care it's phased out or not, what really matters is that it's a quality addon.

What's the difference between Studio and Game drivers? Just installed the latest, Game type. Now gonna make an airliner flight to see what happens. I haven't touched NCP nor selected to clean it, as it has some customised options.

Modified shaders definitely can cause this, together (or not) with those internal brightness P3D settings, and also that parameter that can be added to the .INI file in order to make night brightness more alight or more dark.

This is pretty much what prevents me from upgrading. My v4.5 HF2 is so very stable nowadays, full of addons, and mainly with textures and visuals highly customised including via PTA (which AFAIK doesn't exist for v5). In summary I'm quite concerned about upgrading, have A LOT of work reinstalling mostly everything and then come into conclusion that I didn't like the final result, not to mention the possibility of being "chosen" to have all these reported glitches here and there. I'm still not using FS2020 either (mainly due to the lack of more complex jetliners, AI traffic, etc), and I really have no idea if one day I'm going to upgrade to v5 before moving completely to FS2020.

These are great tools, thank you! Whenever flying at cruise level and another plane passes nearby it acts erratically, like it zigzags up and down in an abrupt manner. Even the contrails are drawn erratically too. Is it possible to fix this behaviour?

Anyone seeing issues when the AI traffic comes to park in a position next to yours and just stops before the correct position? Apparently it keeps waiting for you to leave the gate so that they can finish the taxi and park, they even keep anti collision lights on, but that just shouldn't happen, since the positions are independent one another. Is there a fix for this behaviour? Also I never see surface commands check within AIG AIM traffic, as stated in the readme. BTW, I use both tools together.

@spilok, What's your simulator version?

Just to update you guys, my PSU really seemed to be faulty. I used a quite nice software for hardware stress tests I've got from the Internet, at first I've discovered that my overclock was not super steady, I had to make a few adjustments (when I suspected it was the source of the issue), but even then things continued to happen (the power downs). Then I learnt that this stress test software also could stress the PSU, which within seconds or minutes at most ended up raising the issue. So I've exchanged the PSU with another one (same brand/model) that I had in another PC (which was not being used anyway due to a defective MoBo) and alas... Never happened again, not on P3D nor on the stress test software.