BeforeBroadband

I'm not very knowledgeable on TelemFFB. I just turn it on, boot up the game (DCS in this case) and play. It shows F4U-1D as the 'current aircraft', and my stick doesn't move when I trim. Again, it and the BF 109 are the only two WW2 planes that don't. This is also the case when I don't use TelemFFB. Is there some setting that you can think of that I need to modify or something? Trim moves the stick for you without having touched any TelemFFB settings?

VP Force Rhino doesn't. Just tested it. I have Bf 109, F4U, both Fw190s, Mosquito, P-47, P-51 and Spitfire. Bf 109 and F4U are the only two in this list that don't. Stick forces get relieved, but it stays still.

Just tried this weapon for the first time and I used 'nose-tail' every time. Out of maybe five or six drops, the bomb failed to detonate only once. Out of curiosity, is the need for 'tail' an issue with how the fuses work, or is it just one of those weird DCS things? This weapon is pretty fun, by the way. I enjoy it almost as much as Tiny Tims. In case anyone's wondering about range, it seems to be limited by the radar which gets a target spike at ten kilometers.

I think they're not even there. The crew chief told me he placed them, but a relatively small amount of throttle results in the aircraft rolling forward.

It's like there's a sweet spot of speed/throttle and brake application that it likes, and is a stubborn donkey outside of that. It's doable, but this is definitely the hardest warbird to turn on the ground.

^Guys, please. It does seem very twitchy at all speeds. Perhaps that's accurate, but I would like to 'feel' a little more inertia. The acceleration felt slow to me too at first, but I think that's a combination of constantly having to get it back in trim and forgetting the airspeed is in knots, whereas most of the warbirds are MPH or KPH. I can't speak on the other issues, as I don't have the numbers. This thing has major potential. I'm hopeful we'll be in a happier state once it gets a proper update or two. Edit: Your note about it bleeding energy quickly. Part of that may be the fact that something seems off about the way the elevator input transfers to the plane. You pull what you think is a little, only to look at the G-meter and see you're pulling 4.5 Gs!

I have FFB with extension as well. The only part that took me time to get used to is the monstrous torque. It's also very sensitive, so I can imagine a short stick or controller must make this thing feel very squirrelly without dialed in saturation and curves.

I get people are frustrated, but can we make sure issues posted in Bug Reports are more substantial than 'this sucks'? That is not helpful.

This my least favorite wallpaper out of all the maps because of the low resolution. Normandy's wallpaper could definitely stand to be sharper as well, but this one is noticeably worse because every single building reminds me of how DCS looks in VR. This is a small complaint of course, but please give this beautiful map a wallpaper that does it justice!

You are Chaos SQD-1 with a wingman, Chaos SQD-2. That's only in mission editor, though; you're both non existent upon mission start. When I open up Dawn Defense in the mission editor, it shows both Apaches within the FARP listed in different parking spots. I'm unsure why they don't show up in the mission, but this renders it unplayable. I created the same type of heliport FARP in a new mission, placed two Apaches within the same unit in the parking spots, and it works fine. Something is causing an issue with this in this particular mission, but I can't figure out what.

Partially corrected, it seems. With today's update we now actually have HOBOS on the jet, but only two. The mission briefing says we're supposed to have four.

Very strange. Have your tried deleting MOUSE_BTNX from each of the three combos so that they just say {{key = ''}} ? If you've done that and are absolutely sure you don't have any mods installed, then I don't know what could be causing your issue. Guess we'll have to chalk it up to one of DCS' quirks.

I'm not sure why the issue comes back after you restart the game. It's also odd that you get no popup when hovering over the tooltip. Does this problem affect all your aircraft? Have you tried running the DCS repair tool and then trying these .lua edits? I use the MMB cursor toggle + Mouse4 transpose setup just like you.

Just tested it myself, as well. Caucasus, instant action, free flight, active pause. Very noticeable difference in fuel remaining between military power, minimum afterburner, and maximum afterburner. However, emergency afterburner fuel level was the same at the end of five minutes as maximum afterburner. Seems like a fairly important bug.

I just ran a repair and modified my default lua to match yours. Lo and behold, I got the red exclamation mark. Playing around with the lua, I believe I've found a fix for you. In your lua example, I then tried deleting only MOUSE_BTN2 so that it says {combos = {{key = ''}}, etc. When I booted DCS back up, no red exclamation mark, and assigning mouse button 2 worked flawlessly. Try that.

You're saying that's what yours shows before or after you modified the lua? Comparing yours with mine, I notice you're missing the 'Enable visual recon mode' combo, which is what my file lists as mouse button 2 by default.

Interesting how it usually seems to be Camera Tranpose that's the problem for most people when you search "DCS red exclamation mark" in google. The few other binding conflicts I had were kind enough to tell me what the exact problem was (all UI layer), but Camera Transpose has to make a nuisance of itself.

I hadn't thought of that. I have so few mods that I never bothered with mod manager, but maybe it's time to look into it.

'Camera transpose mode' has been doing this to me for a long time on every aircraft, regardless if I have anything bound to it or not. Hovering over it tells me nothing (see pic). It also renders 'camera transpose' non functional. The only thing that fixes it for me is to go to 'DCS World>Config>Input>Aircrafts>Common>Mouse', and edit the 'default' .lua file. This is what it normally says under 'keyCommands' in there: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, I notice it has mouse button 3 (middle click) listed for camera transpose, even though essentially every aircraft/crew position in the game uses a double middle click by default for 'Force cursor to show, toggle'. If I edit this lua by adding a third '{combos' like so: {combos = {{key = 'MOUSE_BTN2'}}, down = iCommand_ExplorationStart, name = _('Enable visual recon mode'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN4'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name = _('Camera transpose mode (press and hold)'), category = _('View Cockpit')}, {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandCockpitClickModeOnOff, name = _('Force cursor to show on/off'), category = _('General')}, }, the red exclamation mark goes away and restores camera transpose functionality. Slightly annoying that I need to do this after every update or if I run a repair.

Do we need to beg, ED? I can somewhat understand that in the past this may have been an extremely low priority, but now that we've begun getting official flyable unarmed transports in the game, the time for this to be implemented has come. Actually, it seems like every few newsletters you announce some random upcoming visual feature like highly detailed pilot eyelashes or aircraft tire flex. Surely, being able to see (even lower texture) personnel that you're carrying in a combat game makes sense, right? The larger the aircraft get, the worse seeing no troops feels. Is the back of the C-130 gonna be empty too?

Major thanks. Also love your night versions.

Word of warning: Bob will not attempt to dodge trees. Very nice to have a 'co-pilot' (even a very basic one) at launch, though. Should be mandatory for all aircraft with more than one cockpit seat. Well done, ED.

I might have to look into an MFD peripheral just for this. It absolutely sucks that VSD mode can't be full screen.

US Army CH-47F model doesn't have one.

I love this game, but man. Just a few steps into the startup process and a problem/bug(?) is there to greet us.