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

Crashe while running on Unity 2019 #13

Open
Llhai opened this issue Jul 8, 2021 · 6 comments
Open

Crashe while running on Unity 2019 #13

Llhai opened this issue Jul 8, 2021 · 6 comments

Comments

@Llhai
Copy link

Llhai commented Jul 8, 2021

Thanks for your talent work!
It works perfectly on unity 2018, But but when I use Unity2019.4.23, the editor crashes.

The crashed code is
bool result = util.ParseIFCFile(file);

So. Can you help me to solve the problem, Thank you!

@helpsterTee
Copy link
Owner

Can you post a full crash log? The crash in this line only means something went wrong with the parser module. Maybe try to switch the API compatibility level in File -> Build Settings -> Player Settings -> Configuration

Unfortunately, I don't have a Windows system to test this anymore.

@Llhai
Copy link
Author

Llhai commented Jul 12, 2021

Editor.log
error.log
There are crash logs.
I tried th switch the API compatibility, but still carsh.
Thank you for your patience

@Llhai Llhai closed this as completed Jul 12, 2021
@helpsterTee
Copy link
Owner

Why did you close the issue? Did you resolve it yourself or just pressed the wrong button?

@Llhai Llhai reopened this Jul 12, 2021
@Llhai
Copy link
Author

Llhai commented Jul 12, 2021

Why did you close the issue? Did you resolve it yourself or just pressed the wrong button?

SORRY!!!, I just pressed the wrong button

@helpsterTee
Copy link
Owner

No problem.

IFCEngine is crashing when trying to load the IFC version in the IFC file to determine which schema to use.
This kind of error usually happens when something on the filesystem is not found or the file is invalid.

My wild guess is that it has something to do with asset handling (I think asset bundles changed from 2018 to 2019.4) and the necessary files (IFC2X3_TC1.exp) aren't there when the engine tries to load them. You could try creating a 2018 project and then opening and converting that in 2019.4, which should default to the asset pipeline v1, instead of using the asset pipeline v2.

I'm working on an alternative that should be platform-independent, instead of only compatible with Windows, but the progress is rather slow atm, sorry 😞

@Llhai
Copy link
Author

Llhai commented Jul 12, 2021

I tried to create a 2018 project and opening it in 2019, using the asset pipeline v1, but still crashed.
Looking for your new excellent work!!

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

2 participants