An ideia for a new version of deltaglider

[lmarioan]

Hello everyone!

Ive been reading all the posts, and come up with an ideia that i like to share with you...
something to make the Eva experience a necessary and interesting thing, and not just a fun thing (or dull):

It would be interesting having an astronaut docking in some point of the ship exterior just to solve a malfunction!
Im not expert in programming but the process should go like this:
- The main code of the DGIII, randomly create a malfunction (ex: O2, Fuel leak and engine malfunction)
- Time warp would come to normal instantly, and the alarm would sound, o2 or fuel start to leak
- You would have to open a door in the outside of the ship ( a diferent one depending on the problem)
- Go EVA and Dock with the ship in that precise place (should be a normal vessel to vessel docking)
- A counting from 0 to 100% should start (the man was working...)
- And then problem solved, get back to ship and continue the voyage!

What do you think?

This would self generate an objective, no need to be always creating scenarios to make sense of things...
The malfunction generator could even response to reentrie temperature, burning time, and other things that the ship
had done, to increase or decrease malfunction probability!

[Schimz]

What do you think?

LOL, I think you read my mind ! I have thinking of that this week !

[reekchaa]

Sounds Brilliant.  The idea of random failures has been tossed around before, and Dan has teased about
implementing them at some point, but describing it in the way that you just have, or even allowing some level of
scripting in the .SCN or a .CFG file... these things would greatly enhance any custom scenario design.  
 (ie: "Draining Fuel/Oxygen Leak... You have 2 minutes to fix system before depletion" )

One possible problem is that when you currently get too close to any ship, the Z-buffer depth starts 'clipping' the
geometry... putting you inside the craft by the time you reach it.  With a fixed external camera though, this is avoided.

[lmarioan]

The docking point coud be some centimeter away from the ship, to avoid that.
Remember the man is not "docked", (he is docked only in a code functional way), but for us, he is just floating in front
of the panel.

I had this ideia, because i think that there must be objectives! "need to do", problems to solve and feel happy about
it!
Orbiter is so incredible! but lacks of it! So i would not worry much about seing that kind of "bugs", if i new that i
was "really"doing something.

[Evan]

I Like It!! Although I Think You Should Be Able To Have A Check Box Of Failures We Want To Occur, We Check THe
Ones We Want, And The Computer Randomly Chooses From those.

[DanSteph]

lmarioan a écrit:
It would be interesting having an astronaut docking in some point of the ship exterior just to solve a malfunction!
Im not expert in programming but the process should go like this:

this is an idea that float in the air since almost two years...
My idea was to simply detect the presence of the guy near
an area for exemple rear engine and start a bar counter...
when 100% repaired. (no need of docking)

I would make door to give acces to different "visit" area of the ship:
you can open door that cover the engine to see them, etc etc
and different technicals part.

Once failure triggered, you open that part, go near with your mmu
and wait the status bar to complete. This simulate your work.

Anyway before jumping everywhere : I don't think I'll do it for several reasons.

beside the technical problems (low) and "story board" problems (failure should not be boring or annoying)
the main problem for me is now time: I work on four project
in same time and and also on my professional work... this is already much work !

Dan



Message modifié ( 21-10-2006 22:12 )

[Simonpro]

Open source!

(runs away)

[DanSteph]

Sorry ? to far I didn't hear

About Failure the main problem is: I've succeded to add failure that are intteresting
and give a real challenge in my addon FsPassengers, it required 70'000 lines of codes
14 month of work and hundred sounds. (not all dedicated to failure it's true)

A motor that break first time it's funny... second time it's just boring...
one need flight reports, a career,something to gain or loose to render
this intteresting.

Without challenge no fun, therefore something that simply brake without
any consequence possible gain or risk is simply boring once the first suprise done,
thus it would be a useless work jnot as much fun as peoples imagine.

That's the main reason in fact... gameplay.

It would require a complete game behind and this is out of scope of
a freeware add-ons.

But just for eyes candy I might do something once with the repair idea,
technical door, eva etc etc...

Dan

[lmarioan]

You dont have time, and we are always wanting more...
Thats the price of success! You do something amazing, next time your fans want something even better!
You will become a slave of this! 8)

But, i dont think that a motor breaking a second time would be boring... if so we would select "no failures" in the DG
setup.

A diferent way of looking to this could be:
If we land with too much wheight the landing gear breaks, and for now thats the end of the game! This would be a
good excuse to go eva and repair the result of our stupidity! hehe.
So, if you could make malfunction come from our errors, it would be our fault having to eva for repairs...

[DanSteph]

What people don't think about is:

each failure require that you plan all the case and with the appropriate feedback.

One can't broke an engine 10 meter over landing in hover mode, it would be unfair for example.
So first you must make a sort of IA that will decide to set a failure at an intteresting moment.

Second you must test all the case, the guy don't EVA the guy EVA but fail, the guy EVA
but do stupid things with feedback also "What ARE you doing ... go repair NOW" or
the guy will not see what he must do and sit here (unless he read the doc...and who do that ?)

Third you must give accurate feedback... (if you must cheer yourself you can also imagine that your engine is broken
And this for every case....

So I can do failure in one line and it would require 2 minutes:
if(rnd()<0.5) SetEngineFailure

4 line more and you'll have repair :
if(5mnorverarea) SetFailureOff

But such things would be boring... how people imagine it,
it's the first case and this one require a lot of work...

And as said the second or third time without a challenge, something
to gain or loose it would simply be boring. Thus you must plan more failures
to keep the intterest... back to the top of post and back to bottom of post
once all failures experienced. Simply an anoying things that never brake
when you expect, or during a nice and vital manoeuver that make you
loose completely your flight.

Anyway I'll try my best to keep the pleasure high

Dan



Message modifié ( 22-10-2006 03:09 )

[DocHoliday]

Smells like FSPassengers.

Do we get to pay for repairs and earn money with space tourism too? :D And listen to them scream during reentry!

[Cairan]

...yeah and a nice bacon sizzle sound when you let her warm too much during said reentry!