search

tModLoader / tModLoader

A mod to make and play Terraria mods. Supports Terraria 1.4 (and earlier) installations
https://www.tmodloader.net/
MIT License
4.17k stars 1.87k forks source link

[1.4.4/Dev Build] Running the latest build doesn't work: immediately shows error #3164

Closed Setnour6 closed 1 year ago

Setnour6 commented 1 year ago

Note that this issue is similar to #3159

Version

Other (Latest 1.4.4-dev)

OS

Windows

Platform

Steam

This bug affects

Gameplay as a Player (I had "Mod capability as a Modder" because I was going to talk about something else)

Description

When launching tModLoader's 1.4.4 build, the main engine immediately crashes. image I followed the setup steps for contributing to tModLoader, pulled the latest changes, tried to open tModLoader, and it didn't work. I then regenerated the source, tried to open tModLoader again, and the problem is still there. image The last thing I did was delete everything from the tModLoaderDev folder and build the project, which creates the files there but even that didn't work. It still shows some files being dated 2022 November.

This thrown exception could be the reason why this is occuring: image

Log File

client.log Most recent client.log

Steps to reproduce

  1. Follow the dev setup steps and pull the latest commits from the 1.4.4 branch
  2. build the project (For me, it said "Build Terraria")
  3. Launch "Terraria" without debugging image
  4. The error should appear soon.

Expected Behavior

tModLoader runs normally

Actual Behavior

tModLoader doesn't run at all, just an error appears. No splash screen, no game window, nothing.

Reproduction frequency

100% of the time

Additional Information

How do I really update the tModLoader-Dev folder in steamapps --> common? I forgot how to do it, and I want to get the absolute latest version of tModLoaderDev branch build.

direwolf420 commented 1 year ago

Are both Terraria and tModLoader-Dev on the same drive?

Setnour6 commented 1 year ago

Are both Terraria and tModLoader-Dev on the same drive?

Yes, both are on the C: Drive. I recall that the dev build worked back in 2022 when I tested it.

Solxanich commented 1 year ago

Some thoughts: Typically Main.Asset errors come from issues with Terraria content files. Things like filename being upper or lower case.

Try Verifying vanilla files? Maybe also try running Terraria itself.

Setnour6 commented 1 year ago

Some thoughts: Typically Main.Asset errors come from issues with Terraria content files. Things like filename being upper or lower case.

Try Verifying vanilla files? Maybe also try running Terraria itself.

I find it strange that the vanilla game could even cause errors like that. I verified the integrity of the content files, started Terraria itself (it starts up well), and then the next thing I did was select the exe (Select Terraria), then clicked setup. I then ran Terraria with debugging via Visual Studio, but this time no exception message appeared, but the game still crashes right away with about the same error. image

Is there a step-by-step way that I should do that will allow me to launch the dev build with no early issues?

Solxanich commented 1 year ago

With respect to vanilla, we reuse their audio, graphic assets from their install so that we don't duplicate files. And copyright reasons. An unfortunate difference between Terraria and tmod is that tmod is case sensitive. If a file had case swapped during the 9+ updates for Terraria and steam didn't 'update' the file. Could be whats going on here.

Everything checks out with what you did, which leaves this as strange to me. A final idea is to delete the content folder in tmodloader and content folder in Terraria folder, per above. And thats all I got at the moment, unfortunately

Setnour6 commented 1 year ago

With respect to vanilla, we reuse their audio, graphic assets from their install so that we don't duplicate files. And copyright reasons. An unfortunate difference between Terraria and tmod is that tmod is case sensitive. If a file had case swapped during the 9+ updates for Terraria and steam didn't 'update' the file. Could be whats going on here.

Everything checks out with what you did, which leaves this as strange to me. A final idea is to delete the content folder in tmodloader and content folder in Terraria folder, per above. And thats all I got at the moment, unfortunately

That is strange indeed. Is it possible for tModLoader to not be case-sensitive? I followed the final idea and the error unfortunately still appears. This was tested on a branch I was working on for secret seed additions (#3165), and Main itself was not changed at all. image I'm hoping that this can be looked at more and looked into further to resolve the issue so playtesting the dev build can be possible. Also, did the error also appear for you?

Chicken-Bones commented 1 year ago

Please DM me on Discord and I will assist you

Setnour6 commented 1 year ago

Please DM me on Discord and I will assist you

I still don't use discord, but I can message you via email (and try to add you as a contact there)

Chicken-Bones commented 1 year ago

Should be a duplicate of #3159 and fixed by the same d1249475b7adfb2f8d259fe35cafd8bf362de60b