Not tried without RInput.. Will test that..
About the hunkmegs used and the one registered maybe only a value latched at the one registered, and waiting for a vid_restart to get rid of the lock, noh?
You don't really need rinput , its usefull for people running low resolutions with high DPI.
I just though you were using it because of your crash log
@Hunkmegs , when you open ET.exe , it loads the first cfg ( etconfig in etmain I believe ) and the reserve ram according to com_hunkmegs
Since it can't be changed after, it won't change anything if you change it in another mod.
You really need to change it in the first loaded CFG to be effective
else you will get
latched 512 ... which mean com_hunkmegs got set to 512 but won't allocate 512 until reboot , and since the 128 will get loaded first ( again ) its an infinite loop
if /com_hunkmegs is already returning the desired value (512 ) then you are good to go.
And oh missed that part about the shortcut already set hehe
Else Internet says it could be faulty ram but I don't believe its the case here
+ people often says its faulty material because its the easiest answer