69 replies to this topic

[GranoblasticMan]

I really don't understand how a mistake like this could happen in a professional development team unless you're not using proper revision/source control.

[Ranzear]

GranoblasticMan, on 22 March 2013 - 02:05 PM, said:

I really don't understand how a mistake like this could happen in a professional development team unless you're not using proper revision/source control.

Considering that's exactly what he admitted to in the OP... yes?

[Foster Bondroff]

To be honest. Don't fix em out. The situation with both modes only half added is better than the "magic thermal mode" available before.

[Roland]

So is this actually in the game or what? Cause my thermal looks like it always has.

[Targetloc]

Roland, on 22 March 2013 - 03:01 PM, said:

So is this actually in the game or what? Cause my thermal looks like it always has.

http://mwomercs.com/...56#entry2109856

[Stainless Steel]

Matt Newman, on 22 March 2013 - 10:17 AM, said:

and a cool new video
http://www.youtube.c...d&v=ddL0OTjWNUc

It's a shame that your budget doesn't extend to licensing Elvis to play over those loudspeakers visible on that Hero Highlander at the 21 second mark. (I recall that the budget for adding Viva Las Vegas into Fallout:Las Vegas was going to be more then the entire music budget for the game)

[Vapor Trail]

Have to say, the video was pretty nice.

[Vapor Trail]

Stainless Steel, on 22 March 2013 - 03:35 PM, said:

It's a shame that your budget doesn't extend to licensing Elvis to play over those loudspeakers visible on that Hero Highlander at the 21 second mark. (I recall that the budget for adding Viva Las Vegas into Fallout:Las Vegas was going to be more then the entire music budget for the game)

Wonder if they can afford some Queen?

Edited by Vapor Trail, 22 March 2013 - 03:56 PM.

[Brothergrimm]

Matthew Craig, on 22 March 2013 - 12:52 PM, said:

Ever tried to get an artist to use git

One, successfully actually - but not a scientific sample. Some git GUI's are quite good now. If set up correctly they just have to do is push and pull, with someone upstream handling merges.

I admit I am failing with office workers though, but that has more to do with there being no diff for excel files worth a damn.

[Vapor Trail]

With a big enough cattle prod you can teach a bear to dance.

I figure artists would be easier.

[and zero]

Hm. Neither vision mode has reverted back to normal for me. Now i cant see anything on river city night. An atlas killed me at close range and it looked like god had descended to cut me down (entire atlas blinding white in thermal)

[Corvus Antaka]

ty for updates like these.

[Budor]

Current thermal is how night vision should look ^^



I do like the range restriction on it:

[Sable Dove]

Proof the devs are out of touch? During testing no one used thermal? This is Thermal Warrior Online. Thermal ought to be the default vision mode.

I'm kidding, by the way.

In seriousness though, just take the thermal as it was (the newer, unfinished one), increase the range, and slap a green tint on it and that's nightvision. All thermal needed was to show enemy mechs more brightly.

[Ialdabaoth]

GranoblasticMan, on 22 March 2013 - 02:05 PM, said:

I really don't understand how a mistake like this could happen in a professional development team unless you're not using proper revision/source control.

That's what happens when you do a 'hotfix'. Hotfixes almost always happen outside the revision/source control loop, because there's so much pressure to get them out the door.

[Bagheera]

I miss the days when NV was grayvision.

[Gremlich Johns]

here is a link to a bunch of thermal night vision view images.

When I was on the XM-1 project in 1980-1981, we could spot jackrabbits at 2,000m. See people's teeth at the same distance.

1980's technology.

[Rippthrough]

It's a good job they aren't finished, because you could snipe better in night vision mode than you could in thermal or normal.

[Jagdt]

Matt Newman, on 22 March 2013 - 10:17 AM, said:

Ah the Joys of the Hotfix!

So as some of you have noticed the new vision modes are half implemented.What do I mean by half?
The Shader that the modes use got compiled for the patch on April 2nd and slipped into the hotfix yesterday. The other half of the Vision modes is in the rendering code that control that shader. so the vision modes you are seeing are not the final product.
Matt N

I actually liked the concept of having a black & white thermal; much more "Apache Gunship" thermal view. There are some things seriously that need to be done. The same with "Night Vision Green" ... Do you know why NVGs for INFANTRY are green?
Because they need to run on battery power. Green phosphors can put out more visible differences for less juice.

You're sitting on top of a 20 ton reactor, it's not going to grunt at 100watts for a decent thermal / nvg display.

I can drive across the river and talk to some old friends at FLIR Systems and say "Hey, this is what thermal should look like, right?"
This is how NVG should look...
http://www.flir.com/.../view/?id=59323

And this is how thermal -does- look.
http://www.flir.com/...d=639&col=55835

[Mechteric]

GranoblasticMan, on 22 March 2013 - 02:05 PM, said:

I really don't understand how a mistake like this could happen in a professional development team unless you're not using proper revision/source control.

Having worked in a "professional development" environment where we had weekly releases and the potential for hotfixes its very understandable to happen. Thing is that generally it only happens once and then the team implements something so it won't happen again (hopefully). If you've never experienced this then of course you wouldn't understand.