Kassu62

FSR4 and VR?

There is quite big gap between unpowered stick and zeros for all forces. I think that the minimum centering force is too much for the most helicopters.

I did made small project for MSFS2020 using a PC program and Arduino UNO hardware for but kicker. PC did send telemetric information from Simconnect to UNO which was used to drive but kicker. The big thing was the effect which I get when I scale rumble effect with gear compression information. When the plane gains speed, the gear compression decreases and rumble effect is fading very realistic way. Another bonus is, that when you make hard landing or use gear breaks, the gear compression increases and you get strong rumble effect automatically. I would like to see similar effect in your FFB software.

The beta-2 does not start at all. Now the Win11 Smart App Control blocks the application from running.

My first tests are not going well. I did tested Windows 11 version's Mock Sim several times and the program crashes every time when I hit Arm.

In Marine Traffic SW all ships are in right positions and headings. MSFS2024 uses same AIS data, but the headings are totally wrong. Why?

The pre cashing is problematic because the touch down position is not known in advance. In the air the polygon data flow would be continous and you would not even use it. After touch down the speed is typically decreasing (= smaller data flow) and the data is used for rendering and ground physic. So it is better to start data download when you need it.

Earlier MSFS2024 frame rate did drop at the point when the gears hit the ground. Could it be possible, that high resolution ground mesh was the problem? Too much new data in short time. The logical mesh loading trigger is the ground contact so the simulator cannot preload the high resolution ground mesh.

I can't get airborne with gliders in beta releases. When I try it in beta 3, the towing plane did not even start motor. Now in current beta, towing plane starts, but it does not gain speed and then stops at end of the runway.

I have 5800X3D, 4090, and Varjo Aero. With the dynamic foveated rendering (resoluution 25%) I get huge positive frame rate impact.

If you select US server instead of UK manually, you get lower speed without the VPN?

I haven't tested glides for a while. Now, when I did test, I could not even take off from the ground because the tow plane did not move. Is this a SU4 beta specific problem? I also noticed several times "standing" pilots outside the planes. Are they back or have they been there all the time? Then I did try to fly those low flying challenges. I did have very bad shuttering. Frame rates were about one frame / sec. I have VR glasses. This might be a problem in my own setup...

For me the Foveated Rendering Scale adjustment is an improvement. I have Varjo Aero, 4090 and 5800X3D. I can drop the rendering scale to 34% with a minor artifacts, 25% is too low. With the default rendering scale 50%, the foveated rendering performance boost is not so big. Next I will study if I could increase the peripheral area PPD value without significant performance hit.

Another immersion killer is cathedral sized churches in small villages. At least in Finland...

The ground friction does not seem to vary from one surface type to another. When you taxi with a GA plane there is no difference between grass and asphalt. You should need more throttle outside the asphalt. Now there is just more bumps. What is the problem? Incomplete ground friction implementation in MSFS2024, insufficient airfield surface material definitions or airplane wheel modelling?

What is the problem in the MSFS2024 real time boat traffic? MSFS shows the boat type AIS data correctly, but the actual 3D model does not match to the type at all.

What are the right trimming surface settings for a collective stick 4-way digital hat-switch? I am a bit confused... ELEVATOR TRIM AXIS (-100 to 100%) [Helicopters] [Axis] This is clear, but this not for my digital hat switch. ELEVATOR TRIM AXIS (NOSE DOWN) [Helicopters] [Analog] ELEVATOR TRIM AXIS (NOSE UP) [Helicopters] [Analog] What are these? They are Analog, but the UP and DOWN are in separated axis. I would need Digital versions of the NOSE DOWN and UP trim controls? What are the four control trimming surfaces I should use?

Caribbean is not a problem. Almost all boat traffic goes from island to island or near the coast lines. Middle of the Mexicon Gulf is empty.

"Normal" T-AIS data can be received near the coast lines only. S-AIS uses satellites. I do not know it the MSFS2024 includes S-AIS data also? If not, then Atlantic Ocean is empty outside the coast lines.

GAIST settings are not visible inside the MSFS, but you can control it using Graphics setting. Here are the instructions MSFS AI Traffic Settings – Alpha India Group

GAIST model matching is not perfect. Yesterday I did check the Main Schiff 2 and it was show as a big Evergreen tanker. That is a model matching bug. Another problem is in real AIS data. Some boat owners do not have configured their boat information correctly. So some leisure boat can be configured as a cruise ship. Only solution for that is to set Sea Traffic OFF.

Good modeled objects do show models from far distance without performance hit and user can't see LOD model change steps. At moment MSFS2024 does not show other than Asobo's own ship models? It would be very odd if those models would not have LODs at all. You can see 300 meters long ship when the distance is about the boat length. The problem is elsewhere. I have not check how the latest SU3 beta handles AIS data. AIS data includes ship type, ship dimensions, speed, and heading. It should be quite easy to put boats objects on right positions and headings. There is used absolutely no type choosing algorithm for models.

Now the MFS2024 runs smoother than ever with the latest SU3 beta! I did update the NVidia driver to the latest version 476.26 and re-install Varjo Base.

I have constant and bad shutters with my Varjo Aero. Even with the lowest graphics settings. Processor AMD Ryzen 7 5800X3D 8-Core Processor 3.40 GHz Installed RAM 32,0 GB Graphics Card NVIDIA GeForce RTX 4090 (24 GB) In SU3 beta the picture quality is perfect. The cockpit view has never been that sharp. I know that my processor is a bottle neck, but does anybody have with a similar hardware decent user experience in MSFS2024? At moment I have fatal problem in VR mode. The screen goes full black, and I can't use VR mode at all. I will wait till next SU3 beta update and if it does not help, I go back to SU2 and reinstall drivers.

MSFS2024 have all you need for real time marine traffic, but it is still full mess after almost a half year after release. You can see boat name plates, but no boats. AIS data includes boat type and size information, but that information is ignored (passenger ship, sailing boat, oil tanker, etc.). If you are lucy, you can see a boat, but it is flying and totally wrong type. It is very hard to understand why they have not fix it. Showing generic boat types would be good start. Ship model picker could be added later. One solution could be a AIS data bridge between MSFS2024 and GAIST? GAIST have working AIS data support, but they lost their AIS data provider. I have understand that there are ship model copyright problems. This solution would keep MSFS2024 and GAIST separated -> no copyright problems.