Torque 3D 3.7 released
-
triggerfish
- Posts: 24
- Joined: Fri Jun 26, 2015 12:11 am
Thanks buckmaster,
Here's the link to my console.log on pastebin:
http://pastebin.com/frTmXMBs
I was not able to post the entire thing as pastsbin said it was too big. The last messages just repeat thousands of times.
Do you need my system info? Here it is:
http://pastebin.com/GYuLdZ9A
Thanks for all your hard work!
Here's the link to my console.log on pastebin:
http://pastebin.com/frTmXMBs
I was not able to post the entire thing as pastsbin said it was too big. The last messages just repeat thousands of times.
Do you need my system info? Here it is:
http://pastebin.com/GYuLdZ9A
Thanks for all your hard work!
Also, in alignment with the OP's statement about us focusing on stability for 3.8, I've started drafting a "hard" list of things to test prefacing a release.
It's intended as a checklist to make sure we hit as many parts of the engine to ensure it's functioning without surprise gotchas we didn't catch in general testing, which is how we've had the instability slowly creep up on us until now.
As such, I've started a new wiki page that I'll be filling out with an as-exhaustive-list-as-possible listing that we can walk down and check off to make sure a release is as stable as we're going to be able to make it before getting it to the masses.
That page is here.
If there's anything you can think of that needs to be tested, feel free to modify that page or pass it along here or to me via PM. The entire problem we've been having is it's almost impossible for one person to think of EVERYTHING that needs testing, so even if I detail an exhaustive list, there's no doubt some things I'll not think of or forget that you people have noted or tested yourselves.
It's intended as a checklist to make sure we hit as many parts of the engine to ensure it's functioning without surprise gotchas we didn't catch in general testing, which is how we've had the instability slowly creep up on us until now.
As such, I've started a new wiki page that I'll be filling out with an as-exhaustive-list-as-possible listing that we can walk down and check off to make sure a release is as stable as we're going to be able to make it before getting it to the masses.
That page is here.
If there's anything you can think of that needs to be tested, feel free to modify that page or pass it along here or to me via PM. The entire problem we've been having is it's almost impossible for one person to think of EVERYTHING that needs testing, so even if I detail an exhaustive list, there's no doubt some things I'll not think of or forget that you people have noted or tested yourselves.
-
triggerfish
- Posts: 24
- Joined: Fri Jun 26, 2015 12:11 am
Hi buckmaster. I wanted to check to see if you were able to open the pastebin links I sent in my last post. Please let me know if you need any more information from my system. Thank you!
-
buckmaster
- Steering Committee
- Posts: 321
- Joined: Thu Feb 05, 2015 1:02 am
@ triggerfish I have, thanks for that. Not a lot of time right now but I'll try to find a moment to have a look!
-
buckmaster
- Steering Committee
- Posts: 321
- Joined: Thu Feb 05, 2015 1:02 am
@ saindd, check out this PR.
-
buckmaster
- Steering Committee
- Posts: 321
- Joined: Thu Feb 05, 2015 1:02 am
-
buckmaster
- Steering Committee
- Posts: 321
- Joined: Thu Feb 05, 2015 1:02 am
Usually by using CMake to generate 64-bit VS solutions, not the project generator.
Who is online
Users browsing this forum: Bing [Bot] and 1 guest
