bear.is.flying

The current DCS “enhanced spotting dot” system has significant drawbacks, which can be improved with a “hollow box” system. Currently, the spotting dot renders on top the airplane model. This has two major gameplay issues: 1. An abrupt transition occurs at the range where the dot disappears, yet the underlying model is still very small. This makes it easy for the player to lose tally at that moment. 2. The dot blocks the model, making it impossible to assess target aspect or obtain a visual ID at distances where the dot is rendered, even when the player zooms in their view. A hollow box system would solve the above issues. The box would be a thin (1-2 px) square or rectangle that just barely surrounds the plane model. This allows the underlying model to still be seen. As the plane gets closer, the box would also enlarge to surround the model, until at some distance it fades away completely. 1. Approaching the transition range, the player is already seeing the model inside the box. Therefore, when the box fades away, it’s not as abrupt a transition. The player is thus more likely to retain a tally. 2. Players can still zoom in to get a visual ID and assess aspect at ranges where the hollow box is visible.

Yes! How about 10/20/40/60/80/100/120/140 instead?

I’d like the option to skip the CMWS page when using George from the CPG seat. The CMWS settings are already set up before I swapped to CPG seat from the pilots seat. The CMWS page just becomes an extraneous page to have to flip through. For players who wish to fly a single player mission exclusively from the CPG seat, they can keep the existing option to have the CMWS page, or use bindable hot keys for those options.

When exiting F10 Map back to cockpit on a busy MP server (Operation Levant), the game experiences several long stutters about a second each, followed by a terminal freeze and CTD. dcs.log

Using OpenXR and Virtual Desktop dcs.log

Suggestion: set the dot size based on degrees or mils, instead of a fixed number of pixels. For regular screens, you can calculate based on the user FOV divided by the screen resolution. For VR displays, you have the each headset’s rendering FOV and display resolution.

Paddle switch

The NTTR map uses West for Longitude.

In the mission editor, placing a "SAM SA-10 "Grumble" TEL-D" actually puts in a 'S-300PS 5P85C', and vice-versa. The "SAM SA-10 "Grumble" TEL-C" places a 'S-300PS 5P85D'

To add, a CASE I recovery doesn’t start at the break. You won’t be able to safely make a Marshall stack over the carrier at night with multiple flights lights off and radio silent.

Bug: the Course Line on the EHSD is always rendered in the default yellow-green color, even if the other elements of the EHSD are in a different color via the MAPM -> COLOR option.

Depends on the level of alert. For the highest state of readiness you might have a couple jets idling at the departure end of the runway ready to go.

Against a superior pilot in a superior plane? You’re gonna lose for sure. But not for the reason you think. You can’t go into a fight thinking you’re the worse pilot in a worse plane. You have to believe in yourself and your airframe first!

It’s possible to have a sophisticated model without physically stimulating each electromagnetic wave. It’s all about how many input factors you’re considering. For your sonar example - imagine a submarine game where the sonar model doesn’t take into account surface ducting or the effect of the thermocline.

I think you mean MRM? As in MRM / DGFT switch? No difference between MRM mode and AA master mode. The main advantage is you can be in AG mode, and with one flick of a switch, go to either DGFT or MRM mode, and then flick back to AG mode.

It used to work that shooting a Super 530D while in TWS automatically switched you to STT. Does that still hold true?

If the carrier is set on a constant speed and heading, you can set a waypoint where you expect it to be at the time you plan to return from your mission. If you happen to arrive early, just backtrack towards your starting waypoint and you should run into the carrier.

Can confirm this bug is still present in both single and multiplayer modes in the latest Open Beta. Track attached. Like the other players, I had problems after: 0) Changing elevation and distance via Jester menu (no problems here) 1) Launching Phoenix in TWS 2) WCS auto-switch to TWS-A Turn cold... 3) Change elevation and distance via Jester menu - Had to go to RWS mode as it was stuck in TWS-A even after I turned cold and Jester won't let me change elevation. Turn hot... 4) Launch Phoenix again 5) Bug begins! CLICK CLICK CLICK!! Not able to use any ACM modes or STT lock. Sparrows only work in Boresight mode. F-14 Bug.trk

Command Modern Operations has fire and flooding damage for ships. The damage accumulates over time until the crew is able to stop it. The unit’s skill level determines how quickly the damage gets under control. A low skill crew could lose the ship, when a highly trained crew could save it.

While we wait for ED to add a waypoint indication, a workaround is to use the course line, which always indicates the required course TO the selected waypoint to determine which one you’re heading to.

True but this is a concession for gameplay purposes.

I would like an option to have the LSO grade given to you via speech after landing in addition to the current system. It would be really neat. That is all!

For the Tomcat, if you advance the throttles to MIL or higher, the speed brakes automatically retract.

Thanks! Does this version pass IC?

Multiply the radar altitude by the cosine of your bank angle? Just speculation, but doesn’t seem that hard to do.