All Activity

I would think the team building this chair would need to address this; if needed, they could reach out to us to discuss. But we cannot make changes for one piece of hardware without the ability to verify or confirm what is actually needed.

When multiple players use dynamic spawn to spawn more or less simultaneously, they may spawn in the same parking position, resulting in multiple planes spawned inside of each other. This physically invalid state is then quickly resolved by means of pilot death, explosions, and magically levitating fireballs. This is not the first time, I've noticed this issue. Unfortunately, the associated track file is too large to upload (~80 MB). Instead, I've uploaded a fun explosion video, showing the spawn issue occurring twice in a row. First with two F-16s, then with three. Guess this is a server-side issue, with the server failing to arbitrate parking positions between simultaneously spawning players. dynamic_spawn_explosions.mp4

No,no, it is just serious unhappy and expensive mistake on user side

and there is this post

I had my first longer session with the Super and DCS after my summer break yesterday. Tracking on my platform was fine at the beginning but gradually got worse as the session went on. I’ve read somewhere that taking off the headset can worsen tracking results, and I can confirm that from my own experience. So, tracking starts out fine - but once the headset is taken off a few times during a session, things deteriorate, and I just don’t understand why. Overall, I’m still happy with the Super. The tracking issues aren’t bad enough to make the headset unusable, but they are definitely quite annoying.

IRL IRST range is 15 km detection 12 km track for head on Mil MiG-21. Add planes with bigger heat signatures, in rear aspects using possibly afterburner, and no surprised to detect 30-40 km away. Being able to range them though will be limited by MPRF detection though which would be 18-40 km depending on altitude, background, RCS, etc

For those with a Rhino FFB and Helicopters: Do you guys use the DCS Force Trim or the VP Hardware Force Trim?

Just reinstalled this but getting crashes when tryong to fly the F-16D_50_NS? Any ideas?

Well I do it if I'm targeting, say, a building. I have and love VAICOM Pro but there is no "Look for buildings" command. I could do it from the front seat, but the eyeballs command, then head adjustment takes longer than if I went in the RIO seat and did it myself. So I noticed it's mission dependent. I don't know why. But when I flew a different mission, Jester was fine leaving my designated target as his new designated target. But in other mission, he ignores it and goes with his previous one. I dunno why. v6, boNes

Und da bist du dir sicher das im FC Mig Modul das simuliert ist? Hab's eben getestet. Mit Centerline-Tank konnte ich ohne Probleme die Kanone abfeuern.

Добрый вечер, если мод уже закинут, то можно его как-то получить, потому что я этот мод уже очень давно ожидаю, и думаю 90% людей на этом форуме тоже

I get this same bug but it seems to be at random.

No. RTX5080 so I would need to get the adaptor.

Hey! They are both guided precision strike munitions. And since they are pretty accurate, they will hit close to the target spot. If you want to hit a wider area, which is preferable with the cluster munitions, just create several 'Fire at Point' tasks with one round per launch. Make sure to spread them around the area you want to hit.

Well, I replicated Hippos settings and got similar results on the IFLOLS, but the Landing Area lights are obscenely bright now. Not sure how that's possible since his are the same brightness as the ball. Ideas anyone?

Well it better. I just returning to DCS and starting a fresh. Ordered my AB9 FFB base and my first module is the C130J.

When Aegres?

Can I just say how cool it is that Magnitude 3 included a proper FAA variant of the Corsair?

thanks for the log, we will take a look

Да нет, ничего не пропустил. "Тяп ляп и в продакшен" всё ещё основной принцип разработки, поэтому оно сломано уже почти месяц.

Is this related to the windows update issue that has affected some drives? check out Jayz2cents Youtube on the subject

@BIGNEWY; See the above reference Did the A-10 II dev team perhaps forget to press "Enter"?

I would like to add some new information. Unfortunately i have to replace my previous mouse (it was a steelseries rival 3, and its only working with 250Hz, so with 500hz its stutters). I brought a razer deathadder v3... and in synapse i left mouse polling rate at 1000 hz... just in casem and you know, why not. Everything just working fine, and i tested it for i dont know... 4 days now. It seems not every type of mouses suffer with this issue.

I would like to add some new information. Unfortunately i have to replace my previous mouse (it was a steelseries rival 3, and its only working with 250Hz, so with 500hz its stutters). I brought a razer deathadder v3... and in synapse i left mouse polling rate at 1000 hz... just in casem and you know, why not. Everything just working fine, and i tested it for i dont know... 4 days now. It seems not every type of mouses suffer with this issue.

Yeah, can't really say I am having any problems with them. Point the seeker at the bad guy, TMS up, shoot.