Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About MichaelGER

  • Rank


  • Interests
    PCs, Firefighting
  1. Default clock and the driver vsync setting is default (the application can decide). now you know why i am so confused about your overheating statement :D Edit: Disabled vsync, pushed up to 91°C. No driver crash after playing some minutes with 91°C
  2. It happens totally random, sometimes on start, sometimes in the menu and sometimes after playing a long time. The temperature of my card is around 75°C when the crash occures (even lower if it crashes very early). So its hard to believe that overheating is the reason... My VSync is enabled btw
  3. MichaelGER

    'Flushing' in ArmA 3

    I got the same problem. It looks like arma doesnt take any input after the driver crash.
  4. Its not overheating. Its a well known issue (nvidia driver/arma3 combination). A lot of entries about this problem can be found in the bugtracker. http://feedback.arma3.com/view.php?id=579
  5. About two Years ago I stopped ArmA scripting because I started java programming. Now I can do both things with one language. Very great feature!
  6. Alright, I'll use the other way again with publicVariable and the EH to add the action. Yes, I'm using this for add the action to the new created objects. Thank you, Xeno. Very helpful post!
  7. I did some advanced testing (I restarted the server and the client every time because of this bug.) First run: server.sqf (is called via radio with [1] execVM.... or [2] execVM...) The diaglog.sqf (to log everything) The results: The second run (without publicVariable the object and only used the first method) changed server.sqf: results: I think the problem has been solved (thx @ST_Dux for the tip and of course all others that helped) and hopefully the results of the test can help other people to understand setVariable better. E: Sorry for the double post but I thought this test shouldn't be mixed up with other stuff.
  8. Ok, misunderstood you. Yes, I know what you mean. The name of the object on the client is something like this while the name on the server is different. Both mean the same object but setVariable doesn't recognize that, am I right?
  9. you mean something like this _com = createVehicle [comobj, position _x, [], 0, "none"]; publicVariable "_com"; ?
  10. The script that spawns the object is running serverside and addaction is a local command if you mean that. But its possible to add the action global with setVehicleInit (thx @shk btw :) ) which I use directly after creating the object. Yeah, but the value is transferred, thats all I want :) The other script gets the value by _this select. E: btw I dont use the activecoms as pubvar anymore because shk's better solution of setvehicleinit.
  11. I added the action now via setVehicleInit. That way seems to be a little bit faster than with publicvariable and the pubvareventhandler btw. But it doesn't fix the error, the setVariable still wont be broadcasted.
  12. Not sure what you mean. Here are some significant parts of the code: _com = createVehicle [comobj, position _x, [], 0, "none"]; activecoms = activecoms + [_com]; . . . publicVariable "activecoms"; in the other script: { _x addAction [....] } forEach activecoms;
  13. The "name" of the object is the return value of createvehicle. In case of creating a hummwv it will be named as on the client I will try your way to name it. ---------- Post added at 03:58 PM ---------- Previous post was at 03:22 PM ---------- Bit more difficult to implement than I thought. I will describe it better: I spawn an object on the server. The return value of the createVehicle is written in an array. This array is publicvariabled to all clients. The client adds an action to every element of this array. The script called by addaction uses the setVariable command. The problem is i cant use a constant name because its a dynamic spawning system. Tried your way of naming the object but the client is still saying the object is
  14. An object is one of these supported types but it doesnt work. Let me describe the problem: I spawn a object (generator, but also tested with a hummwv) local to the server. Lets name it object1. Then i use this command on the server: object1 setVariable ["test",true,true]; On client: diag_log [object1 getVariable "test"] it will write in the .rpt: Execute setVariable on the client will also return <null> on the server. A object like a generator or a vehicle should be a supported type of the public value, am I right? If no, is there a workaround for it?
  15. E: nvmd changed _caller to player fixed it :) thx for help guys.