Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to build legacy projects with Torque3D 4.0.3? #1239

Open
Capewearer opened this issue Mar 20, 2024 · 6 comments
Open

How to build legacy projects with Torque3D 4.0.3? #1239

Capewearer opened this issue Mar 20, 2024 · 6 comments

Comments

@Capewearer
Copy link

Capewearer commented Mar 20, 2024

When I tried it last time for FPS-Tutorial sample I got only floating camera with wrongly imported assets for Chinatown map. Everything was done on Windows 7.
изображение

@marauder2k7
Copy link
Contributor

marauder2k7 commented Mar 21, 2024

FPS-Tutorial is in a different format to what the engine uses now, but there was a tool created for importing older projects into the newer structure

@Areloch
Copy link
Contributor

Areloch commented Mar 21, 2024

I'll try and run the FPS-Tutorial/Chinatown stuff through the Project Importer Tool tomorrow and try and pin down why it looks like nothing imported successfully. The importer isn't perfect, but it should be doing better than 0.

@Capewearer
Copy link
Author

Is there any investigations or this bug is irreproducible?

@Areloch
Copy link
Contributor

Areloch commented Mar 23, 2024

Apologies on the delay. While I don't get quite the same result(it actually fails to compile a shader and crashes for me) it definitely am seeing a lot of unfound assets and errors and stuff in my log.
So i'll be digging into this more for sure because that's definitely not supposed to happen, heh.

And just to be sure, you just ran the Legacy Project Importer and pointed it at the directory that the FPSTutorial.exe is in and let it complete?

@Capewearer
Copy link
Author

It's okay you delayed answer. Yes, I did import as you said. Also I tried reproducing the same result second time, I actually got failed shader compilation and after relaunching Torque engine achieved the same missing assets result.

@Areloch
Copy link
Contributor

Areloch commented Mar 23, 2024

Ok, so yeah sounding like we're pretty much on the same page, then. I'll do some digging and figure out where it's all breaking down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants