Dynamic Surroundings

Dynamic Surroundings

51M Downloads

Crash on 1.12.2 with Java 8

HenrikoMagnifico opened this issue ยท 20 comments

commented

Mod Version:

DynamicSurroundings-1.12.2-3.6.2.1

Forge Version:

Forge-1.12.2-14.23.5.2847

Link to client log:

crash-2021-03-25_17.37.56-client.txt

Description:

The mod crashes while using Java 1.8.0_281, even with no other mods installed.

commented

Did you install MixinBootstrap? That is a dependency the new BETAs currently have.

commented

Did you install MixinBootstrap? That is a dependency the new BETAs currently have.

I did not! I'll try that straight away.

commented

Did you install MixinBootstrap? That is a dependency the new BETAs currently have.

That completely solved the problem. Thank you!

commented

Update: Having the issue again however this time I am not able to fix it with MixinBootstrap separately. With Mixin installed it refuses to even launch the game whatsoever, an instant crash with no crash log. This is the latest.log, which is all I could get from it. Without it it leaves me with this crash log now.

commented

Interesting. The DS version that is installed is 3.6.0.1, not 3.6.2.1. Was this intended?

commented

Interesting. The DS version that is installed is 3.6.0.1, not 3.6.2.1. Was this intended?

Thanks for the speedy reply! I do not remember why I had the older version installed, I updated it to the latest version and unfortunately it's still crashing. It almost makes it to the title screen now before showing me a crash screen with a link to this crash log here.

commented

I will need the latest.log to understand the context. This still could be a Mixin related issue.

commented
[14:32:48] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.7.11 Source=file:/C:/Users/henri/AppData/Roaming/.henrikoLauncher/common/modstore/me/jellysquid/mods/phosphor/mod/phosphor-lighting/1.12.2-0.2.6/phosphor-lighting-1.12.2-0.2.6.jar Service=LaunchWrapper Env=CLIENT

Update Phosphor to 0.2.7. That version has 0.8 support for Mixin.

Thanks! I just tried it. Unfortunately the same MalisisCore missing message appears, this is the log now: latest.log

commented

At this point it looks like the Mixin related issues are cleared up. For whatever reason Forge cannot identify malisiscore so it stops loading mods and apply transformers. This will result in DS throwing an error because it's transformers didn't fire. It is not clear to me why Forge can't identify that library.

Will the pack load if MalsisDoors is disabled, but leaving malisiscore installed? Core should load like any other mod.

commented

At this point it looks like the Mixin related issues are cleared up. For whatever reason Forge cannot identify malisiscore so it stops loading mods and apply transformers. This will result in DS throwing an error because it's transformers didn't fire. It is not clear to me why Forge can't identify that library.

Will the pack load if MalsisDoors is disabled, but leaving malisiscore installed? Core should load like any other mod.

Disabling MalisisDoors works! So MalisisDoors is the issue, then? I am using the latest version I could find.

commented

I will need the latest.log to understand the context. This still could be a Mixin related issue.

Of course, here is the latest.log.
latest.log

commented

Yep - mixin related:

[12:38:28] [main/WARN]: Mixin config mixins.dsurround.json requires mixin subsystem version 0.8 but 0.7.11 was found. The mixin config will not be applied.

Try adding this mod. It forces the load of the 8.x Mixin as early as possible during the mod load process.

commented

Yep - mixin related:

[12:38:28] [main/WARN]: Mixin config mixins.dsurround.json requires mixin subsystem version 0.8 but 0.7.11 was found. The mixin config will not be applied.

Try adding this mod. It forces the load of the 8.x Mixin as early as possible during the mod load process.

Thanks for the response! Unfortunately that leads to another crash like this: https://paste.dimdev.org/oguhohenis.mccrash

commented

Update: I apologize, it seems I didn't properly enable the Mixin-compat mod in my installation when I wrote the previous message. It's still crashing though, this time with a message related to "Malisiscore missing", which is even stranger since it's definitely not missing from the mod directory. Disabling malisiscore and malisisdoors fixes the issue, it seems, and the game is able to launch properly. However, MalisisCore is necessary for my modpack and I can not remove it without serious issues in other areas. Disabling "Mixin-compat" causes DS to crash, but does not present the MalisisCore missing error. I know this isn't strictly related to DS anymore, but do you know why this error might occur? https://paste.dimdev.org/xabigibasi.md

Here is the latest.log as well, in case you need it: https://paste.dimdev.org/azuyojekim.md

Again, I very much appreciate your help!

commented
[14:32:48] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.7.11 Source=file:/C:/Users/henri/AppData/Roaming/.henrikoLauncher/common/modstore/me/jellysquid/mods/phosphor/mod/phosphor-lighting/1.12.2-0.2.6/phosphor-lighting-1.12.2-0.2.6.jar Service=LaunchWrapper Env=CLIENT

Update Phosphor to 0.2.7. That version has 0.8 support for Mixin.

commented

I am not sure why the issue exists. It is baffling me. It looks like Forge is trying to apply the dependency list of MalisisDoors and is not finding malisiscore. I checked the source trees and it looks like everything is defined correctly. Can you link the latest.log that does not have doors active?

EDIT: Does this pack load without DS installed?

EDIT2: Also try malsiscore version 6.4.0 while having mixinbootstrap and mixin compat installed. I suspect I know what the problem is.

commented

This is the latest.log without MalisisDoors, the game starts fine even with DS enabled:
latest.log

I will try with the 3.4.0 version of MalisisCore. Again, thank you for your time!

commented

I am not sure why the issue exists. It is baffling me. It looks like Forge is trying to apply the dependency list of MalisisDoors and is not finding malisiscore. I checked the source trees and it looks like everything is defined correctly. Can you link the latest.log that does not have doors active?

EDIT: Does this pack load without DS installed?

EDIT2: Also try malsiscore version 6.4.0 while having mixinbootstrap and mixin compat installed. I suspect I know what the problem is.

The pack is starting successfully with 3.4.0 MalisisCore + mixinboot/compat and DS installed! I will try once more with MalisisDoors enabled as well.

commented

I am not sure why the issue exists. It is baffling me. It looks like Forge is trying to apply the dependency list of MalisisDoors and is not finding malisiscore. I checked the source trees and it looks like everything is defined correctly. Can you link the latest.log that does not have doors active?
EDIT: Does this pack load without DS installed?
EDIT2: Also try malsiscore version 6.4.0 while having mixinbootstrap and mixin compat installed. I suspect I know what the problem is.

The pack is starting successfully with 3.4.0 MalisisCore + mixinboot/compat and DS installed! I will try once more with MalisisDoors enabled as well.

Doing the above and enabling MalisisDoors works! Now all is working correctly. Thank you very much for your help! Why does the latest core not work though?

commented

It looks like it calls out a specific forge version in its dependency list, whereas the prior version does not.