RHS Feedback - USAF
The DUKE system appears to work in singleplayer and when the player is the host of a local multiplayer server (non-dedicated). This makes sense since the player would be the server in both of these cases, where enableSimulationGlobal is sufficient.
A suggested fix is to update the duke_jammer function to remoteExec the enableSimulationGlobal command on the server. I'm uncertain if this is the most performance friendly option, but the main loop of the duke_jammer only runs every 0.5 seconds so it may be acceptable.
2. Start the mission and place a Large IED.
3. Get into the MRAP and enable the DUKE system. Confirm that it says DUKE online.
4. Scroll and touch-off the IED you placed. Notice how it explodes and that the DUKE system did not prevent it from exploding.
In the mission I've provided, I have made a variant of the duke_jammer function that uses remoteExec for the enableSimulationGlobal command. To see how this results in the intended behavior do the following:
1. Restart or reload the mission.
2. Place down a large IED.
3. Get into the MRAP.
4. Use the debug console to locally run the duke_test_2.sqf script included with the mission. (execVM "duke_test_2.sqf") Notice that the systemchat shows that simulation has been disabled for the IED.
5. Scroll wheel and attempt to touch-off the IED. Notice that the IED does not explode.
6. Drive approximately 50 meters away. Notice how the IED then explodes, as intended.
Video showcasing behavior: https://youtu.be/1R2aZ53Ne3c [^]
duke_test_vanilla_MP.Stratis.pbo (17,401) 2020-06-26 04:46https://feedback.rhsmods.org/file_download.php?file_id=2187&type=bug