LOL exceeding G-force limit

That was actually more or less a bug believe it or not ;). The effect was nice, but what was actually causing it was the massive accelerations feeding unexpected values into the camera shake/bob model making it go haywire. Which in itself is entirely reasonable (and I'd have left it in) but the same unexpected values in different situations caused a load of transition errors and nasty camera motion - which we fixed at some point. It's on my personal wishlist to re-add correctly way down the line, but there's far more important tasks ahead of it in the queue.

Fair enough, glad it's on the list to reintroduce! It should add to the realism around blackholes and larger/dense stars as well, looking forward to it :)
 
I actually managed to blackout 1 or 2 times in my vulture doing some intense dogfighting, haven't managed it in any other ship though.

Collision blackout seems like a really nice idea though, would make people thing twice before ramming something as it temporarily immobilizes them.
 
Any chance to redouts and blackouts be a bit more prominent in future Mark? It could add nice tension when pulling off complex turns while targeting enemy/avoiding fire.
 
Heh, yeah - we actually started out fairly realistic in that aspect, with limits of -4 to +9 vertical G and about 5g lateral (assuming good neck bracing). Quickly realised that those limits crippled any fast manouvres though, and yes ramming someone almost guaranteed a double blackout :p. I forgot to turn off those limits first time I was experimenting with supercruise actually, as soon as I touched the controls the pilot blacked out for about a minute as the g-forces went high enough to liquify metal! Oops....

Oh god lol
 
OK, now can someone tell me what exact moves do I need to make in my Vulture to get those effects? ;)

Redouts are caused by negative G's which mean that you "dive" or go down (in space of course, this is fully relative to your ship orientation only, no other factors).

Blackouts (technically greyouts until you pass out fully) are caused by positive G's which mean you "climb" or go up (again, relative to your own ship only).

The thing that actually causes them is blood rushing into (redout) or out of (greyout) the brain. The way to understand it is you are doing a loop with your ship. Now as with a ball on a string being spun around, stuff wants to fly out of the loop, and continue moving straight, and is only restrained by whatever acts to hold it on place, in the ball example, the string tied to it. In the ship, we are concerned with your blood, and your body. If you do a loop pulling "up" your brain is on the inside of the loop, and the blood wants to get the hell out of there, so it pools in the arms, legs, and body, so there is less left for the brain, causing a decrease in function thanks to hypoxia, causing a greyout, and eventually, blackout. In a loop going "down" your brain is on the outside of the loop. This means that blood is forced into it, and this can cause reddening of the vision, and also worse things at serious -g's, like your eyes bursting, or stroke.

We have the capability today of reducing the effects of greyout by using an Anti G-suit, which is essentially a suit that has valves that let the plane inflate bladders in the suit in proportion to the G's experienced, which does not allow as much blood to pool in the extremities (in addition to the pilots using their own body to fight the G's, by tensing up), meaning there is more blood to keep the brain oxygenated, resulting in better tolerance of G-forces. There is no such system for preventing redout, however, as it's kind of hard to crush the pilot's skull to force blood out without murdering them.


So in your vulture, full pips to A engines, and do a "dive" loop to get a redout (which is easier) and then do a "climb" loop to get a greyout (which might be beyond the ship's capabilities with the raised limits as mentioned by the dev earlier in the thread).
 
Last edited:
I personally don't like the red-out thingy. I mean sure it's cool when you accelerate/decelerate too fast during combat but ...c'mon...going from 1c to 20c in seconds and nothing happens? I don't see why performance enhancers would work in SC but not in normal cruise =P. Unless there is some sort of space magic explanation to this?
 
Heh, yeah - we actually started out fairly realistic in that aspect, with limits of -4 to +9 vertical G and about 5g lateral (assuming good neck bracing). Quickly realised that those limits crippled any fast manouvres though, and yes ramming someone almost guaranteed a double blackout :p. I forgot to turn off those limits first time I was experimenting with supercruise actually, as soon as I touched the controls the pilot blacked out for about a minute as the g-forces went high enough to liquify metal! Oops....

Why I could see that being an Lore Story about the first FSD test pilot's fate
 
Mark, was the 'bumpiness' of SC toned down after Beta? I remember it feeling like a lot rougher ride initially, but I can't tell if it has been smoothed out in release it if I've gotten used to it.
 
Every time I see someone comment on that effect it makes me giggle a little inside...

Geforce effects was something we had internally in the early alphas but was never really meant to be released - we pushed the limits out to where ships of the time couldn't trigger it and then forgot entirely until faster ships and flight model changes made it attainable again... debug colour-overlay and all. We could remove it but it's become an accidental feature I guess :).

