hello! where is the keithy utils config located? im having an ID conflict and i cant seem to find it for the life of me :/
There isn't a config for KeithyUtils itself, instead you just use the Metallurgy configs. There's a few of them, they'll be located in their own folder within the config folder.
XanderGryphon: Aluminum is used to make Alumite. If you have Steel in one form or another you won't need it to mine nether ores, but without... well. You'll need one or the other.
Ah, I forgot about it being used to make Alumite. We don't actually have a use for Alumite due to using Metallurgy, so I'd forgotten it even existed. Apologies for the mistake.
I've been having a problem with Metallurgy 3 with quite a few other mods installed. Basically, every item, block, & otherwise from Metallurgy itself has name right after it. For example, Damascus Steel Ingot is Damascus Steel Ingot name, as well at the ore, the metal block, and the dust.
Do any of you have an idea on how to fix this? It's not a game-breaking issue, but it's fairly irritating. Here is a list of the mods I'm using:
Thaumcraft 4 (4.10g)
Not Enough Items (1.6.1.9)
WAILA (1.5.1a)
Tinkers' Construct (1.5.3)
Metallurgy 3 (3.3.2) (all of the default child mods included with the normal Metallurgy download)
Thaumic Tinkerer (2.3)
ExtraTIC (adds Metallurgy metals as Tinker tool parts) (0.7.6)
NEI Plugins (1.1.0.6)
Code Chicken Core (0.9.0.9)
COFH Core (2.0.0.2)
Ender Storage (1.4.3.6)
KeithyUtils (1.2.1.6)
Thermal Expansion (3.0.0.2)
Tinkers' Mechworks (0.1.4.2)
This is a known issue that was fixed in a patch, but that patch was subsequently pulled as it caused other issues. That patch was said to be the final patch for M3, so it's possible there won't be a fix for that issue until the mod is updated to Metallurgy 4.
More then half of the mod is useless without aluminum, why would you disable it? Also, you can't disable any ore in TCon I don't think.
You don't need Aluminum at all, actually. And the configs have options to disable all TCon ores from spawning including bushes, so it is - or at least, should be - possible to disable any or all of them if one so chooses. I myself have successfully disabled everything except Aluminum (which I would have disabled had I known at the time that it wasn't actually necessary).
Not that it really matters, but for the sake of conversation, I will most likely always think of Minecraft as being in a medieval timeframe. Most tech mods feel extremely out of place to me in Minecraft, and despite the existence of things that weren't present until far beyond the medieval ages in our world, I see that as no reason why it can't be possible in the Minecraft world.
There has been some ideas I have been toying with and would like your opinion on them.
1. There is an obvious imbalance in research aspects gained. I'm considering two solutions: scanning only giving primals like the decon table or changing some of the low tier aspect combos (for example potentia being aer+ignem instead of ordo+ignem). Thoughts?
I like the idea of getting primal aspect points from scanning things, if you receive the component primals that would make up whatever aspects are contained within.
For example, you could have it set up so you can scan seeds and see that it has Granum (or Obscurus if you haven't yet discovered Granum), but you receive Terra and Aqua from it (Terra+Aqua = Victus + Terra = Granum). This would help promote combining, as well as subtly giving a hint regarding which aspects combine to form another.
As for changing the combinations, as long as they still make sense, I have no issues with that.
2. "Wild" mana beans only giving random primal aspects, but adding a way to crossbreed them into compound versions that only bear a single type of bean most of the time.
I'm all for this. I don't personally use Mana Beans at all currently, but I like the idea of being able to crossbreed them and specify which type of bean you'll be growing.
That sounds almost more painful than the number coding. What's the motivation behind this change from mojang? How are names better than the numbers? There's bound to be same names in different mods ultimately?
It's actually a good change, it's just difficult to make the transition (or so it seems). IDs will still be used numerically, but they'll be handled internally now, and items will be registered like "harvestcraft:apple" or whatever. This means there won't be overlaps anymore (unless someone names their mod the same as an existing mod, or something similar to that effect).
This will allow for things like "minecraft:apple" and "harvestcraft:apple" to exist without causing crashing conflicts. As I'm not a coder, I can't comment on how things will be handled in cases of overwriting vanilla (or other mod) items/blocks, but overall it should turn out to be a change for the better, though there's absolutely no denying the amount of frustration and aggravation it's caused mod developers.
That said, allow me to say Thank you, Pam, for all you've done and continue to do. I look forward to the future of HarvestCraft (especially with Thaumcraft compatibility, if you can ever manage to get that working properly).
I decided to give Metallurgy, a shot. As I am using Tinker's Construct; I added Extra TiC to the mix. When I ran the Minecraft, the game promptly crashed. I've attached the generated crash report.
I am currently running MC 1.6.4 and I'm using the latest version of Metallurgy 3, Kelly's Utilities and Extra TiC 0.7.6 TC is for 1.6.4
Any idea? I'll post a copy of this over at the Extra TiC forum; as it's likely to be a problem with their addon.
---- Minecraft Crash Report ----
// I just don't know what went wrong
Time: 2/23/14 7:25 PM
Description: Initializing game
java.lang.IllegalArgumentException: Slot 4090 is already occupied by glassmaker.extratic.metals.MoltenMetalBlock@3f6e3adf when adding assets.pamharvestcraft.BlockPamFruit@5ddb2701
at net.minecraft.block.Block.<init>(Block.java:349)
at assets.pamharvestcraft.BlockPamFruit.<init>(BlockPamFruit.java:34)
at assets.pamharvestcraft.PamHarvestCraft.preInit(PamHarvestCraft.java:1055)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:545)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:201)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:112)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:522)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at net.minecraft.block.Block.<init>(Block.java:349)
at assets.pamharvestcraft.BlockPamFruit.<init>(BlockPamFruit.java:34)
at assets.pamharvestcraft.PamHarvestCraft.preInit(PamHarvestCraft.java:1055)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:545)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:201)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:112)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:522)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473)
-- Initialization --
Details:
Stacktrace:
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
-- System Details --
Details:
Minecraft Version: 1.6.4
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: Java HotSpotâ„¢ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 315032464 bytes (300 MB) / 481034240 bytes (458 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: FML and Forge are installed
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v8.11 FML v6.4.49.965 Minecraft Forge 9.11.1.965 23 mods loaded, 23 mods active
mcp{8.09} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized
FML{6.4.49.965} [Forge Mod Loader] (minecraftforge-9.11.1.965.jar) Unloaded->Constructed->Pre-initialized
Forge{9.11.1.965} [Minecraft Forge] (minecraftforge-9.11.1.965.jar) Unloaded->Constructed->Pre-initialized
TConstruct-Preloader{0.0.1} [Tinkers Corestruct] (minecraft.jar) Unloaded->Constructed->Pre-initialized
Autoutils{1.0.1} [Autoutils] (autoutils-1.6.4-1.0.1.jar) Unloaded->Constructed->Pre-initialized
BiblioCraft{1.5.5} [BiblioCraft] (BiblioCraft[v1.5.5].zip) Unloaded->Constructed->Pre-initialized
CarpentersBlocks{v2.0.2} [Carpenter's Blocks] (Carpenter's Blocks v2.0.2 - MC 1.6+.zip) Unloaded->Constructed->Pre-initialized
Chisel{1.5.0} [Chisel] (chisel-1.6.4-1.5.0fix.jar) Unloaded->Constructed->Pre-initialized
craftguide{1.5.2} [CraftGuide] (CraftGuide-1.6.7.4.zip) Unloaded->Constructed->Pre-initialized
CustomSpawner{3.0.0} [DrZhark's CustomSpawner] (CustomMobSpawner 3.0.0.zip) Unloaded->Constructed->Pre-initialized
MoCreatures{6.1.0} [DrZhark's Mo'Creatures Mod] (DrZharks MoCreatures Mod v6.1.0.zip) Unloaded->Constructed->Pre-initialized
ExtrabiomesXL{3.15.1} [ExtrabiomesXL] (ExtrabiomesXL-universal-1.6.4-3.15.1.jar) Unloaded->Constructed->Pre-initialized
KeithyUtils{1.2} [Keithy Utils] (KeithyUtils-1.6.4-1.2.16.jar) Unloaded->Constructed->Pre-initialized
Metallurgy3Core{3.2.3} [Metallurgy 3 Core] (Metallurgy-1.6.4-3.3.2.jar) Unloaded->Constructed->Pre-initialized
Metallurgy3Base{3.2.3} [Metallurgy 3 Base] (Metallurgy-1.6.4-3.3.2.jar) Unloaded->Constructed->Pre-initialized
Natura{2.1.14} [Natura] (Natura_mc1.6.X_2.1.14.jar) Unloaded->Constructed->Pre-initialized
TConstruct{1.6.X_1.5.2.1} [Tinkers' Construct] (TConstruct_mc1.6.4_1.5.2.6.jar) Unloaded->Constructed->Pre-initialized
ExtraTiC{0.7.6} [ExtraTiC] (ExtraTiC-1.6.4-0.7.6.jar) Unloaded->Constructed->Pre-initialized
Metallurgy3Machines{3.2.3} [Metallurgy 3 Machines] (Metallurgy-1.6.4-3.3.2.jar) Unloaded->Constructed->Pre-initialized
Metallurgy3Vanilla{3.2.3} [Metallurgy 3 Vanilla] (Metallurgy-1.6.4-3.3.2.jar) Unloaded->Constructed->Pre-initialized
pamharvestcraft{1.0} [Pam's HarvestCraft Base] (Pam's HarvestCraft 1.6.4 v1.1.4.zip) Unloaded->Constructed->Errored
UndergroundBiomes{0.4.2a} [Underground Biomes] (UndergroundBiomesConstructs_1.6.x-0.3b.zip) Unloaded->Constructed->Pre-initialized
mod_ZanMinimap{0.9.4} [Zan's Minimap] (ZansMinimap1.6.4.zip) Unloaded->Constructed->Pre-initialized
TConstruct Environment: Sane and ready for action. Bugs may be reported.
Launched Version: 1.6.4-Forge9.11.1.965
LWJGL: 2.9.0
OpenGL: AMD Radeon HD 7310 Graphics GL version 4.2.12422 Compatibility Profile Context 13.152.1.1000, ATI Technologies Inc.
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Pack: Soartex_Fanver.zip
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
java.lang.IllegalArgumentException: Slot 4090 is already occupied by glassmaker.extratic.metals.MoltenMetalBlock@3f6e3adf when adding assets.pamharvestcraft.BlockPamFruit@5ddb2701
It's actually from ExtraTiC, but this is an ID conflict issue. Simply change the IDs in either ExtraTiC or Harvestcraft so they aren't conflicting anymore.
Other bugs were fixed, aside from just the name. Some ores which were not generating properly were fixed. The enchanter and orbs were also finished.
They also recently released a beta of Metallurgy Bees which requires the pulled version of M3 or later. So I'm sure they wouldn't let all that work go to waste.
If you ask me, they'll probably release new versions after their 1.6.4 modpack is done and officially released.
Again, my point was simply that I cannot speak for the team and can't say "Yes, there will be an update!" when it's just as possible that there won't be one.
Oh I'm sure there will be. They're just busy with M4 right now. And the only problem with the previous build of M3 that I'm aware of was that it'd hose your block and item IDs when you'd update. And the ID conflict errors were pretty cryptic. Not graceful at all.
Yes, I'm aware of the work being done on M4. And yes, the IDs were the main issue, as I mentioned in my post earlier.
My point is just that I wouldn't expect an update for this bug and that while I'm 'close' with the team and get a lot of information from them, I can't outright speak for them when it comes to updates and things.
It's a very minor bug that doesn't hinder the functionality of the mod at all, so it's entirely possible that it won't be fixed until the first release of M4.
Ok, I put the two files back in the mod folder and applied the above fix. It works beautifully. I took a better look at the other set of armors and tools. I see what you're talking about.
I've one other question, though. When I look at the names of the ingots or any other Metallurgy metals; it would say Steel ingot name. Name is added to the end of all Metallurgy metals. Why? I'm also using TC 1.6.4.
I can't offer an explanation for why items have "name" at the end of their names (mainly because I forget the reason), but it is a bug with Metallurgy. It was fixed in a recent build, but that was pulled because it had some issues relating to IDs.
It shouldn't affect the functionality or anything of the mod though, so there's no real downside to it other than it being slightly annoying.
I am new to this particular mod. I am currently running MC 1.6.4 with an assortment of 23 mods. This includes Tinker's Construct and the current version of Metallurgy 3.
I am using Soartex Fanver's resource pack. Before I installed Metallurgy 3, the graphics for my diamond armor and sword looked nice and clean. After I installed Metallurgy, I got a rude shock. The diamond armor and sword looked totally different and terrible. The same holds true for the gold armor and tools. What happened?
The other items appeared normal. It was just the diamond and gold related item. Gold ore block and diamond ore block looked normal.
UPDATE: 1. I downloaded a copy of Faithful 32x32 and I got the same thing with the diamond and gold stuff. Same problem persisted with Default.
2. Okay, I removed M3 from the mod folder and that core file. I turned on MC and everything is back to normal, for all 3 texture packs.
What happened? I've heard a great deal about it and I wanted to give it a shot.
By default, Metallurgy replaces the textures for vanilla tools and armor with textures that are more in line with the rest of Metallurgy's great armor and tool textures.
It's a simple config option located in MetallurgyVanilla.cfg:
I've been having an issue with crashing because of (what I think is) holding pipes in my inventory. I did some testing with it, and I keep getting the same error. I made sure it wasn't placed pipes, but pipes held in my hotbar seem to cause the issue. After it crashes I can't access the world anymore, any help would be appreciated.
EDIT: for clarification, this is using 4.1.0d on the DW20 modpack
I had this exact same thing happen to me last night randomly (or so it seemed) using 4.1.0e. I managed to "fix" it by downgrading to 4.1.0b - but updating back to 4.1.0e caused it to start crashing again. A redownload and reinstall of 4.1.0e did let me back into the game, but it seems that too was just a "band-aid" fix, as today it's started to crash again upon loading.
0
There isn't a config for KeithyUtils itself, instead you just use the Metallurgy configs. There's a few of them, they'll be located in their own folder within the config folder.
0
Ah, I forgot about it being used to make Alumite. We don't actually have a use for Alumite due to using Metallurgy, so I'd forgotten it even existed. Apologies for the mistake.
0
This is a known issue that was fixed in a patch, but that patch was subsequently pulled as it caused other issues. That patch was said to be the final patch for M3, so it's possible there won't be a fix for that issue until the mod is updated to Metallurgy 4.
0
If the configs are set to not generate Aluminum and it's spawning anyway, that's almost certainly a bug.
You don't need Aluminum at all, actually. And the configs have options to disable all TCon ores from spawning including bushes, so it is - or at least, should be - possible to disable any or all of them if one so chooses. I myself have successfully disabled everything except Aluminum (which I would have disabled had I known at the time that it wasn't actually necessary).
0
0
Should be pretty obvious, but no, it won't. Not yet, anyway.
0
I like the idea of getting primal aspect points from scanning things, if you receive the component primals that would make up whatever aspects are contained within.
For example, you could have it set up so you can scan seeds and see that it has Granum (or Obscurus if you haven't yet discovered Granum), but you receive Terra and Aqua from it (Terra+Aqua = Victus + Terra = Granum). This would help promote combining, as well as subtly giving a hint regarding which aspects combine to form another.
As for changing the combinations, as long as they still make sense, I have no issues with that.
I'm all for this. I don't personally use Mana Beans at all currently, but I like the idea of being able to crossbreed them and specify which type of bean you'll be growing.
1
It's actually a good change, it's just difficult to make the transition (or so it seems). IDs will still be used numerically, but they'll be handled internally now, and items will be registered like "harvestcraft:apple" or whatever. This means there won't be overlaps anymore (unless someone names their mod the same as an existing mod, or something similar to that effect).
This will allow for things like "minecraft:apple" and "harvestcraft:apple" to exist without causing crashing conflicts. As I'm not a coder, I can't comment on how things will be handled in cases of overwriting vanilla (or other mod) items/blocks, but overall it should turn out to be a change for the better, though there's absolutely no denying the amount of frustration and aggravation it's caused mod developers.
That said, allow me to say Thank you, Pam, for all you've done and continue to do. I look forward to the future of HarvestCraft (especially with Thaumcraft compatibility, if you can ever manage to get that working properly).
0
It's actually from ExtraTiC, but this is an ID conflict issue. Simply change the IDs in either ExtraTiC or Harvestcraft so they aren't conflicting anymore.
0
Again, my point was simply that I cannot speak for the team and can't say "Yes, there will be an update!" when it's just as possible that there won't be one.
0
Yes, I'm aware of the work being done on M4. And yes, the IDs were the main issue, as I mentioned in my post earlier.
My point is just that I wouldn't expect an update for this bug and that while I'm 'close' with the team and get a lot of information from them, I can't outright speak for them when it comes to updates and things.
It's a very minor bug that doesn't hinder the functionality of the mod at all, so it's entirely possible that it won't be fixed until the first release of M4.
0
Like I mentioned above, it was fixed, but there were other issues with that build so it was pulled.
I can't say for certain whether or not another build will be made, especially considering how minor an issue this is.
0
I can't offer an explanation for why items have "name" at the end of their names (mainly because I forget the reason), but it is a bug with Metallurgy. It was fixed in a recent build, but that was pulled because it had some issues relating to IDs.
It shouldn't affect the functionality or anything of the mod though, so there's no real downside to it other than it being slightly annoying.
0
By default, Metallurgy replaces the textures for vanilla tools and armor with textures that are more in line with the rest of Metallurgy's great armor and tool textures.
It's a simple config option located in MetallurgyVanilla.cfg:
Change that to false and the textures will go back to standard Minecraft textures.
0
I had this exact same thing happen to me last night randomly (or so it seemed) using 4.1.0e. I managed to "fix" it by downgrading to 4.1.0b - but updating back to 4.1.0e caused it to start crashing again. A redownload and reinstall of 4.1.0e did let me back into the game, but it seems that too was just a "band-aid" fix, as today it's started to crash again upon loading.