delevero Posted June 11, 2018 Posted June 11, 2018 (edited) Hello I have a strange bug today. When i make a new mission in the editor and place the Stenis carrier, and the f18c in a ramp possition and load the mission. Then everytime the nose wheel hydraulics are extended as seen on my screenshot. Maybe this is effecting everything i do with carriers even in other missions ? ( note on land the nose wheel piston is compressed and i dont see the dark piston, but only the white cover and tow bar ). - Note the dark hydraulic piston on nose wheel is extended just like you are landing.. it should be compressed on the ground. This happen all the time when i start cold and dark, but also if i start with the engine running ready to taxi. If i start ready for takeoff then there are no problem. I find this bug very strange since I have been flying and taxi without issues on the stenis since release of the hornet. The only thing I have done today is to install 4 skins in the folder of. ( my game is the stand alone dcs world open beta ) I have manualy created the folder \fa-18c_hornet D:\DCS World\Mods\aircraft\FA-18C\Liveries\fa-18c_hornet By the way this happen after i used a usermade mission from the ED user file section named F18 myCarrier_Starter.miz or F18_TRAINING_MISSION.miz that had some Static objects of f18c and other planes placed on top of the stenis. - I dont know if this mission somehow have damaged my original game or the F18c, or if i somehow can "clear a cache " or someting I like to add that it dosent matter if I use a default USA f18 with default skin, or if i use the "danish" ( denmark) with our custom skin. No matter what the f18c is stuck and cannot taxi. Edited June 11, 2018 by delevero
muehlema Posted June 11, 2018 Posted June 11, 2018 Yes, same here. I had this too in one mission X-Plane 11.5x / DCS 2.5.6 / P3Dv5 / Aerofly FS 2 / War Thunder Win10-x64 | ASUS Z390 Maximus VI | Intel i7-9700K @3.6GHz | Corsair Vengeance LPX 32 GB DDR4 | 6TB SSD Samsung 850 Pro | 2TB M2 PCI 4x | ASUS GTX 1080 ROG STRIX 8GB DDR5X | TM Hotas Warthog | Saitek Combat Pedals | Oculus Rift S
delevero Posted June 11, 2018 Author Posted June 11, 2018 here are the missions that I suspect created this bug. Warning might do not use, they might damage your game. NOTE.. I have maybe renamed the missions wrong I all of a suddent had several copys of them all with same name...f18 myCarrier_Starter.mizf18_TRAINING_MISSION.miz
delevero Posted June 11, 2018 Author Posted June 11, 2018 FIX...: I found out how to fix this bug.. Run a command prompt and Repair your DCS world Navigate to your dcs world folder \DCS World\bin Hold Left SHIFT and right click with mouse anywhere Select OPEN command prompt TYpe CMD DCS_Updater.exe repair Then the f18c will work again. But at least now we know that a mission can damage the F18c
sniperwolfpk5 Posted June 12, 2018 Posted June 12, 2018 I am facing same issue. Yesterday I have converted a Bigbird server track to miz for single player practice and I was stuck on Stennis can't taxi even using afterburner. It happens on both cold and hot aircraft. Win10, Intel 3rd Gen. Core i7 3.8Ghz, 20GB ram, Nvidia Geforce 1060 6GB Opentrack (Download it from HERE), PS3 Eye, Saitek x52-pro Joystick, DIY Rudder Pedals, Google Cardboard with DCS World English is not my native language
Recommended Posts