nomdeplume

All you can really do at the moment is make the tanker fly at its maximum possible speed, so it's unable to accelerate further. Try mashing 9999 into the speed field, might have to experiment with different altitudes too.

Try creating a new mission and placing a 342M. Or, deleting and re-adding it to an existing mission. That worked for me with the open betas. Weapons panel in the centre, below the pedastal. Got to switch it on (which will give you your count of rockets and shells remaining) and below it there's two guarded switches next to each other, left is rockets, right is cannon. To actually fire them, master arm must be on and the sight must be lowered. When you see the reticule you're set.

In addition to the Vivianne controls, I've also noticed that the throttle can still be controlled after commander and pilot are dead. For consistency with other modules, please consider setting it so that: if both pilot & commander are dead -> black screen as well as freezing controls if crew member player is currently controlling is dead -> kick player to the other seat (I think the Huey does this). Will need some reconsideration when multiseat arrives.

Sorry, wasn't game to post it there in case it wasn't actually a bug. :) Edit: as penance for not posting it in the right place, I've recorded a track and also uploaded a video. Might be helpful to be able to just see it. Video is in the spoiler: While I was editing the video, I noticed one of the times when I switched from PIC to PID, the distance went from 170 to 400 for one frame only, then back to 160. Don't know if this is a clue, or just an anomaly. Only happened once, but the recording was only at 30 FPS so it's possible it happens more often but just didn't get captured. But if it's occasionally getting incorrect values for the distance, it might explain the bizarre behaviour. Sequence of stills of the distance anomally are attached. It's from just after 1m30s in the video. M2000C Closure Rate.trk

Noticed this for a while, but thought I'd finally ask about. When tracking a target in PID/TWS mode, the closure rate is quite different (usually lower) than the rate when locked in PIC/STT, and also fluctuates a lot. Maybe that is correct behaviour, but the icons on the VTB move smoothly as if they're being interpolated, and it seems like a highly undesirable thing for the system to do. It seems reasonable that PIC would provide better information, but the way the closure rate in PID oscillates between values suggests it's calculating the rate based on a 'snapshot' of the target's position/velocity at the time it was last scanned, rather than an interpolation of its probable current position. Attached is two screenshots taken a second or two apart, of the same non-manuevering, constant-speed aircraft. First picture is PIC, second is PID. You can see the big difference in closure rates presented, but it doesn't tell the whole story as in PID mode the closure would start at about +55 knots and decrease to -50 knots or so, then jump back to +55. This behaviour seems to be consistent and easy to reproduce. It makes PID mode much less useful than it otherwise would be, both for engaging enemies and for using it to intercept friendlies (e.g. tankers) or just to stay 'tied' to your flight lead.

There's two separate 'game options' in the Gameplay section; are neither of them staying off? Also, are you using any particular missions? The mission files themselves can enable game mode, so if you're only trying certain missions it could be that simple. You could try deleting your options.lua settings file so the game generates a new one - maybe it's gotten corrupted or something. You can find it under your user profile directory in Saved Games\DCS\Config. Also - what version of DCS are you using?

Just in case you've actually been using a mod to do this ... this is built-in functionality now.

Worked out where I'd seen it - the MiG-15 actually has this! Since we're pretty off-topic already I don't want to embed a video and can't work how to link to YouTube without it embedding, but if you search YouTube for "MiG-15 takeoff from Runway 2, KSAF, NM, USA" you'll see someone running through the startup checklist and taking off in a MiG-15. ADI is brown above horizon and blue below it.

Well, both the primary and standby ADI are off/inoperative, so I'm not sure how much should be read into them. The stranger part to me is the lack of visible pitch markings on the primary ADI, but maybe they become visible when it's uncaged?

The point is that any reasonable "repair" activity would necessitate moving the aircraft. Moving the aircraft will invalidate the INS alignment. The A-10 has a GPS that continually corrects the INS position, but the M-2000C does not.

