All Activity

SO I think this is by design, sort of like saying yes, you own it but you forgot to enable the module, if that make sense. If you want to get rid of it in your cockpit, its best to just disable in the Mission Editor and leave it alone in Special Options.

Have you made any customizations yourself? Because, obviously, if one adds the defaults from ED in the Saved Games files, then one would of course have doubled the inputs. The Munkwolf files I use don't have that. Just to check, have you tried the latest Quaggles version? There was a new release after this update. Cheers!

https://magnitude-3.com/downloads/

sliders are set to 0. The final position of the stick is correct, there's just that annoying pull at button release.

Hi I tested it on Kola map on sunrise and din't have this issue with Cirrocumulus 3. Here is a wonderfull screen with this preset with a great rainbow effect.

It would be better to start your own thread in the Bugs and Problems section with crash logs and such. Thanks

This mod has great potential. Unfortunately it has some constant crash issues with Pimax Play resulting in game crashing to desk top. I have researched and tried numerous ways to comply with the online system crash advice, but nothing seems to work. Trying the old open XR and Pimax play start options initially start off fine, but then almost at the exact same spot taxiing from a cold start the sim crashes. It is very frustrating, especially considering the amount of time I have dedicated to learning this module. As far as my rig, I am operating a Cyber Power Intel(R) Core(TM) i9-14900K, 3200 Mhz, 24 Core(s), 32 Logical Processor(s), with Nvidia GeForce RTX 4090. So handling this module and DCS should be no problem. These crashes only happen with this MiG-29A module. Something is wrong with this module and Pimax Play. Anyone else having these issues?

Hello, When I try a pop-up attack if there is an obstacle between me and the target during ingress for the attack, I cannot see the distance to target but the distance to the obstacle on the HUD lower right corner in CCRP mode. How can I overcome this issue? Is this a bug? Can I see the 'B' range (slant range) to target instead of 'F' range which shows the target to obstacle in front of me.

Hi hoping for some help here. When using the A10C divert airfield function the list provided in the CDU page shows no airfield information, the airfield names are replaced by letters and numbers only e.g. H17, all other information is missing, pressing the corresponding OSB opens the airfield page but there is no runway, tower frequencies, ILS frequencies etc. Anyone in the community seen this before and apologies if this is a noob question

Hi, Thanks to everyone who took the time to read my post. I have fixed the problem, after changing the order the export.lua file runs scripts. You learn something every day! Thanks again, Gareth

With the roll limiter in the F-5E, you should feel resistance. It shouldn't move the stick either in a push nor pull movement. You have to specifically choose the correct option in the special settings. It's quite self explanatory. If you also choose the linear stick option, the stick will "tilt" forward, so you have less travel forward and more backwards, as in the real aircraft. Cheers! Sent from my SM-A536B using Tapatalk

I notice something similar. However when pulling it back again, then the limiter is activated again. So I cannot actually hold the virtual stick beyond the limiter. the forces can be very subjective.. I personally cant feel the forward force at the limiter, only the violent shaking. I will experiment some more and try the F5 as well for comparison.

Sadly - or more like thankfully - it hasn't happened again, so no luck recreating. Ahh right, still familiarizing myself with the virpil gear, I just upgraded. Definitely not wake turbulence. Only other plane around was my wingman 0.7nm off my wing and back a bit. I suspect you might be right with the random bad luck of gremlins.

I did see that maybe 4 or so missiles did reach the base. I just happened to open the map as they were hitting. I have a track, but it's too large to upload and I don't have a screenshot of the results. I managed to gun two right off the bat, then use two sidewinders, and then for the ones that got a little further away I used my two AMRAAMs. My wingman got 4 with sidewinders and AMRAAMS. Though, on that run I turned off fuel consumption so I could RTB faster because I was tired of doing it again (my fault and an input control bug on previous attempts), so that probably helped with my ability to get 9 kills. I'll try again with fuel consumption on and only gun if I can easily get in range. See if I get fewer kills and prompt the dialogue. If I don't get the dialogue I will post the results, but I assume the track file will be too large to upload again. Regardless I'll try again and post the results that I can. Appreciate the input! Cheers!

So it seems that the Flogger will be relased at the end. For another game. Not a big deal for me: I wouldn't have gotten the module for DCS anyway, and I don't think I'll get it for the other game either (and it's not sure that I'll get the other game yet).

Definitiv, und ganz besonders beim Gaming, kommt aktuell nichts an die X3D von AMD ran... Also immer schön AMD bis sich da was bei der Konkurrenz ändert

там так и написано выпуск при нажатии взлет ИЛИ посадка. как тут говорили рил летчики всегда жали ток взлет, но разницы никакой.

SPO has a maximum detection range of 150% of illuminating radar's max. range. I am guessing that that's for when the signal enters the center of a lobe.

Nice Because I had the same issue and after removing the mod, no more double inputs. That's why I thought of that.

Yeah I can confirm this, yesterday it was working fine with pooling rate 1000 and day before that I had to lower it to 250, cause 500 was stuttering as well. at the moment of posting this, 1000 pooling rate was the cause of stutter, when I lowered to 500 it was ok. Mouse stutter pooling rate 1000.trk

Now that the L118 can finally be picked up without slamming into the helicopter, the next problem shows itself. When carrying at speeds below 40kts, it merely bounces around and starts swinging without any manouvering. Above 40kts, it gains enough energy to risk slamming into the carrying helicopter. Above 60kts, even a gentle manouver is almost guaranteed to cause the gun to swing into the fuselage. The gun is tested to be stable at 120kts when in a single point sling, according to US TM 4-48.10 "Multiservice Helicopter Sling Load: Single-Point Load Rigging Procedures". Attached is a track showing how it behaves in steady (except the gun swinging wildly enough to make it not steady) forward flight at increasing speeds. ArtilleryKarate.trk

You're probably talking about the before-1 patch video, here's the after video, it looks pretty good:

I´ve also experienced this more and more recently. Strangely only in a multiplayer session hosted by myself on my pc with only one other person joining. I´ve managed to take some screenshots and it is exactly as has been described here many times. Looking away from the sea frames are rock-steady, looking at the sea fps go down massively. We´ve also tried setting up a mission from Garz and frames immediately go down to 18 looking towards the area described in this thread. This has not always been the case for us and has gotten really bad fairly recently. So as it stands, that whole area up there is absolutely unplayable for us as well now.

What random Russian people say on an internet forum is not necessarily an indication of what RL MiG drivers from Russian AF say, or what the Soviet ones used to say. Besides, since MiG-23 is long retired and MiG-27 is obscure, I suspect "the MiG" works for most people these days.