hreich Posted April 14, 2010 Posted April 14, 2010 I tried everything, reinstalled 3 times now, lost 2 deactivation while trying to fix this stupid bug...I know i asked before, but to repeat again - why dont i get update from fac controller in a-10 campaign missions? I checked, and i am inside the trigger zone, and there is no orange smoke, no fac, i checked the first 3 missions - the same result. Only time i get fac to talk is when targets are destroyed. [sIGPIC][/sIGPIC] Pilot from Croatia
EvilBivol-1 Posted April 14, 2010 Posted April 14, 2010 Hard to diagnose with so little information. Put up a track of your flight for review. - EB [sIGPIC][/sIGPIC] Nothing is easy. Everything takes much longer. The Parable of Jane's A-10 Forum Rules
hreich Posted April 14, 2010 Author Posted April 14, 2010 Ok - I am posting trk file Ok, here you go...you can see that i am inside trigger zone..NO FAC.trk [sIGPIC][/sIGPIC] Pilot from Croatia
EtherealN Posted April 14, 2010 Posted April 14, 2010 I tried everything, reinstalled 3 times now, lost 2 deactivation while trying to fix this stupid bug... Please note that deactivation is not necessary for simple reinstalls. New activations only get triggered with hardware changes or operating system reinstalls. [sIGPIC][/sIGPIC] Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules | | | Life of a Game Tester
Distiler Posted April 14, 2010 Posted April 14, 2010 (edited) That track has something really weird going on just after you start rolling. It's easy to spot, it's like a "reset", a "glitch" (don't know how to explain it better) If I watch your track, FAC trigger is not activated, but if I take control at the start, just before that weird thing, FAC trigger activates. If I take control after that weirdness happens, the trigger doesen't work. I don't have any explanation for that weirdness. Wich mods are you using btw? Edited April 14, 2010 by Distiler AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2
ShadowVonChadwick Posted April 15, 2010 Posted April 15, 2010 I tried everything, reinstalled 3 times now, lost 2 deactivation while trying to fix this stupid bug...I know i asked before, but to repeat again - why dont i get update from fac controller in a-10 campaign missions? I checked, and i am inside the trigger zone, and there is no orange smoke, no fac, i checked the first 3 missions - the same result. Only time i get fac to talk is when targets are destroyed. I also have noticed this but with tower responce usualy after a very long mission (1hour or two) RyZen5 3600x, MSI GamingX RX 5700xt, AX-370-K7, 16 Gig G-Skil 3200 :thumbup:, Antec 650w (Still),Win10 on 256G 870 NVMe, 860+850 Evo for Apps, 2x1TB WD HDs for :music_whistling:, TR5 :detective:, Hog stick:joystick:, 3x TM MFD Bezels. a 32" AOC, @ 2560x1440, no floppy & a crappy chair :pain:. Its hard to find a chair that accepts you as you grow.:pilotfly:
hreich Posted April 16, 2010 Author Posted April 16, 2010 Ok...that could be because when i start mission i PRESS ALT+J combo, so i give control to AI, and then take it back (this is only way that i know of for force feedback joystick to work without nose down trimming issue)... So it could be a bug introduced by giving control to AI for split second! That track has something really weird going on just after you start rolling. It's easy to spot, it's like a "reset", a "glitch" (don't know how to explain it better) If I watch your track, FAC trigger is not activated, but if I take control at the start, just before that weird thing, FAC trigger activates. If I take control after that weirdness happens, the trigger doesen't work. I don't have any explanation for that weirdness. Wich mods are you using btw? [sIGPIC][/sIGPIC] Pilot from Croatia
Distiler Posted April 16, 2010 Posted April 16, 2010 Ok...that could be because when i start mission i PRESS ALT+J combo, so i give control to AI, and then take it back (this is only way that i know of for force feedback joystick to work without nose down trimming issue)... So it could be a bug introduced by giving control to AI for split second! That is curious. Perhaps, the AI change makes you'r airplane ID different so the trigger doesen't activate. Don't know about trim down issue. AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2
Recommended Posts