xaoslaad Posted March 17, 2016 Posted March 17, 2016 Is there a bug in 1.5 or has something changed in the takeoff procedure? I can not in any way move from the start position on the carrier. Even at full burn I am stuck in place.
DarkFire Posted March 17, 2016 Posted March 17, 2016 That's strange - if memory serves the 'tether' should automatically disconnect when you hit afterburner. I take it you pressed the key to move in to launch position ("K" I think)? System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit. Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.
xaoslaad Posted March 17, 2016 Author Posted March 17, 2016 U moves to takeoff position. I created a new mission with just a plane and carrier to test and can't move. I tried takeoff from runway, parking hot, ramp and ran yhe startup, etc.
DarkFire Posted March 17, 2016 Posted March 17, 2016 U moves to takeoff position. I created a new mission with just a plane and carrier to test and can't move. I tried takeoff from runway, parking hot, ramp and ran yhe startup, etc. Did you still experience the problem during runway & parked starts or just with the carrier? System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit. Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.
Ironhand Posted March 17, 2016 Posted March 17, 2016 U moves to takeoff position. I created a new mission with just a plane and carrier to test and can't move. I tried takeoff from runway, parking hot, ramp and ran yhe startup, etc. Are you certain that your throttle is allowing full power (afterburner) for takeoff? This has traditionally been the issue, when folks have had this problem in the past. FWIW, I just created a quick test mission as a double check and was able to take off without any problem. 1 YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.
xaoslaad Posted March 17, 2016 Author Posted March 17, 2016 (edited) Probably was the case. I had some double mapped axes in the open beta. Once I fixed those I could take off. 2.0 and release were fine. Too many versions * aircraft to keep track of. Thanks! :) Edited March 17, 2016 by xaoslaad
Recommended Posts