For anyone interested the current limits are 18 negative G to start a red-out and 25 positive G to start a blackout, if you hold it for 4 seconds above that limit you'll lose control. Sustained for a while that would not to good things to a human body/brain!

DON'T REMOVE IT! Actually we need to tweak it a bit.
 
Last edited:

Mu77ley

Volunteer Moderator
I personally don't like the red-out thingy. I mean sure it's cool when you accelerate/decelerate too fast during combat but ...c'mon...going from 1c to 20c in seconds and nothing happens? I don't see why performance enhancers would work in SC but not in normal cruise =P. Unless there is some sort of space magic explanation to this?

That's because the Frameshift drive works by compressing spacetime in front of the craft and expanding it behind. Your ship technically never exceeds c (because that's impossible).

A little light reading: https://en.wikipedia.org/wiki/Alcubierre_drive
 
Every time I see someone comment on that effect it makes me giggle a little inside...

Geforce effects was something we had internally in the early alphas but was never really meant to be released - we pushed the limits out to where ships of the time couldn't trigger it and then forgot entirely until faster ships and flight model changes made it attainable again... debug colour-overlay and all. We could remove it but it's become an accidental feature I guess :).

For anyone interested the current limits are 18 negative G to start a red-out and 25 positive G to start a blackout, if you hold it for 4 seconds above that limit you'll lose control. Sustained for a while that would not to good things to a human body/brain!
Got a bit of Red Out in a dogfight the other day, also once during an emergency drop from SC. Nice to see it, as long as it isn't over-done I think it is worth keeping both effects in the game and revisiting later to possibly enhance/tweak.
 
Every time I see someone comment on that effect it makes me giggle a little inside...

Geforce effects was something we had internally in the early alphas but was never really meant to be released - we pushed the limits out to where ships of the time couldn't trigger it and then forgot entirely until faster ships and flight model changes made it attainable again... debug colour-overlay and all. We could remove it but it's become an accidental feature I guess :).

For anyone interested the current limits are 18 negative G to start a red-out and 25 positive G to start a blackout, if you hold it for 4 seconds above that limit you'll lose control. Sustained for a while that would not to good things to a human body/brain!

Er.. Unless I am hallucinating I remember it being clearly stated by someone at FD that blackout was meant to be another game system we'd be expected to manage. It is news to me it wasn't meant to be released. Pity.

I think it could make for a very cool feature especially if we consider possibilities such as character avatars, equipment: i.e space (g) suits, and planetary atmospheric game-play. Right now I can flip ships and do all sorts of crazy moves without any other consideration, if we did have to manage g-force (allowing for good gameplay) it could add another layer of depth to the game and further add to the system of piloting skill.

Could be interesting ;)
 
Last edited:
I agree with all the other posters here. Would be nice if this was a more integrated feature. Collisions. Super Cruise. Gravitational fields. Anything with rapid accelerations should induce biofeedback. The human bodies seem a little too robust and aloof in ED. The game could use more immersion. Very glad to hear that the framework for this is already in place.
 
I personally don't like the red-out thingy. I mean sure it's cool when you accelerate/decelerate too fast during combat but ...c'mon...going from 1c to 20c in seconds and nothing happens? I don't see why performance enhancers would work in SC but not in normal cruise =P. Unless there is some sort of space magic explanation to this?

I understand that SC is 'squashing' spacetime so that you have less space to pass through. To go faster in SC the ship squashes space even more so there is even less space to go through. The speed the ship is traveling is the same speed as when it entered SC (I guess around 200-300m/s based on most ships). In effect the ship doesn't go faster, you are just reducing the amount of distance you need to travel to get to your destination.

This is just how I understand SC from what I remember reading ages ago so that could all be hogwash!

-edit-
I calculated how much G force there is when my Python accelerates. Takes about 10 seconds to get from 0 - 252m/s and equates to about 3.5G :)
 
Last edited:
Back
Top Bottom