[1.14.4][28.1.70]java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

[raziel23x 0]

I have updated my modpack to the latest forge 28.1.70 and cannot get the modpack to even get past the forge loader

Crash Log- https://paste.dimdev.org/zomezuhuyo.mccrash

Debug Log https://paste.dimdev.org/juxeneliwi.sql (this was added because some idiot said it was needed even though it was created and modified almost a week ago when i had my last crash when i added a new mod that i removed and fixed the issue i had last time)

Edited October 28 by raziel23x

[DaemonUmbra 358]

Please read the Logs section of my signature below and provide the appropriate log in the appropriate manner.

[raziel23x 0]

29 minutes ago, DaemonUmbra said:

Please read the Logs section of my signature below and provide the appropriate log in the appropriate manner.

the crash report is the link and already using this system

[DaemonUmbra 358]

That's not the file I want. Please read my signature.

[raziel23x 0]

there is no other files other then the latest.log and it has the same information as this is the twitch launcher

[DaemonUmbra 358]

If you're using Twitch please follow the instructions I have specifically for Twitch

[raziel23x 0]

like i said no further information is there even in the the log you keep referring to that file i uploaded is a few days old so this log you want is invalid  i think i know what information is relevant to post so telling me to look at your signature every time is pointless when i know what a time stamp is and posted all timed stamped items of the date and time the issue happened

[diesieben07 6693]

debug.log contains more information than the other log files.

Please provide the files you are asked to provide using the given instructions (see Daemon's signature) and stop being a prick.

[raziel23x 0]

you both stupid or what the debug file was modified is over a week old and has nothing to do with the issue at hand last night crash

[raziel23x 0]

the debug file has stopped working like 5 forge versions ago and the last known version of forge where the debug forge file was working is not compatible with most mods anymore so if you want one i will have to downgrade about 40 different mods and then the issue will not be present anymore so again that file will again be not valid and this is a known issue with the debug file and being worked on if you are following the issue tracker on github,,,,,,

[diesieben07 6693]

1 hour ago, raziel23x said:

this is a known issue with the debug file and being worked on if you are following the issue tracker on github

Link?

[raziel23x 0]

I fixed the issue by changing forge versions and it has both fixed the crash and debug working yet debug just does this

 

C:\fakepath(49,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(55,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them 

 

over and over again with just

C:\fakepath(49,8-56):

C:\fakepath(55,8-26): 

the (xx,xx) has differnt numbers

 

[diesieben07 6693]

Some mod you have installed (most likely related to shaders) is producing OpenGL errors.

[DaemonUmbra 358]

5 hours ago, raziel23x said:

the debug file has stopped working like 5 forge versions ago

Is this about how long ago you installed Twitch?

This is a known TWITCH issue that they ignore the Forge logging configuration that creates the debug.log and launching Forge 28.1.70 myself I see a debug.log being generated.

[DavidM 105]

Always posts logs. Without logs other cannot help you, as others won’t know what the problem is caused by.

[raziel23x 0]

https://github.com/MinecraftForge/MinecraftForge/issues/5907

 

debug is generated but no matter what its always just https://paste.dimdev.org/zaraholobo.sql never any info just the same line over and over again with crashed ones as well as fully functional games with no crashes the debug always reads these lines even if i delete the debug log and rerun forge

 

you can even compare this debug log to the original one that i sent to you after telling you the debug log was useless and not needed and you can see that even this newly generated debug log i just posted as a example which was deleted and freshly created today is a exact copy of the debug log from oct 27th

Edited November 6 by raziel23x

[diesieben07 6693]

On 10/28/2019 at 4:09 PM, diesieben07 said:

Some mod you have installed (most likely related to shaders) is producing OpenGL errors.