3D games on Xbox360 may crash.

#1 I would second that question as it seems a fundamental requirement that Torque X actually works on an XBox 360. That's pretty much it's whole reason for being after all!

#2 when running the FPS demo physics level on the 360 the frame rate drops drastically, can hardly move the player anymore, and the menu's take forever to select. Is there a fix for this problem. I reduced the number of boxes to 4, and removed the spheres, and it improved. Probably a issue with the physics.

Best Regards.

#3 Wait, what do you mean it crashes on Xbox 360?

#4 I was commenting on the release notes. 2 notes for 3D, #2 xbox may crash. I guess that is what was holding it up.

I still paid for it! : )

#5 @Henry

Your question is 100% valid. From what the microsoft guys have said (I'm a creators club premium member). Nothing you release, that crashes an XBox will be allowed. They are totally un-movable on that issue. The only odd thing is that the creators club guys at microsoft seemed oblivious to TX3D even existing at all!

#6 Are there more detailed patch notes available? My game is 2d but a note as general as the 3D games may crash on the 360 makes me wonder what other smaller issues the engine may have.

Also is there a list of bugs that where fixed? I've found a host of bugs ranging from memory leaks to particle problems and it would help to see what bugs have been fixed if any with this release.

Could we get any more visibility into what changes have been made with the 3.0 release?

#7 First off, as part of the Torque X team, I was against including that in the release notes because it is ambiguous and not actionable. It is there because during testing on an Xbox 360, a repeatable crash was encountered. We're still investigating it and plan to have a fix posted as soon as possible. The crash sometimes occured in the FPS split-screen demo when one player faces another player. In the meantime, I have about 15 other 3D projects running on the Xbox 360 and have yet to crash it (without me doing something silly in my game code). I'll try to find a list of all the engine fixes and post it.

John K.
www.envygames.com

#8 Thanks John. I think they should have listened to you or have at least re-worded that note.

Thanks for clearing that up.

#9 Thanks John. Unfortunately they would have had to include that note. I would rather GG were honest about such things than cover them up and I end up with Microsoft pulling my game down from creators after encountering the bug.

#10 Thanks John, My comment was on the ambiguity of it all. I would prefer to know what causes a crash to avoid it and avoid the madness over in the XNA CC.

#11 I'm glad to help. But there is definitely no "cover up" going on. GG really wanted to push this out as quickly as possible balancing with quality. I personally prefer the approach of releasing sooner with some bugs as opposed to releasing later without bugs especially since bug-free software is impossible ;)

But we're still making progress with the engine and I'm hoping to see some new features (not just bug fixes) in the next release.

John K.
www.envygames.com

#12 No accusations of a cover up! I am glad to have this in my hands. I will probably have my next XNA game out this month yet. Thanks John, keep up the good work.

#13 Thanks Henry, I really want to see what you're working on. And, the new Dream-Build-Play competition is on, so be sure to submit ;)

John K.
www.envygames.com

#14 @John

Understand the 15 projects that you have that work, but this is the demo you are selling your engine on. I can crash the FPS demo 100% of the time with a code 4. I sure hope you get it fixed soon, because developers like me who come here soley because of the new Microsoft CClub download that was posted a few days ago are all gonna check it out. Sucks that your engine will be writen off by alot of people over the next week because your main demo that showcases your engine doesn't work. Why not make 1 of your 15 projects the demo? I would like to see what this engine is capable of, but a demo that crashes 100% of the time with a code 4 is worrying at best.

#15 John, Not to turn this into a philosophy debate, but simply to support something you said. I also agree on sending something out the door sooner rather than later. I am sure you guys balanced stablility with time out very carefully. There will always be bugs and probably many of them you won't find until you DO release the product into the wild.

I would hope (and guess) that you guys didn't release with a ton of known bugs with no work around. From the release notes and what you said here it looks like the bugs are specific and there are work arounds or just "don't do that" for now things.

Kudos on standing up for that.

PS A better description of the bug would probably have been better, but I am glad it was in there rather than not at all.