Devrim Posted January 25, 2012 Posted January 25, 2012 Hi. I'm sorry if this problem discussed before... While just flying for fun, I did bad landing. The blades stopped but Ka-50... :) Please watch that; (This video is not public.) I'm not questioning the physics of this game. But I wonder how a bug is that? Thanks. Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR >>MY MODS<< | Discord: Devrim#1068
PeterP Posted January 25, 2012 Posted January 25, 2012 (edited) Here is a uneducated guess: The physical-mathematical model of the terrain is not really representing what you see, and it is very simplified... .... the engine keeps on polling if the airframe will fall to the left or right - short: It can't decide. (Maybe because a programmer didn't really found it useful to spend hundreds of hours to see where this simplified vehicle-gerund interaction will fail.) Edited January 25, 2012 by PeterP
Devrim Posted January 25, 2012 Author Posted January 25, 2012 Here is a uneducated guess: The physical-mathematical model of the terrain is not really representing what you see, and it is very simplified... .... the engine keeps on polling if the airframe will fall to the left or right - short: It can't decide. (Maybe because a programmer didn't really found it useful to spend hundreds of hours to see where this simplified vehicle-gerund interaction will fail.) I played and tried to create same acciadent without damaging gears. I damaged lower blades and landed in the same way that seen in video (tried four times). This time Ka-50 didn't swing. May be the factor in my video was the front-gear... or I don't know... But, in my opinion, yes actually it's also related the physical-mathematical model of the terrain as you said. Because, in some crash situations such as on the ground or mountain, Ka-50' body never stops. Even fire has been extinguished, Ka-50's body always moves like nonsense. That's because of terrain issue I think... Make better landings :) :D :D Definitely. :) Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR >>MY MODS<< | Discord: Devrim#1068
Migow Posted January 30, 2012 Posted January 30, 2012 (edited) I played and tried to create same acciadent without damaging gears. I damaged lower blades and landed in the same way that seen in video (tried four times). This time Ka-50 didn't swing. May be the factor in my video was the front-gear... or I don't know... But, in my opinion, yes actually it's also related the physical-mathematical model of the terrain as you said. Because, in some crash situations such as on the ground or mountain, Ka-50' body never stops. Even fire has been extinguished, Ka-50's body always moves like nonsense. That's because of terrain issue I think... :D :D Definitely. :) it might be dynamic rollover pivot around a wheel gear then the helo spin and become uncontrollable http://en.wikipedia.org/wiki/Dynamic_rollover but damaging one rotor should spin your helo too so there is a bug if your helo doesn't spin in other test Edited January 30, 2012 by Fifou265 member of 06 MHR / FENNEC Mi-24P
Devrim Posted January 31, 2012 Author Posted January 31, 2012 Oh, I think I should have typed that I shut off the engines after every landing. The problem is that engines & blades stop, but body still moves. In second test that everything was like how it should be. Because the gears wasn't damaged. While typing these, I got an idea. I'll be back if found something. :p Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR >>MY MODS<< | Discord: Devrim#1068
213 Posted January 31, 2012 Posted January 31, 2012 you broke the rotor so the bottom rotor wasn't able to negate the torque made by the top one.
Devrim Posted February 2, 2012 Author Posted February 2, 2012 you broke the rotor so the bottom rotor wasn't able to negate the torque made by the top one. Thanks but, what is this answer for? Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR >>MY MODS<< | Discord: Devrim#1068
Jona33 Posted February 2, 2012 Posted February 2, 2012 the video Yes but that shouldn't happen after the rotors have stopped moving. Always remember. I don't have a clue what I'm doing
ARM505 Posted February 2, 2012 Posted February 2, 2012 You're seeing the sim equivalent of the old first person shooter model 'ragdoll' flopping around - remember the first shooters that used 'ragdoll' physics? Sometimes the corpses would jerk around after they've been 'killed' and were just laying there. The physics model keeps bouncing a part from one side to the other. Same here.
Winged Trainee Posted February 3, 2012 Posted February 3, 2012 you broke the rotor so the bottom rotor wasn't able to negate the torque made by the top one. This explains the spinning, but not the swinging after engines are off.
Recommended Posts