TSE "Milestone 3.5" Update
by Ben Garney · in Torque Game Engine Advanced · 06/30/2006 (11:06 am) · 246 replies
Hi guys,
We've checked the next TSE update into CVS. It's NOT Milestone 4 - so no fancy lighting - but it does include many bugfixes, a new vastly more efficient rendering infrastructure (ported from Marble Blast Ultra), way faster skinning, and the first drop of the new Atlas codebase.
Brian has more complete info on the delta in this update, and should be posting it sometime in the not too distant future - I just wanted to let you guys know what was up ASAP. :)
Please note that some parts of this are still a little rough, and the new Atlas codebase does not yet have the full complement of art tools, but everything is functional and ready to use.
This thread is for posting general feedback on the release and collaborating on any bugs that might come up. Please be patient, as here in the States we're just about to go into a 4 day weekend - so responses might be a little slow. But we are committed to making everything work 100%, so definitely let us know what your experiences are!
Regards,
Ben Garney
Torque Technologies Director
We've checked the next TSE update into CVS. It's NOT Milestone 4 - so no fancy lighting - but it does include many bugfixes, a new vastly more efficient rendering infrastructure (ported from Marble Blast Ultra), way faster skinning, and the first drop of the new Atlas codebase.
Brian has more complete info on the delta in this update, and should be posting it sometime in the not too distant future - I just wanted to let you guys know what was up ASAP. :)
Please note that some parts of this are still a little rough, and the new Atlas codebase does not yet have the full complement of art tools, but everything is functional and ready to use.
This thread is for posting general feedback on the release and collaborating on any bugs that might come up. Please be patient, as here in the States we're just about to go into a 4 day weekend - so responses might be a little slow. But we are committed to making everything work 100%, so definitely let us know what your experiences are!
Regards,
Ben Garney
Torque Technologies Director
#142
Yeah - well... I think in this case we have a few small bugs (on VS2k5 mostly, so we're testing w/ that now), and some build file snafus. It looks like everything is in (see Michael Branin's comment "Ok I fixed this issue. the TSESDK.vproj is pointing to the wrong folder for libqslim.vcproj I fixed that error." I wish he'd tell us what he did to fix the error, though. :).
Obviously only time will tell... and hopefully we're giving good response time to people's problems. :)
07/04/2006 (1:48 pm)
Thanks for understanding. :)Yeah - well... I think in this case we have a few small bugs (on VS2k5 mostly, so we're testing w/ that now), and some build file snafus. It looks like everything is in (see Michael Branin's comment "Ok I fixed this issue. the TSESDK.vproj is pointing to the wrong folder for libqslim.vcproj I fixed that error." I wish he'd tell us what he did to fix the error, though. :).
Obviously only time will tell... and hopefully we're giving good response time to people's problems. :)
#143
07/04/2006 (1:50 pm)
Okay cool. BTW Ben, is MS3 completed? since we're at MS3.5. should you guys have it updated on the site? or is there still much more bugs to fix? i havnt really been paying too much attention to TSE lately, mostly TGE, so i'm not up to date on whats really happenning.
#144
We'll be announcing things on the site once this "put it out and see what lights on fire" phase is done.
07/04/2006 (1:58 pm)
I'll let Brian field that one. :)We'll be announcing things on the site once this "put it out and see what lights on fire" phase is done.
#145
and change it to:
That's what needed to change in the vc8 TSESDK.sln file. It was looking for the libqslim project file in the same folder as the other project files.
07/04/2006 (2:18 pm)
@Ben - Open the TSESDK.sln file in notepad and look for this:"libqslim", "libqslim.vcproj",
and change it to:
"libqslim", "..\lib\libqslim\libqslim.vcproj",
That's what needed to change in the vc8 TSESDK.sln file. It was looking for the libqslim project file in the same folder as the other project files.
#146
07/04/2006 (2:19 pm)
Awesome, thank you Bryan! This will let us fix things much more quickly on our end. :)
#147
I think that the current libqslim.vcproj should be moved to the VC7 project folder as well
EDIT: had to type most of it again because it only took the first few words when i submitted first <.<
07/04/2006 (2:30 pm)
Actually that is not the right fix ... because at "..\lib\libqslim\libqslim.vcproj" is the VC7 version you would have to manually convert it to VC8 everytime. I did send a converted libqslim.vcproj file along with the rest to brian that was supposed to go into the VC8 folder. Must have been forgotten.I think that the current libqslim.vcproj should be moved to the VC7 project folder as well
EDIT: had to type most of it again because it only took the first few words when i submitted first <.<
#148
#1 that post was geared towards all the belly achers, not just you.
#2 you said nothing about the build working, but instead a general 'fix all errors' comment:
I can see that this is leading into a flame war, so this'll be my last post in reply to belly achers who think GG is some huge company with a large QA department. oh... wait.. MS is and released buggy crap all the time....
*pulls out extinguisher*
07/04/2006 (2:45 pm)
Quote:uhhh what? i just say, make sure the build works before uploading it to cvs. The rule of thumb, well at least where i worked at. If it doesnt compile, dont commit the code.
#1 that post was geared towards all the belly achers, not just you.
#2 you said nothing about the build working, but instead a general 'fix all errors' comment:
Quote:Arg. GG, please fix your errors before you upload it to the CVS.#3 if you don't care about tse, then why complain when it doesn't work fully on all systems?
I can see that this is leading into a flame war, so this'll be my last post in reply to belly achers who think GG is some huge company with a large QA department. oh... wait.. MS is and released buggy crap all the time....
*pulls out extinguisher*
#149
07/04/2006 (2:45 pm)
@Florian - You are right. I also, created a working VC8 project for TSE and had to upgrade the libqslim project to version 8. so that it would place the lib file in the correct folder when you compile it.
#150
07/04/2006 (2:46 pm)
... not necessary anymore ...
#151
man, you really got to lean2read(check all post). but none the less. lets end this, to prevent a flame war.
07/04/2006 (3:06 pm)
@Jonathon Stevensman, you really got to lean2read(check all post). but none the less. lets end this, to prevent a flame war.
#152
@Jonathon: No need to get in anyone's face over this. I think everyone's made their points, and going into any more detail really isn't going to help. Hopefully T Squared has the good graces not to take things any further. :)
07/04/2006 (3:08 pm)
@Bryan/Florian: Thanks for following up on your stuff - I guess I'll have to... uh.. "gently remind" Brian that he needs to check added files in as well as changes. ;)@Jonathon: No need to get in anyone's face over this. I think everyone's made their points, and going into any more detail really isn't going to help. Hopefully T Squared has the good graces not to take things any further. :)
#153
If you want to make this a public flamewar, that's your problem - just like how you can consider yourself a professional developer if you can't either a) fix the problems on your end w/o complaint, or b) work with the community and GG employees in a mature fashion to get things going.
PS - Flamers need not apply here. This thread is for troubleshooting and support on the TSE 3.5 release. If people cannot be civil & on topic I will be forced to be heavy handed - which none of us want. If you have to call someone out, at least do it in a seperate thread. :P
07/04/2006 (3:13 pm)
@Anton: I didn't realize "supporting Torque artists" meant being personally accountable for making you a build at 9pm on a Sunday night, aftering staying at the office all weekend making sure that the build was supported & that everyone with problems at least got some feedback and help. If you want to make this a public flamewar, that's your problem - just like how you can consider yourself a professional developer if you can't either a) fix the problems on your end w/o complaint, or b) work with the community and GG employees in a mature fashion to get things going.
PS - Flamers need not apply here. This thread is for troubleshooting and support on the TSE 3.5 release. If people cannot be civil & on topic I will be forced to be heavy handed - which none of us want. If you have to call someone out, at least do it in a seperate thread. :P
#155
07/04/2006 (3:30 pm)
@Florian - did you go through all of the project files and fix their output folders? I had to upgrade each project file and then fix the output path on each project.
#156
07/04/2006 (3:31 pm)
From Brian's post earlier in the thread:Quote:
Here's a more complete list of what's in this update:
Atlas 2.0 update - I'll let Ben elaborate on that
Render Batching - see my latest .plan
Optimized skinning further - fixed some performance issues
Added support for dynamic vertex buffers in addition to the "static" and "volatile" buffers in TSE.
Added a warning material that will show up if a piece of geometry doesn't have a material mapped to it.
Debris is now rendering in TSE.
Tons of bug fixes (this is just a few):
Disappearing water on editing change is fixed
Objects/terrain jumping around in editor is fixed
Fixed XInput init problem
Fixed text edit control problem
#157
07/04/2006 (3:41 pm)
... not necessary anymore ...
#158
added a "..\lib\libqslim\" before every cxx/h file using notepad :)
07/04/2006 (3:47 pm)
Yes i had to manually change all the paths in "libqslim.vcproject" to reflect that the project file was moved.added a "..\lib\libqslim\" before every cxx/h file using notepad :)
#159
07/04/2006 (4:08 pm)
I just grabbed a fresh CVS checkout, copied the missing (edited and converted) libqslim.vcproj to the VC8 folder and changedadio->setCallback(this, AtlasTOC::cbOnChunkWriteComplete, key);to
adio->setCallback(this, [b]&[/b]AtlasTOC::cbOnChunkWriteComplete, key);and it compiled without errors. So i think its just those two issues that are left in order to "compile" succesfully. :)
#160
Status update for everyone - I have the & fix checked into SVN and Brian will take care of libqslim when he gets in tomorrow, so sometime tomorrow we should have a CVS update with those fixes and maybe some other goodies too. ;)
07/04/2006 (4:12 pm)
Thanks for the summary Florian!Status update for everyone - I have the & fix checked into SVN and Brian will take care of libqslim when he gets in tomorrow, so sometime tomorrow we should have a CVS update with those fixes and maybe some other goodies too. ;)
Torque 3D Owner Thanhda Tie
Digital Shock Inc.