SUBSIM Radio Room Forums - View Single Post

emsoy · 07-10-14, 12:10 AM

Think the solution will probably be something like this...

The JAS 39 Gripen will have a 6 hr normal turnaround. But the scenario author can activate 'quick turnaround' in his scenario if it makes sense to do so. Some (but far from all!) loadouts in the platforms database will be 'quick turnaround' capable, typically simpler A/G loadouts on tactical jets. Bomber loadouts, cruise missile loadouts, etc will never be in this category.

Then, if the player decides to use 'quick turnaround', the plane can fly 4 sorties with 25 minute turnaround. But once the plane stands down it will be out of action for a prolonged period of time, probably 36-48 hours. The exact number of missions, the turnaround time and the penalties will be set for each loadout in the database. So no in-code 'one rule' implementation.

This should solve the problem I think?

07-10-14, 12:10 AM	#25
emsoy Loader Join Date: Nov 2003 Posts: 81 Downloads: 4 Uploads: 0	Think the solution will probably be something like this... The JAS 39 Gripen will have a 6 hr normal turnaround. But the scenario author can activate 'quick turnaround' in his scenario if it makes sense to do so. Some (but far from all!) loadouts in the platforms database will be 'quick turnaround' capable, typically simpler A/G loadouts on tactical jets. Bomber loadouts, cruise missile loadouts, etc will never be in this category. Then, if the player decides to use 'quick turnaround', the plane can fly 4 sorties with 25 minute turnaround. But once the plane stands down it will be out of action for a prolonged period of time, probably 36-48 hours. The exact number of missions, the turnaround time and the penalties will be set for each loadout in the database. So no in-code 'one rule' implementation. This should solve the problem I think? __________________ Database guru, sensor model developer, system tester and senior scenario designer in the "Command: Modern Air/Naval Operations" project!