@Pedro hmm, I downloaded the 2021 Unity and loaded the mod tools without a problem there. Then I saw your reply, so I went ahead and switched to the 1.2 beta branch in steam, redownloaded the game, and then made another Unity project using the 2022 editor. However, when I load the mod tools, I get the same crash as before. I checked and my computer shows the datestamp on the modTools package as being created just a few minutes ago, when I updated the game to the beta in Steam. I guess I'll try to completely delete JNO and start from a completely clean beta installation, see if that works. Are you sure the mod tools included in the beta package are updated to the new version? Also, the new Unity version is 2022.3.7f1, right?
[EDIT] Saw the "mod_dev" branch and thought maybe that was it, but I get the same error with that version of the modtools package as well.
@JanusSpaceIndustries @Suspaceius Actually, those are called "braces" {} (or "curly brackets" sometimes, but they are properly called Braces). Brackets are the other character on that same key (on a standard American English KB, at least), the [ ]. Just dropping a little typography science...
@Pedro Ok, that's probably the problem. I read a post from a few months ago calling out the upgrade to 2022.3.7, thought that was part of the "Spin Me Round" update. What is the exact Unity version I need then?
Thanks for the quick response.
[EDIT] I see in the post above is a 2021 Unity version, I thought it spoke of a 2019 version, so I'll grab the one mentioned above. Thanks.
I saw a comment here about three years back with this, and no one responded. After installing Unity 22.3.7, I import the mod tools and wait a couple of minutes or so, then Unity crashes with a Bug Report window popping up. After that, if I try to open the project again, it loads for about 20 seconds, then crashes and opens the Bug Report again. Any suggestions? I tried this both through the Hub and through a direct installation of the editor, with the same result. The crash appears to happen during the "Compiling Scripts" phase of startup. I found the crash log and .dmp files, but I can't make heads or tails of them.
@Pedro hmm, I downloaded the 2021 Unity and loaded the mod tools without a problem there. Then I saw your reply, so I went ahead and switched to the 1.2 beta branch in steam, redownloaded the game, and then made another Unity project using the 2022 editor. However, when I load the mod tools, I get the same crash as before. I checked and my computer shows the datestamp on the modTools package as being created just a few minutes ago, when I updated the game to the beta in Steam. I guess I'll try to completely delete JNO and start from a completely clean beta installation, see if that works. Are you sure the mod tools included in the beta package are updated to the new version? Also, the new Unity version is 2022.3.7f1, right?
[EDIT] Saw the "mod_dev" branch and thought maybe that was it, but I get the same error with that version of the modtools package as well.
1.2 years ago@JanusSpaceIndustries @Suspaceius Actually, those are called "braces" {} (or "curly brackets" sometimes, but they are properly called Braces). Brackets are the other character on that same key (on a standard American English KB, at least), the [ ]. Just dropping a little typography science...
1.2 years ago@Pedro Ok, that's probably the problem. I read a post from a few months ago calling out the upgrade to 2022.3.7, thought that was part of the "Spin Me Round" update. What is the exact Unity version I need then?
Thanks for the quick response.
[EDIT] I see in the post above is a 2021 Unity version, I thought it spoke of a 2019 version, so I'll grab the one mentioned above. Thanks.
1.2 years agoI saw a comment here about three years back with this, and no one responded. After installing Unity 22.3.7, I import the mod tools and wait a couple of minutes or so, then Unity crashes with a Bug Report window popping up. After that, if I try to open the project again, it loads for about 20 seconds, then crashes and opens the Bug Report again. Any suggestions? I tried this both through the Hub and through a direct installation of the editor, with the same result. The crash appears to happen during the "Compiling Scripts" phase of startup. I found the crash log and .dmp files, but I can't make heads or tails of them.
+1 1.2 years ago