Started by DWreck1995, December 30, 2015, 06:31:38 PM
Quote from: edkiefer on December 30, 2015, 07:02:53 PMI got a few questions that might narrow down whats happening.When you say it closes and restarts you mean game restarts itself , PL didn't change ?Maybe you could try this, do the same but with game mode not set for this game.Last set the priority before starting game and see what happens (do this through options>configure CPU priority, and add game exe).The game might have some kind of protection running.Edit: Also does the same thing happen in task manager or Process Explorer.
Quote from: DWreck1995 on January 01, 2016, 12:35:56 AMWhat I meant by it restarts itself is as soon as I right click "arma3.exe" the screen goes away, aka crashes. But if I go back to the bottom right corner of the screen where my applications are running and it will show up as running still so I can reopen it immediately.I tried it with and without gaming mod enabled.I've also manually set the priority but it does not change.What did you mean about task manager?
Quote from: edkiefer on January 01, 2016, 07:51:13 AMWindows task manager (Ctrl+Shift +Esc keys) , process tab and set priority there (it only last till you reboot or restart the app).Oh, I found this guide on Arma3 , so it must be working for others ok (look at system optimization).http://wiki.day0.com.au/ArmA_3_Performance_Tweaks_and_Settings_Guide#My_Optimized_SettingsAlso while might not apply to you, with any stability issue i recommend disabling "show processes icon in list" , if its enabled (setting is under view menu ).
QuoteOn your settings, there really is no need to raise a process that in in foreground (full screen game) , the main thing is controlling all the other back-ground processes so they don't take away CPU% .
Quote from: edkiefer on January 02, 2016, 08:14:07 AMOk, that is odd results , not sure whats going on here, we never got this kind of report before.On your settings, there really is no need to raise a process that in in foreground (full screen game) , the main thing is controlling all the other back-ground processes so they don't take away CPU% .That is done automatically within Probalance, but you can micro manage a few if you want.
Quote from: edkiefer on January 02, 2016, 09:05:20 PMHave you tired same thing with other processes .Does PL save priority on other processes set to always ?Check that your game is still in list , Options>Configure default cpu priority
Quote from: Jeremy Collake on January 04, 2016, 10:26:48 AMI am setting up a test bed ASAP to debug what in the world is going on here, so should have some information at that time. Until then, we can only speculate.I can say that any crash within Process Lasso's code base should be handled gracefully, so I suspect that the crash is occurring in another module mapped into Process Lasso's address space. Whether it's part of the game (maybe API hooks for protection) or what, is again only speculation until I go and look.