Grenadier-Ghost 1 Posted May 16, 2017 Good morning. Since I was upgrading to 64bit, I noticed that some times you are bugging trigger, drive. The same problem has been found by a friend of mine who as I edited missions. You are required to delete the item that creates the problem, save and re-insert the item with the code you used before. With that I just want to make a note so that you can check my words. It's really frustrating to create a mission and then get crazy to look for the problem that first worked and after it no longer works. Thank you for your attention and excuse my English Share this post Link to post Share on other sites
Midnighters 152 Posted May 16, 2017 I'd think the only thing that actually changed in terms of editing in arma 3 would be extensions. commands, triggers, any of that sort did not change. Nor did it break anything. You need to elaborate on the specific problem. This very well could be just a bug. Are you implying that trigger "drop down" menus are not being dropped down? Share this post Link to post Share on other sites
pierremgi 4851 Posted May 17, 2017 IMHO, there is no more reason to replace some non-working triggers, or else. This problem occurred at the beginning of Eden 3D, when the mission.sqm had to be reformatted with the new class attributes... More recently (since 1.68), I also experienced that all triggers with no condition at all (blank),which worked as activated ones, failed in new version. And yes, for that, you need to write: true in the condition field to make them work again. Why so poor compatibility? I can't say. But, for sure a blank field condition wasn't the best thing to do... I did for my bad! Share this post Link to post Share on other sites
Grenadier-Ghost 1 Posted May 17, 2017 The trigger included was recent, not put in a previous version. At the beginning of the mission creation everything was running smoothly afterwards, with the passage of time, changes to mission changes strangely did not work. I repeat that I had not made any changes to that trigger, and I did not include strange scripts, but only a trivial line of code. I have the feeling that the more you become bigger and elaborate the more mission you have these unstable behaviors. Now that I think about it during editing I got some crask, caused by not what, so I restarted the game. Can I imagine that it was due to possible cracks during editing and that they damaged part of the missions.sqm file? Share this post Link to post Share on other sites
