83 replies to this topic

[Artgathan]

Molossian Dog, on 27 November 2014 - 06:20 AM, said:

Now you are just being silly. Rear view cameras or parking assistants are lostech in 31st century.

Actually the no-rear view thing is apparently due to the fact that it would be way too costly (performance wise) to re-render the scene behind the player.

In BT Lore, pilots actually have a compressed 360 degree view displayed for them, either on a visor in their neurohelmet, or on some kind of screen. Objects at the extreme left and right of their view are actually behind them.

Edited by Artgathan, 27 November 2014 - 06:46 AM.

[Almond Brown]

Sug, on 26 November 2014 - 06:20 PM, said:

[/center]

Literally like 5 min.

So replacing one static image for another would keep everyone happy? For how long?

MoonUnitBeta, on 26 November 2014 - 06:53 PM, said:

Yeah. See. like.. I dunno.. these empty screens just makes the whole "immersion" thing and the "highest fidelity" buzz words that got tossed around back in closed beta just feel non existent. Even so, the fidelity has been reduced quite a bit. Thermal and night vision working in wacky ways, the cockpit glass is still incomplete botched. Stalker, Direwolf, Warhawk, etc walking animations don't sync correctly, and look like the mechs are constipated. I get they're heavy mechs, but what's with the bunny hops? I like the long, controlled, and dominating stride of the Atlas.
I can really nit pick, but there's definitely areas that could use another pass or polish.

Your mock up really shows how detail in the MFD's can bring life to the cockpit, and make it feel useful.

Real time data would be good. Those images are not at all useful, just different. meh.

[MoonUnitBeta]

Almond Brown, on 27 November 2014 - 06:48 AM, said:

So replacing one static image for another would keep everyone happy? For how long?



Real time data would be good. Those images are not at all useful, just different. meh.

Better some kind of random sin waves moving up and down on one monitor than 6 duplicates of AUTO-DETECT [ NO ] , or even just an orto or wireframe of the mech you're selecting
It just feels lifeless at the moment, and even if the images are not useful, they kick it up a notch

[Tarogato]

I really don't understand what's so challenging about this implementation - I haven't seen any explanation that really leaves me thinking "Oh yeah, that really is a problem..."

We have a functioning HUD. We have 3D objects in the cockpit. Why can't we just scale and move the existing HUD panels to place them over top of the monitor faces? If possible have them attached/tracked to the actual monitor, but hey, if we can't manage that and it looks wonky because the mech bobs up and down and side to side but the HUD doesn't, just explain it away with fluff and say they're actually holograms projected from the panels that are synched with the pilot's head bob via the neuro helmet.

/fixed?

If the dev answer to this is "It's not that easy" then I sure would just like to hear about why in a DevVlog at some point.

Edited by Tarogato, 27 November 2014 - 04:27 PM.