All Activity

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 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.

Вот ведь! А я подумал, что наоборот поломали. Тогда здорово!

Do you play DCS yourself remotely? I have the Nvidia app already and it is a graphics config app, nothing to do with cloud gaming/streaming whatsoever. It even has a link to download GEForce Now as a separate application.

In my experience the none option does what it says, it sets no trim and the magnetic brake remains in the center position, not in the newly set position (probably has to do with polychop's implementation of magnetic brake combined with manual trimming), so your ffb stick is centered and you can't do anything. For ffb sticks the option that works better is instant trim, the option that works best is flying with magnetic brake off.

HI @Polonsky Thanks for the track. Just checked this out. This is not a bug but a campaign design decision. When your wing gets close enough he is removed from the SIM so as not to conflict with the your landing on the carrier. Noticed you had quite a few attempts at landing. Had the wing not been removed he would have conflicted with your attempts. Have done two campaigns after this one and now adopt a kiss off system in these and control the wing. Think in time I will update this campaign in line with them. Noticed you entered the wrong coords and tried to locate the harboured subs with the Sea mode radar which will not work. Also, you had quite a lot of positional and level issues. I have attached Flying Kennys fly through of the mission which will hopefully help you. Cheers

Все правильно, это я перегрелся, с GNS-430 разбирался, это она не туда считает BRG , потому аж 10град вышла разница со склонением +5

Их починили полностью

Wonderful news and thanks for doing that.