Game Development Community

Torque Game Builder - Resource Tutorial - followed instructions but not working for me

by Zachary Buckholz · in Technical Issues · 02/20/2011 (9:22 pm) · 6 replies

I have been going through each tutorial, and when trying to work through the "Torque Game Builder - Resource Tutorial", I seem to have completed it without any TGB generated errors. However none of the items I supposedly imported actually show. What I get is black boxes where I should be seeing the resources. I went through the tutorial again, and believe I double checked every step. Has anyone else gone through this tutorial, did you succeed?

About the author

Linux admin currently on contract for large multi-national company that provides payment solutions for business's and individuals. Looking forward to mastering this iTorque 2D technology, and creating really cool games with my 10 year old son.


#1
02/21/2011 (5:32 am)
If you post a link to the tutorial you are talking about along with your console.log file output I will try and help you. Maybe a screenshot also?
#2
02/21/2011 (10:59 am)
Odd. I thought this bug was fixed in a previous version of iT2D. In the earlier versions, the original team bypassed the code that would support resources. I thought it had been fixed, but I guess it was never fully solved. It's a problem with the engine itself, not the tutorial.
#3
02/21/2011 (11:58 am)
Can I get access to your Jira tracking system, so I can search for other issues I may come across and contribute anything new.
#4
02/21/2011 (12:21 pm)
@Zachary - We have toyed with that idea in the past, but we decided we will not be opening up our Jira tracker to the public. After 1.4.1 releases, I will keep a thread of known issues stickied in this forum. We will update it as we confirm bug reports, sort of like a Jira summary.
#5
02/21/2011 (12:27 pm)
If you wanted access to the Jira tracker you would have to get it the hard way:

jobs@garagegames.com
#6
10/05/2011 (1:23 pm)
Got the exact same issue so I am guessing this isn't fixed yet?

~E