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

Forest in Outpost level not appearing in Ubuntu #1287

Closed
crabmusket opened this Issue Apr 27, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@crabmusket
Contributor

crabmusket commented Apr 27, 2015

Level loads, but no forest trees exist. Relevant extract from console.log:

Executing levels/Outpost.mis.
Failed to create resource: [levels/outpost.forest]
levels/Outpost.mis (0): Register object failed for object theForest of class Forest.

Putting this here to remind myself to look into it, and see if anyone else has the issue.

@LuisAntonRebollo

This comment has been minimized.

Show comment
Hide comment
@LuisAntonRebollo

LuisAntonRebollo Apr 28, 2015

Contributor

Can be a case-sensitive problem in the file name.

Executing levels/Outpost.mis.
Failed to create resource: [levels/outpost.forest]
Contributor

LuisAntonRebollo commented Apr 28, 2015

Can be a case-sensitive problem in the file name.

Executing levels/Outpost.mis.
Failed to create resource: [levels/outpost.forest]
@crabmusket

This comment has been minimized.

Show comment
Hide comment
@crabmusket

crabmusket Apr 28, 2015

Contributor

😭 I'll check it later on.

Contributor

crabmusket commented Apr 28, 2015

😭 I'll check it later on.

@crabmusket

This comment has been minimized.

Show comment
Hide comment
@crabmusket

crabmusket May 16, 2015

Contributor

Okay, that was the problem, but fixing that causes a super hard crash when the level loads. Yay.

screenshot from 2015-05-16 18 14 00

See the middle console for the error message.

EDIT: also, yes, I forgot that SIGKILL was 9 and SIGTERM was something else :p.

Contributor

crabmusket commented May 16, 2015

Okay, that was the problem, but fixing that causes a super hard crash when the level loads. Yay.

screenshot from 2015-05-16 18 14 00

See the middle console for the error message.

EDIT: also, yes, I forgot that SIGKILL was 9 and SIGTERM was something else :p.

@crabmusket

This comment has been minimized.

Show comment
Hide comment
@crabmusket

crabmusket May 16, 2015

Contributor

@Azaezel, you were right. When you posted that line with the defaulttree.dae, I thought you were referring to the other place that line exists, which is in some random TSStatic that was also causing console errors, which I had fixed, but hadn't fixed in the forest item definition.

As for the source of the crash, the problem originates in tsForestItemData.h:

   const Box3F& getObjBox() const { return mShape ? mShape->bounds : Box3F::Invalid; }

When the shape file is not found, every item gets given an invalid object box. Then, when the forest cell goes to update its bounds, it tries to update with all these invalid boxes.

I've made two PRs from this. #1307 fixes the default bounds issue. If you're missing a shape file, you really don't want a crash, you want a console error, which you do currently get. #1308 fixes the filename case :p.

Oh, and #1309 adds more detail to that fatal assert we were looking at :p.

Contributor

crabmusket commented May 16, 2015

@Azaezel, you were right. When you posted that line with the defaulttree.dae, I thought you were referring to the other place that line exists, which is in some random TSStatic that was also causing console errors, which I had fixed, but hadn't fixed in the forest item definition.

As for the source of the crash, the problem originates in tsForestItemData.h:

   const Box3F& getObjBox() const { return mShape ? mShape->bounds : Box3F::Invalid; }

When the shape file is not found, every item gets given an invalid object box. Then, when the forest cell goes to update its bounds, it tries to update with all these invalid boxes.

I've made two PRs from this. #1307 fixes the default bounds issue. If you're missing a shape file, you really don't want a crash, you want a console error, which you do currently get. #1308 fixes the filename case :p.

Oh, and #1309 adds more detail to that fatal assert we were looking at :p.

@crabmusket crabmusket closed this May 17, 2015

RichardRanft added a commit to RichardRanft/Torque3D that referenced this issue Jul 25, 2015

RichardRanft added a commit to RichardRanft/Torque3D that referenced this issue Jul 25, 2015

RichardRanft added a commit to RichardRanft/Torque3D that referenced this issue Jul 25, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment