TSE "Milestone 3.5" Update
by Kyle Carter · 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
#122
07/03/2006 (4:13 pm)
Because it's the C runtime, it's tracked seperately. In VC7.1 the setting is under C/C++ -> Code Generation. 
#123
07/03/2006 (5:23 pm)
OK, vc7 and vc8 project files have been updated. Should all be happy now. Thanks Florian and others who helped out with this. 
#124
WOW...im exited!!!Thank you all for your help!!!!...although im glad to hear is all good with 2005...
07/03/2006 (8:27 pm)
Yes thank you all...in my fustration with all of this I un-Installed VS2005 and got out and dusted off the copy of 2003 and what do you know...It compiled with out any error or warnings of anykind!!!!WOW...im exited!!!Thank you all for your help!!!!...although im glad to hear is all good with 2005...
#125
it seems to have problems with the atlas code.
07/03/2006 (10:31 pm)
This update just made it have more errors.it seems to have problems with the atlas code.
#126
07/03/2006 (10:36 pm)
Wish it worked for me. I am still getting craploads of errors, and thinking that maybe I fubared the CVS somehow I deleted and redownloaded CVS and bah ... you have hit your download quota for the day .. so denied . have to wait 24 hours to try again.
#127
61 errors to be precise.
WinXP Home SP2, VC 2005 Express, DXSDK April
This is the same problem I've had the whole time. I have this problem with the VC7 project, I had it with the redistributed converted VC8 project, and now I have it with the official VC8 project... so I guess it's not the project? Any ideas?
07/03/2006 (11:14 pm)
I just did redownload the entire CVS, just on the offchance it was something wierd. I am still getting a bunch of errors that look like this:c:\tse\engine\atlas\core\atlasresourcetoc.h(387) : error C3867: 'AtlasTOC::cbPostBackToAtlasFile': function call missing argument list; use '&AtlasTOC::cbPostBackToAtlasFile' to create a pointer to member
c:\tse\engine\atlas\core\atlasresourcetoc.h(378) : while compiling class template member function 'void AtlasResourceTOC<StubType>::cbPopulateChunkReadNote(AtlasReadNote *)'
with
[
StubType=AtlasResourceConfigStub
]
c:\tse\engine\atlas\resource\atlasresourceconfigtoc.h(63) : see reference to class template instantiation 'AtlasResourceTOC<StubType>' being compiled
with
[
StubType=AtlasResourceConfigStub
]61 errors to be precise.
WinXP Home SP2, VC 2005 Express, DXSDK April
This is the same problem I've had the whole time. I have this problem with the VC7 project, I had it with the redistributed converted VC8 project, and now I have it with the official VC8 project... so I guess it's not the project? Any ideas?
#128
First, as the error says, find all the error, and add a & in front of the altas part, should shave off a load of errors.
second, make sure you have user32.lib, Advapi32.lib, gdi32.lib, ole32.lib and oleaut32.lib in your additional dependancies in the project's linker properties.
Make sure you set it to use the UNICODE set as well.
If you have all of that, it should compile just fine.
07/03/2006 (11:32 pm)
You had the exact samesetup i had(same error count and everything)First, as the error says, find all the error, and add a & in front of the altas part, should shave off a load of errors.
second, make sure you have user32.lib, Advapi32.lib, gdi32.lib, ole32.lib and oleaut32.lib in your additional dependancies in the project's linker properties.
Make sure you set it to use the UNICODE set as well.
If you have all of that, it should compile just fine.
#129
07/03/2006 (11:33 pm)
I've got a copy of TSE_DEBUG.exe that I can email anyone who emails and asks me for it. Just post on here so I know you are a TSE licensee. :)
#130
07/04/2006 (12:21 am)
Same here!!....if you need a compiled EXE.....
#131
sparhwk@hotmail.com
07/04/2006 (4:18 am)
I could use the exe please, I am still having trouble compiling this.sparhwk@hotmail.com
#132
Project file 'F:\torque\TSE\vc8\libqslim.vcproj' could not be loaded.
The project is either missing from disk or access was denied.
the project is not in the newly downloaded cvs.
Ok I fixed this issue. the TSESDK.vproj is pointing to the wrong folder for libqslim.vcproj I fixed that error.
07/04/2006 (7:25 am)
OK I just pulled a fresh CVS. Upon Starting the vc8 Project I immediately get this error box.Project file 'F:\torque\TSE\vc8\libqslim.vcproj' could not be loaded.
The project is either missing from disk or access was denied.
the project is not in the newly downloaded cvs.
Ok I fixed this issue. the TSESDK.vproj is pointing to the wrong folder for libqslim.vcproj I fixed that error.
#133
07/04/2006 (9:30 am)
Arg. GG, please fix your errors before you upload it to the CVS.
#134
Just to be clear - we're completely committed to fixing every bug, but there's no way we can identify all of them without ever releasing code to you guys! (And I'm sure you guys are happier to be more closely involved in the development process, rather than waiting months and months between milestones.)
@Michael - you don't need that project to compile TSE, incidentally. But it's good you got it fixed. What was wrong with the project file - where was it pointing instead of the right place?
07/04/2006 (12:18 pm)
Friendly Warning: If you're not willing to deal with working out the final little bugs with us (which are going to show up when you go from having 2 guys testing something to a thousand guys testing it!), it might be best to wait until we've committed all the fixes from this initial soft release of 3.5 to CVS. When we have done that we will be doing a more formal announcement on the GG site about the update.Just to be clear - we're completely committed to fixing every bug, but there's no way we can identify all of them without ever releasing code to you guys! (And I'm sure you guys are happier to be more closely involved in the development process, rather than waiting months and months between milestones.)
@Michael - you don't need that project to compile TSE, incidentally. But it's good you got it fixed. What was wrong with the project file - where was it pointing instead of the right place?
#135
I agree with Ben. When I see things Like what T Squared posted, it makes me sick. You guys complain for GG to hurry up and release things *cough* constructor *cought* faster, yet when they do *cough* TSE *cough* you get pissed that it's not all working properly. Don't forget those two little letters after TSE that say EA. That means stuff ISN'T going to work fully most of the time they do a push to CVS.
Think about productivity for a moment. What's more productive and allows for faster development: Release code that may be broken to thousands of people to test and give instant (and I mean within minutes of releasing) feedback on issues; not releasing the code and having a few internal people with a few computer setups and graphics setups testing it?
Use your head guys, give em a break. Sheesh
*rant disabled*
07/04/2006 (12:28 pm)
*rant enabled*I agree with Ben. When I see things Like what T Squared posted, it makes me sick. You guys complain for GG to hurry up and release things *cough* constructor *cought* faster, yet when they do *cough* TSE *cough* you get pissed that it's not all working properly. Don't forget those two little letters after TSE that say EA. That means stuff ISN'T going to work fully most of the time they do a push to CVS.
Think about productivity for a moment. What's more productive and allows for faster development: Release code that may be broken to thousands of people to test and give instant (and I mean within minutes of releasing) feedback on issues; not releasing the code and having a few internal people with a few computer setups and graphics setups testing it?
Use your head guys, give em a break. Sheesh
*rant disabled*
#136
07/04/2006 (1:12 pm)
/agree
#137
07/04/2006 (1:31 pm)
@Ben Keep doing what your doing, and thank you for all the help you have given us during what must be time you have off of work [unless @ gg they work you Saturday,Sunday and the 4th of July]
#138
Thanks everyone for pitching in and making this release succesful. Have I mentioned that the community here has pretty fantastic attitudes, all told? :)
(PS - let me know if anything else comes up - Brian and I will be doing some more work on getting stuff out to CVS tomorrow when he's back in the office.)
07/04/2006 (1:33 pm)
No worries - they have AC at work, while home is nice and toasty at the moment. :)Thanks everyone for pitching in and making this release succesful. Have I mentioned that the community here has pretty fantastic attitudes, all told? :)
(PS - let me know if anything else comes up - Brian and I will be doing some more work on getting stuff out to CVS tomorrow when he's back in the office.)
#139
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. But anwyay i dont really care too much for TSE at all. and i'm not telling them to hurry up at all. please show me were i said that. If you have every read my post history you see that i'm cool with them taking time to do it. So please take the time RIGHT NOW to do so before you mouth off to me.
@Ben
Cool, just let us know when its been committed to the CVS bug free.
07/04/2006 (1:38 pm)
@Jonathon Stevensuhhh 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. But anwyay i dont really care too much for TSE at all. and i'm not telling them to hurry up at all. please show me were i said that. If you have every read my post history you see that i'm cool with them taking time to do it. So please take the time RIGHT NOW to do so before you mouth off to me.
@Ben
Cool, just let us know when its been committed to the CVS bug free.
#140
We ALWAYS check that our code compiles before checking it in. Brian and I both have done several clean builds from CVS to double check this. It's only by posting it and seeing what breaks for other people that we can fix problems beyond that. If you have a better approach, please share! :)
07/04/2006 (1:41 pm)
Like I explained - we did test it, and it did work (for VC7). Not our fault that VC7 keeps its settings in strange places - now that we know about it we can avoid it of course.We ALWAYS check that our code compiles before checking it in. Brian and I both have done several clean builds from CVS to double check this. It's only by posting it and seeing what breaks for other people that we can fix problems beyond that. If you have a better approach, please share! :)
Torque 3D Owner Jonathon Stevens