davidp57 Posted February 8 Posted February 8 Hi @BIGNEWY, here's a new bug report ! How to reproduce: In the mission editor, either set a "smoke" trigger command on a trigger zone, or use the `trigger.action.smoke` API command in script. What happens: The smoke effect starts, and a neutral ZIL-135 unit appears on the F10 map, which I can select and see coordinates of. It's a ghost unit though, there is no model in the 3D world, and the other units don't react to its presence. What I expected: I expected a smoke marker, nothing else. Screenshots: Here's a test mission: Testsmoke.miz Zip - VEAF :pilotfly: If you want to learn, talk and fly with french-speaking friends, the Virtual European Air Force is here for you ! Meet us on our Discord and our forum If you're a mission creator, you may want to check the VEAF Mission Creation Tools (and its GitHub repository) a set of open-source scripts and tools that make creating a dynamic mission a breeze !
Flappie Posted February 8 Posted February 8 Salut David! This issue was reported internally just a week ago. 1 ---
davidp57 Posted March 20 Author Posted March 20 Merci Flappie ! Zip - VEAF :pilotfly: If you want to learn, talk and fly with french-speaking friends, the Virtual European Air Force is here for you ! Meet us on our Discord and our forum If you're a mission creator, you may want to check the VEAF Mission Creation Tools (and its GitHub repository) a set of open-source scripts and tools that make creating a dynamic mission a breeze !
Recommended Posts