All Activity

Well... I just may have solved the problem. I went back to Open Composite, activated it and disabled Steam VR in the Open Composite option. Activated Open XR and Tool kit programs. Started Pimax Play, and in the Games section disabled in the menus any reference to Steam VR (including aspects regarding the DCS Game Start option) and hit Apply. Then activated DCS from the Pimax Game option (with all the Steam VR stuff off). Held my breath, and to my amazement flew a complete 40 min solo Nav mission out of Maykop from cold start to shut down. Everything worked perfectly!! Therefore, I am assuming the problem is actually with Pimax, (not playing with) Steam VR and something to do with those two that relates to the Mig-29A module. Of course that was only one flight. Will try multiple flights soon and report if all is okay using the above process. Again this whole problem only seems to be a factor with 29A module, all others are fine. As I am fixated on the 29A for the time being, guess this will be the new DCS start norm using the Crystal for me.

Something just randomly changed all your loadouts in your mission? Or is the default loadout changed in general? Have you accidentaly copied the loadout of one unit over to the rest? Or have you modded something? Because default loadout should always be empty, unless you changed it of course.

Su-27SK manual says it happens at 85-95 degrees, I assume this is for high frequency pulse Doppler fighter radars as those are more precise for SPO

Awesome, thank you. I must have missed that update - thanks for the info

For the FC (and now FF) Mig-29 I've always un-mapped aileron trim because it was too coarse and impossible to centre; plus I could count on one hand the times I ever actually needed it compared to the times I accidentally bumped it. As for the pitch axis I do prefer the current gain. The Mig frequently needs gobs of pitch trim (just think of air-starts) so if there are plans to reduce/alter the sensitivity I hope it's optional.

Reinstalling DCS is hardly ever the option. Please provide the information that MAXsenna requested along with a screenshot of the exact error.

@Schlomo1933 Here are two tracks: Rotor brake handle lowered using mouse: the engine starts with rotor brake in lower position. Rotor braked handle lowered using an axis: the engine only starts while rotor brake appears to be in upper position. AXIS.trk MOUSE.trk So, for me at least, the incorrect behaviour you described in OP is still applying. I deleted my axis and rebounded it, but it's still the same result.

Can you please attach your DCS log file for when this occurs again. The log file will get overwritten each time you start DCS so make sure to grab it first.

That's what I was using.

It happens during taxi because putting it into STANDBY will start the heatup, leading to the radar melting if you take your time on ground.

Does anyone know what this yellow "radalt-looking" symbology on the HSDH is? Pulled from this video

Hey all, so after discussions with the dev team and feedback from SMEs, the Trim Hat sensitivity is how it was experienced in the real thing. I have been flying it for some time, so I might have just gotten used to it. It's possible that if you are coming from another module, you might be experiencing just that difference.

It is an interesting topic. Was YT played at PC through HDMI over to the receiver? Thanks.

Beim Mainboard habe ich auch lange hin und her studiert. Auch bei den Herstellern. Naja je mehr man da sich einliest desto mehr ist man verunsichert. So bin ich von ASUS weg, da sich viele über ASUS beschwerten. Schlussendlich bin ich bei MSI gelandet. Mit dem Chip das selbe. Was ist besser, was lohnt sich, was nicht. Mein Focus war, das ich nur noch M.2 SSD verwenden möchte, das MPG X670E CARBON WIFI hat 4 Anschlüsse on Board und alle Lanes der PCI Anschlüsse sind so konstruiert, das ich keine Einbusse beim PCI 5X Anschluss der Grafikkarte habe und im verbind des M.2 Solt 4 habe. Der ist zur Zeit noch noch belegt. Ich hatte am Anfang etwas mühe mit dem Arbeitsspeicher, aber nach dem 2. BIOS Update, läuft alles super.

I lost count of the hours spent changing the livery on several spawn points. This reminds me of the bug that kept resetting sound files. Can we please address spawn points resetting the livery from X to "DEFAULT"? As you can clearly see, this is not the default livery. Yet the ME seems to randomly (or universally) reset any livery for any aircraft to "default". Is it possible to use the same method of saving sound file in the trigger system to have the same effect on liveries?

@Furiz Can you also attach your DCS log file after replicating this issue.

Namely, the MiG-29 on the CW Germany map is catching ARK on both sides of the runway, when it should be on the active side / they should be active on active approach . I don't know if it's the map's or the aircraft's bug, because I don't have Caucasus or L-39 installed. Easy to reproduce, no track needed i think.

Has anyone else noticed their AH-64 default load outs changed? I don't know how this happened, but I'm effin pissed! Every AH-64 spawn point in my MIZ file for the PG map has a "default" load out of Rocket Pods x2 and Hellfire x8.

Please see the following bug report: Basically, FP created in Mission Editor not showing up on the NS-430. Only seems to affect C-101EB and CC.

Additional information: Tested, and only appears to affect C-101, both variants, both front and back cockpit. I tried it in the Mi-8, which I also have the NS-430 for, and the flight plan from the Mission Editor succesfully propagated into the NS-430. Also, tested the same flight plan in the Hornet, as made in the Mission Editor, and it showed up as expected in the Hornet's Nav computer. Tested on Normandy and Marianas maps

@upyr1 I didn't find this when I was looking. Guess I didn't go through enough forum results or just overlooked it. But, yeah, this would be a great feature.

Yeah, I've added a cow on top of the buildings I want to trigger

Here is a recording and a track file of the sound issue. I just a made a mission with a cold start and nothing else in it. I removed all mods, reinstalled the F4E and repaired DCS. Flew the F4 about a week ago without issue so not sure exactly when it started. Same noises with engine on. Not occurring with any other modules so far. F4E Sound Issue.mp4 F4ESoundIssue.trk

Почему-то у меня не работают. Как ни старался. 0 канал 124 МГц, 1 - 255 МГЦ (ДРЛО).

The only thing that puzzles me about Manual/Auto mode is that even if the RSBN channel is set correctly, after catching a path, the direction indicator needle (yellow) starts spinning. It simply lost the signal (Landing switch up). It's possible that the navigation system is actually only able to receive a single beacon signal, and if we're using PRMG, the RSBN doesn't work. The approach path can be manually set on the HSI and that's always a good indicator.