All Activity

Screen recordings with Quadviews have a fundamental problem. The recorded image can only come from the peripheral, i.e., low-resolution view. How did you manage to record good quality before?

After the update yesterday I wanted to sit in the Corsair after a quite some time again and it was impossible for me to taxi to the runway in that Mission where you have to transfer two corairs from Nellis. In no way this behavior can be acurate. First I thougt, I would be doing something terribly wrong but after checking this thread I´m glad to hear that I´m not the problem. But when I think twice it would be easier to avoid a mistake than dealing with a broken module. Quite dissapointing. Is it confirmed by M3 that it is a bug and they are working on it?

Yes I can see the effect when I'm at higher altitude. Expected something like MW50 in the German birds, but it's quite different. I would appreciate a comprehensive guide for its use. The bits and pieces in the posts don't help me.

Aerges please add specific keybinds for selector switches such as IDN Mode Selector or Radar Function Selector, etc. Currently there are only options for turning the knob left/right. It would be very helpful to be able to directly select e.g. the radar modes (H.A, I.A, etc.) or the IDN modes (TT, TE, VT, AR). Many button boxes (e.g. VKB SEM or STECS) have mode selector switches which could then be bound to the functions mentioned above. On the other hand some switches like the Stores Jettison Select Switch only have bindings for their positions (up, middle, down). Here it would be great to have bindings to move them up/down, or - even better - toggle switches. The up/down keybinds could then be used with K-switches. Generally, having more options to add keybinds would greatly improve the usability for existing button boxes and HOTAS setups.

WhaaaaaaaAAAAAAAAT!! Still not fixed?

Thank you for replying

As a new F1 pilot I would like to chime in - please add more toggle options!

Good to hear if the issue is fixed! Did not see a line item in the changelog for it

not sure thats what this is ? middle is an F-16 top is an F-18 ...might just be the screen backgound

Tbh I wasn't aware the A-10C II did ever receive a gateway function already, be it with the implementation of the ARC-210, before or afterwards. So in my world, seeing a L16 Viper, Hornet or any flight's PPLI on the TAD seems wrong at this point, regardless A-10C or A-10C II, so I think the OP has a valid point. ED's manual for the A-10C II doesn't mention any gateway at all. Regarding datalink and TAD, it specifically focuses on SADL, which is incompatible to L16. I don't see how the fact that we can see L16 PPLIs on the TAD is basis for the assumption that we received a gateway capability. For now its a bug, unless ED confirms this is intended as simulating a gateway in any of the both A-10Cs we have.

Didnt sleep much last night so went through all of Talleymouse settings. Tried several options and eventually got to the stage of almost zero stutters and blur. Tried launch via Pimax, Launch direct from DCS, various and some minor tweaks to get a reasonable result. Personally It did require me reverting back to 1.40 version to acheive this. PC specs below. Regards

Why would it? It is a replacement for WMR, so it is irrelevant whether or not you are running a Windows version that still has WMR in it.

I'll try to find what asset must be replaced and release an update later this month. In the meantime, high digit SAM is a fairly common mod, you can find more here :

Of course BigNewy.

No but I have bumped the report internally. thank you Hi, CDU work will take a little more time sorry.

folks please dial it back or this thread will get closed down.

Hi, thanks for the report. This has been sent to the team. thank you

same here engine quits after a while but only with to much wingload i start from the carrier fly 3 to 5 minutes in max continues 2550rpm 44mp all theperatur are in the blue sector i watch the gauges the whole flight an when i fly witout any wing load nothing happens to the engine and when i start in the air with full wing loads also nithing happens to the engine i can fly max continues all time till my fuel runs out im not at home and cant provide a log file i think its a bug before the update nothing happen to the engine under the same conditions but after the update engine dies and i cant explain why i start in hot start on the carrier

No idea what DTC issue you are assuming, since the partition containing navigational points hasn't been implemented so far. As above, its a result of a wrong utilization of the route tool. Enter elevations, otherwise any point will default to 6523 ft. Also FIX would be the wrong method to "fix" this, as 1. this is an altitude issue and 2. you would only adjust a correct alignment to a different one (with a wrong system altitude).

this has been reported, thank you

Gute Neuigkeiten im Newsletter von Bigscreen: https://store.bigscreenvr.com/blogs/beyond/how-eyetracking-works-in-bigscreen-beyond-2e?srsltid=AfmBOoqwz3ShIhjJDbmeZ0SlSMzYK8XuAqWA4aLjmi0FO5ly3eHVdHoU Sie versprechen zwar immer noch nichts, gehen aber davon aus, QuadViews zu implementieren. "...As we further develop the underlying eyetracking models and resolve OpenXR bugs, we expect to release advanced performance enhancing features such as Foveated Rendering and Quad Views. This means that Beyond 2e can enable performance intensive games like iRacing, DCS, and Microsoft Flight Simulator 2024 to run more easily on PCs."

That's how it's supposed to be. Same thing is in the F-5, although F-5 does have a "Special" option to enable/disable this whereas A-10 does not, but it doesn't make it incorrect.

А, да, помню. Но его потом убрали. Я считаю, что правильно. Ибо это профанация!

What you describe there is the result of you not entering elevations in the route tool. You seem to assume the route tool will set each new STP at ground by default. It doesn't. By default its at some 6500 ft or so. I can agree this isn't optimal but you just have to deal with it. If you ignore this and load in your route with all STPs at 6532 ft, its only correct to expect the TGP pointing into higher elevations, touching the ground only in the distance if at all.