chromium Posted June 3, 2020 Posted June 3, 2020 Hi, I noticed that S_EVENT_ENGINE_SHUTDOWN event is not triggered anymore for client. I attach a log, a test mission with a small lua code that show message for takeoff, land & shutoff events. If you fly that mission in SP or MP as host, it works. As client, it does not. I also attach dcs.log and the track file.BugCheck.mizserver-20200604-000514.trkdcs.txt Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.
ZlinMan Posted June 4, 2020 Posted June 4, 2020 I guess ED or the testers once again won't understand for years where the problem is ... Waiting for the return of: -TLP- -True LAN Play- Multiplayer without permanent internet connection to ED master-server. Plane wishlist: Antonov - AN-2
chromium Posted June 4, 2020 Author Posted June 4, 2020 I'm optimist, I might believe in a couple of build rotation to have a fix. They have a much more important issue to look into, reading the forum (lights, crashes). But even if it's going to be complicated, I can rewrite my things to adapt to this: it's the modder works. I just wanted to let them know so that they can try to reproduce & fix if it's simple, cause it doesn't seem a change in code behaviour but a real bug. I think that this should be done by everyone that is using openbeta and also has sufficient skills to help. Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.
ED Team BIGNEWY Posted June 4, 2020 ED Team Posted June 4, 2020 @chromium Reported, thanks @ZlinMan we are dealing with hundreds of reports on the forum, sometimes it takes a while to get around everyone, confirm it and report it. Occasionally we will miss reports, it is not intentional. Thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
chromium Posted June 4, 2020 Author Posted June 4, 2020 You're welcome! Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.
ZlinMan Posted June 5, 2020 Posted June 5, 2020 (edited) @ED Community Manager Thank you for the tireless work of browsing these forums and other resources. Unfortunately, one can assume that misunderstandings of various kinds arise even if knowledge of problems and their extensive description is given. Unfortunately, for too many different reasons, these will persist too often a long time. A prime example would be following bug: The event that a player entered a unit (S_EVENT_PLAYER_ENTER_UNIT) is not fired correctly und MULTIPLAYER. see: https://forums.eagle.ru/showthread.php?t=186666 see also: https://forums.eagle.ru/showthread.php?t=206069 and: https://github.com/FlightControl-Master/MOOSE/issues/692 Whoever reads through these excellent discussions can see that two parties are talking at cross purposes for a long time. Perhaps ignorance is also involved here? Unfortunately, there are some bugs that have been known for a VERY LONG time in DCS-World and are serious and cause major headaches for the scripting community. To put it cautiously and politely. Changes, corrections or improvements, also with regard to a comprehensible continuity or even cooperative documentation, are hardly or not recognizable. On the contrary - at regular intervals, ED publishes new, effective for the general public, alqays unfinished but nice-looking extensions - so called EYE-CANDY. There are some very talented DCS scripting freaks with skills and background knowledge who work tirelessly to improve this game with sacrifice - but unfortunately they feel long-term that they get little or no attention. It’s very frustrating. Others, after a great deal of personal energy, have probably given up trying to make further improvements. It's a pity ... It is more than logical that this also has an influence on the buyers, isn't it? Informations about possible DCS bugs, issues and informative discussions about it can still be found here: https://github.com/FlightControl-Master/MOOSE/issues?q=is%3Aissue+is%3Aclosed+label%3A%22DCS+bug%22 Thanks for reading. Edited June 6, 2020 by ZlinMan Waiting for the return of: -TLP- -True LAN Play- Multiplayer without permanent internet connection to ED master-server. Plane wishlist: Antonov - AN-2
Recommended Posts