Why is it upside down? And why we never care? I think they're referring to the way some countries seem to use a dark area to indicate 'above the horizon' (sky) on the ADI while the light area indicates 'below the horizon' (ground). As opposed to the US (and lots of others) that use a light colour (usually blue) to indicate the area above the horizon and a dark colour (usually brown) below it. This aircraft is obviously quite a bit upgraded and modified compared to the F-5E-3 - radio panels in the centre (+ VHF radio), and the right panel seems to house some kind of navigation system so presumably it has an INS and/or GPS. So I'm not sure why Manuel would assume "our" ADI should be the same as the one in that aircraft. Or maybe they just want it as an option for some reason? Going a bit off topic, but I found this post which has a picture of the modernized Brazillian F-5EM glass cockpit, with a pic of the original cockpit below it. Pretty neat.

No idea still. There's a few things they did in a different order to my usual startup, but I've spent at least an hour trying variations of the start procedure to try to cause it to occur but had no luck. Originally I thought it might be related to enabling the trim and/or AP channels before the gyros are ready but that doesn't seem to be it.

Same as with MiG-21, Huey, P-51, et al: it doesn't. ME waypoints won't do anything, as it doesn't have a navigation system that uses waypoints.

Took control after your first few attempts and couldn't get it to work either. Also noticed the magnetic brake trim was not working. I had that happen in the 2nd campaign mission with the -M (prior to the latest open beta updates). Not sure what causes it but in that one I had difficulty clicking in the right places when spinning up the gyros. Restarted your track, took control right at the start, went through my usual startup procedure and it all worked normally - so it's not the mission and is most likely something to do with the specifics of the startup. I've saved my track and attached it if you want to play "spot the meaningful difference", but I'll do a few more tests and see what I can figure out. Edit: after much testing I still can't work out how to reproduce this. :( Replayed the track, took control after startup, verified auto-hover wasn't working, landed, shut down, after a cold start the auto-hover was fine (magnetic brake trim still didn't seem to work though). SA34L AutoHover Test 2.trk

Haven't played in a while, eh? :) http://forums.eagle.ru/showthread.php?t=164408

They don't release betas on Steam, and M-2000C is still under heavy development. So... "when it's done", I guess? :)

I think they received more/better information subsequent to that. Though in a way it's still correct, the close-combat modes available with cannon/Magic are not available with S530D. But, the Super has its own close-combat modes.

Contrail formation depends on temperature and humidity, so with different weather conditions it can form much lower, although there's usually a maximum ceiling after which they'll stop, as well. Just something to keep in mind - you'll need to adapt tactics to the environment.

When it's ready. The Black Sea + NTTR integrated version will be 2.5 (NTTR open alpha is 2.0). There's some gamebreaking issues with head tracking in 1.5.4 still so that's most likely what's holding up the release, but there may be other quality issues they're still addressing. But the answer is always: when it's ready.

Well, I definitely can't reproduce it. Using any mods? Tried running a repair of DCS? Since it's also occurring with new missions, could perhaps try uploading a .miz here which you're having the issue with and see if it occurs for others.

1.5.4.54316 (also in previous 1.5.4 open beta). When saving or loading a mission with dynamic weather, the pressure zones are displayed as grey circles, similar to the view when you click on the Weather icon, with the "H" or "L" in the middle of the zone but without the wind strength/direction symbols. Reproduce: On load: Open a mission with dynamic weather enabled. Most/all of the map will be 'dimmed' because it is covered by the weather system(s). On save: Simply pressing the 'Save' button to save the mission file will result in the weather systems being displayed. Workaround: Pretty simple, just click anywhere on the map (without any tools selected) and the pressure zones will disappear.

Any more information? Particular aircraft? I can move waypoints around as always.

Any movement on this issue? Still seems to be the case that explosions etc. only produce sound in the first mission you run. Are more logs still required to isolate the issue or is it just on the to-do list?

I suspect they don't want to have maintain two completely separate view control methods for the rest of time. That will add constant overhead to the development process, both for ED and third party developers who have to test and support both methods. Plus: not all devs may have a VR headset, and in future some may only have VR headsets but no TrackIR. There's also likely to be more types of headsets and developers won't have all of them. So, creating a single unified view control system that works properly with all devices makes sense in the long term. Some teething issues are to be expected, and if they can't iterate on these types of changes in an open beta then where on earth are they supposed to?

Is the magnetic brake trim working the same in the -L and -M versions in the current open beta? The -L version seems to work exactly how I would expect, while with the -M I still have no intuitive sense of what it's doing. Edit: never mind, seems -M in newly created missions works the same as the -L. Fixed my older test mission by deleting and re-adding the -M.