Ka-50 test

[press]

Has anyone thought what would happen with the helicopter if you keep the Black Shark (I mean the game/program/simulation) running for let`s say 1-2-3 weeks or more? And in this period fly each day 1-2 hours and after you end the flight don't shut down the program, just leave the simulation running with the helicopter powered off on the platform.

I`m thinking that if the program simulates so many systems and their interaction with the surrounding environment, keeping the simulation going on for a long period of time, the helicopter might behave like a real machine. In time different system might fail.

Has anyone tried this? What are the devs thinking about this? Could this happen?

 

I would try it, but my BS is on my lappy and I cannot keep it on for that long period of time.

[Distiler]

Can't happen if you haven't setup timed failures in the mission editor. The most you'll get is a mission crash due memory usage XD

[zdXu]

Can't happen if you haven't setup timed failures in the mission editor. The most you'll get is a mission crash due memory usage XD

 

What about if you just pause the game during a mission for 8 or so hours? Is this also not possible?

[sobek]

Can't happen if you haven't setup timed failures in the mission editor. The most you'll get is a mission crash due memory usage XD

 

Not true, AFAIK engine wear is modelled, so if you run the engine in takeoff setting for prolonged periods, the power will degrade and eventually the engine will fail.

[press]

Can't happen if you haven't setup timed failures in the mission editor. The most you'll get is a mission crash due memory usage XD

 

 

Let's assume we have a super computer.

 

What about if you just pause the game during a mission for 8 or so hours? Is this also not possible?

 

No pause.

[EtherealN]

Let's assume we have a super computer.

 

Irrelevant. It's a 32-bit application: the process only has some 2GB of adress space. You either have the adress space, or you don't.

[ericinexile]

Has anyone thought what would happen with the helicopter if you keep the Black Shark (I mean the game/program/simulation) running for let`s say 1-2-3 weeks or more? And in this period fly each day 1-2 hours and after you end the flight don't shut down the program, just leave the simulation running with the helicopter powered off on the platform.

I`m thinking that if the program simulates so many systems and their interaction with the surrounding environment, keeping the simulation going on for a long period of time, the helicopter might behave like a real machine. In time different system might fail.

Has anyone tried this? What are the devs thinking about this? Could this happen?

 

I would try it, but my BS is on my lappy and I cannot keep it on for that long period of time.

 

Come on! Really!? It's one thing to appreciate the realism that the Devs have built into DCS. But let's not get girly over the brilliance and sophistication of the simulation. Much is still scripted (the ABRIS boot sequence, for instance). DCS is complex enough without wasting time math-munching gearbox oil viscosity loss over time, turbine blade dust nicks, and seat cushion sweaty-butt compression.

[wickedpenguin]

Maybe someone can conjure up a mod that tracks your flight time through campaign and online play. Something like an airplane's HOBBS meter. The more hours you play, the more chance of a failure in the systems.

 

I'm not talking a huge chance, but let's say for every 20 or 30 hours of play your chance of an engine or system failure increases by 1% or 2%. You will have an option to "perform maintenance" after, say, one hundred hours.

 

When you crash - and therefore get a new helo - the meter gets reset to zero.

[JG14_Smil]

I like that idea wickedpenguin.

[deltatango]

Maybe someone can conjure up a mod that tracks your flight time through campaign and online play. Something like an airplane's HOBBS meter. The more hours you play, the more chance of a failure in the systems.

 

I'm not talking a huge chance, but let's say for every 20 or 30 hours of play your chance of an engine or system failure increases by 1% or 2%. You will have an option to "perform maintenance" after, say, one hundred hours.

 

When you crash - and therefore get a new helo - the meter gets reset to zero.

 

It's not a new idea. But it is a good idea.

 

Aeroworx KingAir for MS FS9

 

http://www.aeroworx.com/b200.html

 

"To add to the realism, the B200 has realistically animated wipers, control surfaces, and an aircraft maintenance module that monitors engine hours, airframe hours, oil usage, tire wear, engine wear, and prop wear.

 

The pilot can replace/repair engines (when damaged by hot-start), props, engine oil, tires, gear and flaps (gear and flaps are damaged if extension/retraction speeds are exceeded) via the maintenance module. "

 

Aerosoft's Dornier DO-27 for MS FSX

 

http://www.flight1.com/products.asp?product=DO-27

 

"- Panels and instruments may be damaged by hard landings.

- All circuit breakers work.

- Instruments are affected by flight conditions; the panel may vibrate, instrument needles may be influenced by vibrations, g-forces, or other disorders.

- Engine and gear can get damaged by a number of factors.

- The flight model is affected by a number of different conditions - so it means you must pay attention in Pro mode.

- Structure and controls can get damaged through high speeds and extreme maneuvers.

- Windows get dirty."

[Total]

Your pilot would short circuit the electronics in the helicopter cuz a person can't sit in there that long without having to take a leak eventually :D

[Panzertard]

...

 

I'm not talking a huge chance, but let's say for every 20 or 30 hours of play your chance of an engine or system failure increases by 1% or 2%. You will have an option to "perform maintenance" after, say, one hundred hours.

 

When you crash - and therefore get a new helo - the meter gets reset to zero.

 

Moore's law and my own skills take care of that. I dont need a mod to crash ... :cry:

Edited June 23, 2009 by Panzertard

[-Bazong-]

Maybe someone can conjure up a mod that tracks your flight time through campaign and online play. Something like an airplane's HOBBS meter. The more hours you play, the more chance of a failure in the systems.

 

I'm not talking a huge chance, but let's say for every 20 or 30 hours of play your chance of an engine or system failure increases by 1% or 2%. You will have an option to "perform maintenance" after, say, one hundred hours.

 

When you crash - and therefore get a new helo - the meter gets reset to zero.

 

I also thinks this is would be a great feature!! :)

[Feuerfalke]

Irrelevant. It's a 32-bit application: the process only has some 2GB of adress space. You either have the adress space, or you don't.

 

Well, technically this is right, but it's still not the full story.

 

I have upgraded my gfx-card to a GTX 285 2GB. Together with my current 4GB memory, BS states in the ingame stats, that it is using 3.5 GB of RAM. (Vista64bit)

 

Preloading takes some time, but almost no loading during flight.

[hilikusopus]

DCS is complex enough without wasting time math-munching gearbox oil viscosity loss over time, turbine blade dust nicks, and seat cushion sweaty-butt compression.

 

:megalol: