Torque 3D 3.6.1 preview build testing

#21 Outpost:
no crash

OS:
Win 8 x64

Seems to work fine so far

#22 Google Chrome display a warning on hyperlink (https://www.dropbox.com/s/ajs86591kcg4hpz/Binaries.zip?dl=0)
to download from dropbox to be a malicious code and block download....

#23 That's just because it's not a commonly downloaded file, and it's an .exe at that. I highly doubt you have anything to worry about when the committee is offering out files so the community can help with testing...

#24 No i don't have any worry the all about the files been infected is only pointer a issued so can be corrected it on the side so other wont be asking the same question that is all.

#25 And then how if some one running into that issue can get around it so it can be download it.

#26 If you're downloading from dan's dropbox, and not building from github, on chrome, you can go ahead and reject the download, then

go into chrome's download section:

and select recover:

#27 Thank you for the tip. Now other using Chrome can fallow these.

#28 What version of Visual Studio is support by the Engine now?
Thank you

#29 The Project Manager generates solutions for VS2008 and VS2010, but the 2010 works in 2012 and should work in 2013. CMake can generate solutions for most versions of VS, including 64-bit solutions.

#30 Tested x86 build with Visual Studio build files, works with VS120 and VS120_xp native in both debug in release. Windows 7 Professional x64.

#31 I've noticed that the T3D Master and development branch are now labeled 3.6, and have been for a few days or so. Is 3.6 official now, or still in testing?

Quote:The Project Manager generates solutions for VS2008 and VS2010, but the 2010 works in 2012 and should work in 2013.

Used the Project Manager this afternoon to generate the solutions. If I open the 2010 project in VS2013, it will perform the conversion process but still reports the solution as incompatible. Do I need to generate using CMake?

Edit: Ugh, after generating with CMake still says incompatible for VS2013 :/

Edit2: I believe I found the issue. When using CMake and choosing a generator I chose 'Visual Studio 12 2013 Win64', which seems like it should be the right choice. Unfortunately it's not, and by choosing 'Visual Studio 11 2012 Win64' I was able to compile it on VS2012 on the Win7 machine. Hadn't tried it again yet on 2013.

#32 Details to come in the release blog. Basically, I pushed to the master branch too soon, before we'd tested with people, so the version we'll announce will be 3.6.1.

Weird, other people have reported being able to use the VS2010 solutions with 13. I don't know enough about visual studio to be able to debug that... also seems very odd that the CMake solutions are invalid because those *definitely* work for us (our CI server uses them).

#33 I'll just chalk it off as my inexperience with using CMake in general :)

I was generating with CMake using the wrong generator I think Danny. Let me ask you something about adding new source files though. I managed to compile the 3.6 x64 build finally, but adding my new files to the /source folder doesn't compile them anymore. How should I go about using my custom files now?

#34 Just uploaded new binaries. They shouldn't be any different, but they now report their version as 3.6.1 and the Full template art has been improved in tiny ways.

Good question - I'd have to ask someone else actually as I'm not the CMake expert around here :P. For now, just add them directly to your generated solution, but there should be some way of automating that. The VS project named after your Torque project does have a folder for 'source', which looks like the place it should be put. But nothing's showing up there?

#35 It's just me stumbling over the new process, that's all Danny. Don't worry yourself with me. I'm so used to the old way of generating the stuff that I didn't re-generate the project after adding my custom files(using CMake). After I did that all is well and yes, the new files all show up as expected in the source folder :)

Sweet, gonna download the binaries and give those a run for you.

#36 Ouch, uh oh...The standard T3D gave me psychedelic Desert. Loaded up Empty Terrain and everything was a sea of mushroom magic colors. The x64 binary hung on launch of the mission. On Windows8.1.

#37 Whaaaaaaat. Okay I'll doube check.

#38 Okay, if you feel like it, check out the binary downloads on this page. They were built in VS2013 on our CI server. If they're messed up I don't know what's going on. I'm in Ubuntu for the evening so I can't test, but I'll do so as soon as I can.

EDIT: Can't reproduce your issues at all. :(

#39 Sorry I've just been able to get back to you Danny. Yea me either...I have no idea what caused it to begin with. I had downloaded the new binaries and on the first run of Empty Terrain, magic world! Since then, I've tried and tried to replicate it but no luck. I have no idea what that was all about. I keep my PC's drivers and stuff up to date etc.

Anyways, today I did some research to find out what has been wrong with my VS2010 x64 environment. I like VS2010, for some reason I've just grown attached to it...lol. So it turns out it is a common issue with VS2010. The problem lies with VS2010 Service Pack 1. Basically, what happens is if you install VS2010 SP1 prior to the Win7 SDK the SDK won't install properly. In some cases if you had the Win7 SDK installed prior to the SP1, without applying the patch for Win7 SDK Compilers, the SP1 would actually remove the x64 compilers. It's all a hot mess, so what you have to do is install your VS2010 tools in a very specific order:

1-Install Win7 SDK (winsdk_web)
2-Install Win7 SDK Compiler patch (VC-Compiler-KB2519277)
3-Install VS2010 Express (vc_web)
4-Install VS2010 ServicePack 1 (VS10sp1-KB983509)

I just downloaded the current Master 3.6.1 branch tonight, and I am happy to report I was able to compile the x64 build on VS2010 with no problems!!(generated with CMake)

#40 Both binaries crash when loading any mission. No errors :|

Windows 7 x64 / SP1
Core i7-4770 @ 3.5GHz / 16GB RAM
Gefore GTX660 Ti / 344.11 stable drivers
2 x 1920 x 1080 / 60Hz