Posohm

Get rid of DCS-export if you´re using it, caused a crash with the TGP. Also caused a crash accessing P3 on the DED-Link16 page.

Was the track looked at before this was marked correct as is? TWS seems like it's broken as is. Cannot promote other tracks to system tracks with TMS up...

Tested in PG map. Fly towards two Tu-160´s spaced 1nm apart at 30.000. Set 80nm scope, RWS, A6, 4B - Note both aircraft visible on scope. TMS right long - enter TWS. 1. Wait for track files to generate ( note altitude numbers are superimosed on leader lines, making them impossible to read). 2. TMS right several times, note TWS jumps between the two tracks as expected. 3. TMS aft long to RWS again, then TMS right long again to enter TWS. Instead of TMS right to jump between tracks, TMS-UP short to bug a target. Note target hollows out. You can now no longer bug the other guy with a TMS UP short nor TMS right short to jump between tracks. Only way to reset is to TMS aft long back to RWS, then follow steps 1 and 2. Expected behaviour: TMS-up short should bug target under cursor or STT if cursor already over bugged target. Track file included. tws_strangenessr.trk

Hmm - maybe its because UHF/VHF is mapped to SRS and not UHF/VHF transmit in dcs ;) Can't have both though, lest I be bringing up the comm menus all the time :/

Not entirely sure this is implemented in tape your modeling but a pilot should be able to return to the previous frequency he was on, for example by pressing COM1-ENTER on the ICP. Implementing this would facilitate better/quicker channel hopping when you can anticipate what the next channel is that you're going to be on, effectively cocking the next frequency you're going to be on. Granted its quick and easy when it's just a single digit channel number, but saves some seconds when its manual frequencies. Example; You're on Channel 1 and you know that following line up, you're going to be checking in on 250.10 ( departure for example ) then after that you're pushing strike on channel 5. So being the good wingman - anticipating this, you press COM1-2510-Enter, then quickly again COM1-enter ( back on channel 2 ). You line up on the runway, hear lead say "push 250.10" - all you have to do is press COM1-enter...

Hello :-) Are there plans to implement this? When UHF / VHF is transmitting ( PTT held ) the DED label should highlight.

Indeed. According to AFI11-2F16V3 the max crosswind component for formation takeoff's is 15 knots. I'd be interested in seeing a trackfile of a fmn takeoff in those conditions now :-)

Be that as it may - there's the track file FWIW. Be interesting to see what ED testers come up with in cross wind conditions.

Just to clarify the scenario - NWS is already in a slight turn and you disengage the NWS, it's as if there's a mechanical force that drives the NWS to center - seems off. Think about if you were pusning a shopping cart along with some sort of power steering, then as soon as you disengage the steering, the wheels re-center no matter what the path of the cart is. That's the point I'm trying to get at.

Here is a track file - 10 knot crosswind from the left. NWS to steer below 60 knots, as soon as NWS is disengaged it feels like the nose wheel is forced to center rather then caster. Wobbling starts and is irrecoverable. https://www.dropbox.com/s/3ukkhhg3d8vaq0z/10kt_crosswind_crash_on_takeoff.zip?dl=0 You´ll have to fast forward through the taxiing. The mission was set to takeoff from runway yet it dumped me in the ramp O.o Also - noticed some sporradic wing vortex on bumpy taxiways - strange.

Just to underscore DRAKO's post - I'm having the same issues. Right before rotating is the most dangerous part - it really feels like a race to get airborne before becoming one with terra firma.

In a related topic - but perhaps different enough to warrant a separate thread: It seems only the X-axis ( i.e. pilot head moves only left/right) is recording for clients, not up/down. This could be a viper thing, not sure. The same can be said for client's nose wheels. Their recorded for the player only. Are those things sent out over the wire at all?

Hi Apologies if this has been asked for before, but if it's do-able somehow - could you please provide a hot-key to restore players head movements after it has been manipulated in a track file? Alternatively - negate switches between views counting as intervention. Currently the pilots head movement is lost upon manipulating the view in any way - e.g. switching to F2. Justification: Implementing this would go a long way towards making better in-game cinematic where the pilot's head is in view - which would also results in better marketable material for ED. Thanks! :-)

Just wanted to drop by and give Hav a thumbs up review. Bought a UTC II pro - shipped to Iceland without any problems. Transaction was a breeze and quicker to place then through Amazon 1-buy click, definitely helps with impulse buyers like myself :-) So glad to be rid of TiR5 wires. This will serve nicely until its VR time. :-) Thanks!