Hello Everyone,
Oh, how I do wish I could say I love this pack and all that stuff, but I am one of the lucky people for whom it did not work, I am hoping to remedy that situation. But thank you in advance for your hard work all the same, even if I don't get to see it.
What follows is the trouble, so sorry to be the bearer of bad news.
Before I begin, I mean no offense, but please kindly bear in mind that I am a seasoned user and developer within modded Minecraft servers and clients with about 20 years on me and a daytime computer professional before you suggest the more "beginner" answers
(allocate more ram, did you configure x correctly, etc.). Also, I am quite aware the OP might reject this entirely because SB3 is ever so slightly modified. If that is the case, I hope you will at least consider leaving this as a stepping-stone of sorts for others that might run into this problem in the future, or kindly move me off to another thread if that is not possible. But it does still pertain to this particular pack directly so there's that.
The 64x just doesn't work at all for me, not because of any usual reason, mind you. I would like to give more detail other than 'it just "crashes"'. But it does
just that, it does not give any warnings/errors (or helpful INFO), nothing in crash-reports, nothing in latest.log or previous-logs.gz of any kind. There is no system report or error either.
I actually wrote a script to catch nontrivial errors to catch hard-to-see problems, but that attempt was a NG as well. The game will load normally to the title screen (with the pack already loaded into memory). However, once a single player world tries to load *or* the pack attempts to load into memory while the world is already running, the java process faults on the system end, which tells me it is probably an error with a resource being incompatible somewhere and causing an unexpected exception. As far as I can tell, the memory used by java up to the point of the crash never gets past 50% of what is available to it during
the troubleshooting of the run.
This is very strange indeed, since I have been using my completed soartex pack that I patched (called st-patchmix for future reference) to include all of the mods I am using and had no problems whatsoever, so that clearly tells me that memory is not the issue. Video performance has never been a problem either. The st-patchmix is also 64x and includes some custom models and sounds. As far as total data size, it is slightly larger but not by much (about 5MiB give or take a KiB).
Other possibility was the NVIDIA cache and/or system graphics settings. So, I made sure I cleared those and defaulted any settings that might have been changed for the duration of these tests. I don't think allocating more than 16GiB for a 64x pack should be needed here, since I never have to go beyond 8GB for st-patchmix. And yes, I did try 16GiB anyway, and of course, no luck.
I'll have to test it on a 'stock' SB3 and see if it works on that. The version of create that I am using is the newest, which of course required me to update flywheel and create crafts & additions as well.
My next step after that would have to be the divide and conquer method: cut the pack in half, test that, cut it in half again and again until I find the offender --but that's going to be a lot of time so I'll get back to this thread if I do find out the cause. I summarized the versions and relevant settings below, if you care to know them.
Until then if anyone has any ideas, I'd like to hear them! Because if divide and conquer doesn't work I'll be out of ideas
Sincerely,
osirisgothra
Summarized:
The versions that were modified:
Create version 0.5.0-i
Flywheel 0.6.8-a.
Versions of video-enhancement mods that were tested with/without:
Rubidium 0.5.4
Oculus 1.4.3a
(Optifine was a NG on SB3)
Additional mod used (not native to SB3) tested with/without:
Create: Steam n Rails 1.1.1
BetterF3 3.0.0
Memory allocation:
Min: 8GiB, Max 16GiB
Other steps taken:
System settings (video) defaulted
NVIDIA (all) Cache Clear
Java Allocation Memory Trace (never exceeds 50% on the 8GiB run)