JayJ

Very professional study

It's called proximity fuse

Slow down and lower your altitude. It will go away. I don't know why it happens but my theory is that anti-icing mechanism can't put up with the amount of cold or something. Maybe it's a bug idk.

Isn't QFE at altitude of 0 (ASL) --> QNH?

Problem: Altitude values displayed by barometric altimeter show high error. The higher the altitude, the higher the error. (As much as 600 meters at 5000 meters ASL). Description: For missions where temperature is high and sea-level air pressure is set to high. In provided track I started in the runway of Batumi (correct QFE already pre-set). As I ascend the display error worsens. Similar issue observed for Su-27 and for low temperature/pressure combinations. Primarily would appreciate a confirmation that it is a bug. Secondarily, I'd appreciate a fix. altimeter_report.trk

Will it work if I fly right over the sea level, then set it to QNH provided in the mission briefing?

How do I set QFE on my altimeter in Su-33 if I started the mission mid-air?

Alright then. Thank you for your insight and time @Flappie

I replayed your track. Smoke color was correct and same as in the SS you provided. It seems the key factor in smoke color manifestation is weather preset. I use latest Open Beta (updated today in the morning before recording tracks). nothing_smoke.trk overcast4_smoke.trk

Any flanker from FC3. I did a quick additional test and attached two 'white' smokepods and one 'blue' in the center. Blue smokepod produces dark blue smoke. White ones produce blue-greyish color. I can re-edit my autoconfig.ini to record a track tomorrow if needed but honestly there wouldn't be a whole lot to look at in the trk file. Steps to reproduce are just attach the pods, start the mission and start smoke.

As in title; I have a few mods installed so I am not sure if this bug is common for everyone. Can someone with a clean install cross check?

I think last time this happened to me I had trial modules installed. This may be linked.

+1

Not 100% sure about this. But what I usually do is - I lower my altitude and speed and the message disappears after a while. Perhaps the anti-ice system has its limitations.

+1 for the mig-29

My bad, the option is already here and it's called 'Allow Players Pool' under 'Advanced' while setting up server.

You can hide role slots in the lobby by assigning a password to them in the editor. In my opinion too many people think DCS is all about continuous mass airquake servers. DCS is more than that. We're merely asking for an option so that we, as mission creators can exclude this type of spoiler from the mission. I don't care about the score table being enabled or not elsewhere - it should be up to the host. The form we currently have it in right now is simply limiting. There are some scenarios where it will be harmful for the experience to have the scoreboard enabled. I don't want my clients to frantically check every minute what their opponents are flying and whether or not ther amraam hit the target already. I want them to play the game. Again, the decision should be made by the host. Not enforced by the game limitations (which in this case should be easy to overcome). Thanks for the tip about DDCS though; indeed they found a way to hide the scoreboard contents. I'd rather have it done the easy way though; without scripting.

It's a small thing that would make a big change for mission creators

+1 +1

Did You happen to have a short power outage during your flight eg. due to blade rotation speed being too slow on abrupt deceleration?

Dear ED, Thank You for Black Shark 3!

Hit Rctrl+Enter while in flight to see Your controls overlay. This will help you understand the trim functioning. You do not need the 'reset trim' keybind. You need the "trim" one. You can record and post a video of You flying with that overlay on. Maybe it would be easier to spot what's wrong. Tip from my experience: there are 3 general ways to fly the shark: - with autopilot channels on (3 of 4 blue square buttons on the right) - with AP channels on + flight director (fifth blue button) - IMO easiest mode for as long as you don't know what trim does - it dampens autopilot channels giving you more control. - without AP channels on - this is either due to AP malfunction or when you want to maneuver fast to eg. dodge a burst of bullets coming your way (having a quick keybind for flight director instead is better). Generally shouldn't happen.

I just started free trial for the Mi-8 today. It's a perfect fit for missions I fly with my squadron involving troop and cargo transport into combat zone. Very easy to learn; very fun to fly. Please prioritize adding proper multicrew feature for this module. Thanks!

+1 Imagine events like EMP pulse during a mission that would damage all clients' radars and radio communications. We need that feature badly.

Thanks very much for fixing this!