tModLoader v1.4.3 cannot be launched
After RE-LOGIC logo is shown, the game freeze with black screen.
I've tried things but it's not fixed:
- Wait over 10 minutes
- Reboot tModLoader
- Reboot Steam
- Reboot PC
- Verify game files
- Reinstall tModLoader (by switching version)
- Repair Microsoft Visual C++ 2015-2022 Redistributable (x64)
- Repair Microsoft Visual C++ 2015-2022 Redistributable (x86)
23 Replies
Also I tried:
- Remove
enabled.json
- Turns "ShowNewUpdatedModsInfo"(config.json) into "false"Tag: alllogs (Owner: jopojelly#0000)
If the information in the pinned thread does not solve your issue, please post all log files by dragging and dropping them into this chat. In Steam right click on tModLoader in the library, then hover over Manage and click on Browse local files. In the folder that appears find tModLoader-Logs and open that folder. Inside that folder are the logs files. Select them all except the Old folder and drag them into this chat. If you need a visual guide to this process watch this: https://github.com/tModLoader/tModLoader/assets/4522492/3f4efa43-753f-4733-b630-ba85e711340c
Oh, sorry. There are all logs
Is there a reason you want to play 1.4.3? It looks like the game is trying to load your mods that you've subscribed to on the Steam workshop, but the mods don't have a 1.4.3 version available.
That's because I wanna play 1.4.3.
It's usually that "No .tMods found for this version in Workshop Folder C:\Program Files (x86)\Steam\steamapps\common\tModLoader....\workshop\content\1281930... Defaulting to show newest" is shown in
client.log; it shows regardless whether the game can't launch or not.This is the first mod in the list
It's only for 1.4.4
Try unsubing from it
That means, should I unsubscribe all mods supporting only v1.4.4?
Maybe
You could also try launching the game in a couple different ways
Up until now, I subscribed mods supporting only v1.4.4 and I could launch v1.4.3.
I don't know why but it's today that tML v1.4.3 cannot be launched.
different ways?
Run the
start-tModLoader.bat file instead of starting through Steam. Probably won't make a difference but you could try it.
Another option is this:Tag: powershelllaunch
A last resort is to launch the game manually in PowerShell.
1. Go to the tModLoader install directory. Hold shift and right click in the folder. Click "Open PowerShell window here".
2. Type
dotnet tModLoader.dll and press enter.
If the game did not launch, you likely have an issue with .NET; You can try installing the .NET 8 SDK from here https://dotnet.microsoft.com/en-us/download/dotnet/8.0. Select Windows x64 and run the installer. After you have installed the .NET 8 SDK, you will need to delete your dotnet folder in the tModLoader install directory.Thank you! I will try them after lunch.
The last option I have is to use the
-steamworkshopfolder <path> launch option to change where the game looks for workshop mods.I've succeed to lauch tML by turning Steam offline and remove directory containing files of workshop mods!
I'll check what mod makes tML unlaunchable.
Finally!!!!!!
I found these mods making tML v1.4.3 unlaunchable
https://steamcommunity.com/sharedfiles/filedetails/?id=3375903288
https://steamcommunity.com/sharedfiles/filedetails/?id=3476640589
However why...?
if you are the person in the workshop page with the same issue, what enabled mods did you have at the time of this crash?
@Tyfyter can you also read the client logs whenever convenient? i suspect this might be a mod conflict
Yeah, but if it's really unlaunchable it couldn't be a mod conflict because it'd be happening before TO's code runs
oh right
That's probably not mod conflict because tML cannot be launched even when I remove
enabled.json.
In my opinion:
The causes itself is on the side of tML v1.4.3, not Terraria Origins.
(However, the issue occurs only Terraria Origins and that music mod currently and just in case, I reported in the steam workshop page of Terraria Origins.)
I try to call methods I suspect to occur the issue, but I cannot find what method occurs for now. (Above all it's so difficult to run only one method in tModLoader outside...)
-# To be honest, if I find cause of the issue, I can not expect tModLoader team fix the issue because they always say me "why do you play v1.4.3? play v1.4.4."...it’s fair. we’d still like to try and see if it’s still our problem