Forum
Questions, builds, help and the odd argument. The mods and guides are out front.
I found out recently that the problem to the crashes was the KeeJay rims (v2 - v9) and it sometimes conflicts with other rims that also don't make them work either. If i scroll through the pages of the rim pack enough, my game with freeze and crash without putting out an error log. Can anyone help me fix this?
Maybe a badly installed rimpack or rim
This is most likely a script redefinition problem check whether there are rim-classes defined with the same full name (package.shortClassName) if there is a perfect match you would need to change the classname of one of the rims or remove one of the classes(even the rpk reference).
If you want to change the name keep in mind that the class,java filename needs to be the same as the short class name and this means you would need to change the definition in the rpk and every reference to the given class (although because we are talking about rims it is very unlikely that the class name is directly referenced) a good practise would be to add some kind of prefix to all the classes referenced in a given rpk.
To properly rename a class file without the java source you can use this little experimental program I wrote (I originally wrote it to check whether the data in the MTHD and FLID parts of a class file is actually some lookup pointing to indices in the CONS table sadly it is not (or not directly), but the renaming functionality can nevertheless be used, though it will not rename the class file to adhere to the new fullclass name nor will it update the rpk) LINK
Another problem that can cause this is that you run out of the available 254 slots for rpks(250 in the default game (the default track rpks reference some that are not there but nevertheless they do take away an index )) this can happen dynamically because the loading of rpks is lazy in the base game.
Added 5 minutes later:
Or you simply run out of memory (the game can only handle 3.5Gb of memory if you reach 3Gb the game should be exited because it will crash very soon after)
tbh i dont really understand anything you just said about the .class with the rims, but i did experiment something with the rims. I was adding the rims one by one and when I got to the v8 pack that ALAN made, it made all the rims past that pack in the catalog disappear. The rims would still have text under it, but no model to display. Everything from pack v8 to v9 (so v8, v8a, v8b, v9) have probably caused a conflict with other rims meshes and scripts (mostly affects the v2 pack and the spare track day rims by AutoSaloon). I check how many rpks I have and it something around 175 or 180 so i'm fine right now. I also don't know how to check if I reached the max memory for the game. If you could possible respond back and help, that would be great.
EDIT:
I uninstalled your reshade and all of a sudden it works...... tf is going on lol
To check the memory consumption run the game in windowed mode and just see how much it uses in the task manager.
Reshade of course adds some additional memory usage though I would be surprised to hear it is that significant (also I have more than 2000 rims in SlrrExhaustive with it so it should not directly be reshade or did you exceed this?)
The class thing is just that if you have classes with the same name it can naturally cause conflicts in the game these errors are just like you described random and have strange effects
I am currently running 8gb of ram on my pc and without reshade i'm only using 1.5gb when in the catalog. With your reshade i'm using 3.4gb. While checking the usage i got to the 5th or 6th page of the rims and it hit 3.5gb and crashed. It's definitely the reshade in this case.
Hmm that is concerning.
Are you using the latest one? It's from march 4 please try that version.
You would need the 2 dlls the exe, and the reshadeFX folder from this download (LINK)
(one of the old versions had logging issues this may be the root problem, with the current version I experience largely equivalent memory usage)
yes, i was using the newest version
Strange indeed...
Can you give me the [ReflectionSettings.fx] part of your ReshadeConfig.ini
check your dms.
I was thinking about the ReshadeConfig.ini file in the slrr root
oh sorry. lemme link that one in the dms too.
It was the correct one but nothing is suspicious in it and still not producing adverse effects on my end
I see you disabled every effect and still not helped.
Are you sure you are using the new Slrr_GI.exe aswell? and with the exe and no reshade the thing works like it should?
If so I'm at a loss 🙁
so do you want me to try the patch with no reshade?
yes lets see with only the new exe
Added 27 seconds later:
just rename the d3d9.dll to something else not_d3d9.dll fr example