r292 issues / bugs/ proposals

[GoogleCodeExporter]

MENU

Career Intro page
- change "Career Into" in "Career Intro" (spelling)
- pilot's name proposal (see point 1) in proposals)

Campaign Intro page
- change "Campaign Into" in "Campaign Intro" (spelling)
- redeploy screen's elements (move Back and Start buttons to their positioning 
in the rest of the screens, which is lower left/right part of the screen)

Campaign
- Campaign picking up page should be the first one (as you shouldn't be able to 
pick a side and generate a career until you won't know which sides are 
available for the campaign you want to play)

Select Airgroup
- redeploy screen's elements (move Back and Start buttons to their positioning 
in the rest of the screens, which is lower left/right part of the screen)

Battle Intro
- briefing scroll is aligned to the right of the briefing's text, inside to the 
ride of briefing text's window frame
- mission briefing.. WIP (read later after completion)
----------------------------------------------------------
BUGS

a) Press Back button from Campaign intro screen (at airgroup's selection) and 
then enter again the campaign -> the previously "created" career appears as a 
choice (even the folder wasn't created), by pressing Continue you enter in a 
broken Battle Intro screen from which you can only exit by Task Manager and 
force-closing the application

----------------------------------------------------------
PROPOSALS

1) Name generator (based on different nationalities) for a new campaign pilot's 
name (or take it randomly from a per country pilot names list) default proposal 
in Career intro Page
2) Select Army should be Select Side Axis/Ally or Germany/Britain/Italy/etc

WIP (read later after completion)

Original issue reported on code.google.com by ado...@gmail.com on 9 Oct 2011 at 7:50

[GoogleCodeExporter]

- mandatory missions -> failure them won't provide any Next button, but only a 
restart one
- use a special briefing section which is never assigned to any flight in order 
to have some DCE custom special data area for that mission (for example for the 
above mission's type)
- Skip mission button -> for generated missions players don't want to play
- Refly mission button -> for missions of which result players aren't satisfied

Original comment by ado...@gmail.com on 9 Oct 2011 at 8:38

[GoogleCodeExporter]

- support for more than a single mission in a day (using a chance % to generate 
another mission in the same day, when the battle commander AI will be ready, it 
will generate more missions in a day depending on the front situation)

There's no need to have separate SP/MP code due to the fact that the SP usually 
play only a single mission a day. simply use the MP to generate a new situation 
for the next day, then generate a mission which will be used in SP. The 
in-mission code remaining the same, AI battle commanders continuing to inject 
new flights/situations into the mission as the user is flying it (same as in 
MP).

Original comment by ado...@gmail.com on 9 Oct 2011 at 9:09

[GoogleCodeExporter]

Menu structure:

1) Careers list screen
IF there's no career found at launch, the 2) Campaigns list screen becomes the 
starting screen)
    1.a -> existing careers list (last one played is selected by default)
    1.b -> current selected career's details text area (Pilot name, Campaign name, Start date, Current Date, Missions flown, Score, some short campaign resume)
    1.c + Back button (goes back to 0) IL2CoD menu)
    1.d + New button (goes to the 2) Campaign screen)
    1.e + Delete button (deletes the currently selected career; needs a confirmation popup)
    1.f + Continue button (goes to 4) Career screen)

2) Campaigns list screen 
    2.a -> campaign templates list (first one selected by default)
    2.b -> current selected campaign details text area (geographical area, start date/end date, combatants, number of missions,difficulty, size, etc)
    2.c -> current selected campaign image area
    2.d -> current selected campaigns description text area
    2.e + Back button (goes back to 1) Careers list screen if there's any career created, or to 0) IL2CoD menu otherwise)
    2.f + Continue (goes to 3) Campaign creation screen)

3) Campaign creation Screen
    3.a -> Campaign setup area
        3.a.1a -> Select campaign's Start Date
        3.a.1b -> Select campaign's Start Date
        3.a.2 -> Select Side/Airforce (Axis/Allies ; Luftwaffe/RAF/etc)
        3.a.3 -> Select campaign type (Fighter/Fighter-Bomber/Bomber/Divebomber/etc)
        3.a.4a -> Select aircraft
        3.a.4b -> Select airfield (from Map would be awesome)
        3.a.4c -> Select airgroup
        3.a.5 -> Select Career realism (normal/extreme -> pilot's death will force the end of career; can be overwritten by 4.d.2 Reactivate button)
    3.b -> IL2DCE setup area
        3.b.1 -> forceSetOnPark
    3.b.2 -> flightSize
    3.b.3 -> flightCount
    3.b.4 -> additionalAirOperations
    3.b.5 -> additionalGroundOperations
    3.b.6 -> debug
    3.c -> Pilot area
        3.c.1 -> Select rank
        3.c.2 -> Enter Pilot name
    3.d + Back button (goes back to either 2) Campaigns list screen OR to 1) Careers list screen if there's any career created, or to 0) IL2CoD menu otherwise)
    3.e + Create button (goes to 4) Career screen)

4) Career Screen
    4.a Pilot area
        4.a.1 Pilot details text area (Pilot name, rank, missions flown, aircrafts downed/probable/damaged, ships sunk/tanks,trains,cars destroyed/bomb runs, deaths/downed/wounded times, etc)
            [4.a.1.a +Pilot details button (if the above is in form of a small resume, this button leads to a Pilot Details screen, with more details about the pilot)]
    4.b Campaign area
        4.b.1 Campaign details text area (geographical area, start date/end date, combatants, missions flown, etc)
            [4.b.1.a +Campaign details button (if the above is in form of a small resume, this button leads to a Campaign Details screen, with more details about the campaign, similar to the Campaign view from 2) Campaigns list screen)]
    4.c + Back button (goes back to 1) Careers list screen)
    4.d.1 + Reactivate (revives the pilot and marks the career as normal; ONLY appears if the career is terminated via pilot's death in extreme mode)
    4.d.2 + Fly button (goes to 5) Mission screen); ONLY appears if the career is not terminated)

5) Mission screen

Original comment by ado...@gmail.com on 9 Oct 2011 at 10:36

[GoogleCodeExporter]

5) Mission screen
    5.a Mision briefing area
        5.a.1 Briefing area
            - on sections for all available flights (as it is right now)
            - mission's general info should contain:
                    - Campaign name
                    - (career's) mission number
                    - date
                    - time
                    - [weather local]
                    - weather over target
                    - cloud ceiling
                    - wind speed
                    - airfield/location
                    - runway type (earth/concrete; short/long)
            - flight's info:
                    - flight name
                    - aircraft type
                    - callsign
                    - altitude
                    - cruising speed
            - mission's text (a few details in word regarding the mission: "We have to intercept incoming bombers", "We are requested to exort our bombers on their way to London", etc)
            - mission's info:
                    - mission's type
                    - target info (name, flak presence/density, CAP/Interception probability, etc)
                    - additional flights info (depending on mission's type: for ESCORT the callsign of escorted flight airgroup, its name, aircraft type, aircrafts number, target, flight altitude and cruising speed, etc)
            - waypoints (only relevant ones, not the current's full list; they should also be named:
                    - Take-off
                    - [Escort randezvous point]
                    - [Target]
                    - [Escort end]
                    - Landing
        5.a.2 Results area (ONLY present for older mission, does not appears if the mission viewed is the career's current mission)
    [5.b Slides area (not necessary if all the info goes into the 5.1 Mission briefing area]
    5.c Map area
    5.d + Slides button
    5.e + Map button
    5.f + Back button
    5.g + Player's Plane button (ONLY appear if the mission viewed is the career's current mission, and does not appear for any older missions)
    5.h + Skip button (ONLY appear if the mission viewed is the career's current mission, and does not appear for any older missions)
                                     (ONLY appears if the career is in normal mode, does not appear if the career is in extreme mode)
    5.i.1 + Fly button (ONLY appear if the mission viewed is the career's current mission, and does not appear for any older missions)
    5.i.2 + Refly button (ONLY appear if the mission viewed is any of the older ones, does not appear for the career's current mission)(Reflown mission results won't be registered)

Original comment by ado...@gmail.com on 9 Oct 2011 at 11:13

[GoogleCodeExporter]

This can also be modified, a little bit, for the concept of same pilot + 
multiple campaigns instead the current career one (a pilot in a campaign).

User can create pilots which can participate in various campaigns, with results 
registered for each campaign in part, and a general for the pilot's career.

At the creation of a new Campaign, the user should chose and existing pilot 
(which is alive and haven't already flown that campaign) from a available 
user's pilots list (or create one if he hadn't already before entering the 
Campaign screen).

This way, a proper pilot career across multiple campaigns can be played.

Original comment by ado...@gmail.com on 9 Oct 2011 at 11:18

[GoogleCodeExporter]

We also need an implementation of the 4. Mission Radio Comm section (at least 
in order to get info regarding the current mission's objective, and reported 
enemy/friendly flights).

Original comment by ado...@gmail.com on 9 Oct 2011 at 12:40

[GoogleCodeExporter]

for the custom Radio Comm implementation see IIIJG27 server

Original comment by ado...@gmail.com on 9 Oct 2011 at 12:44

[GoogleCodeExporter]

Original comment by il2...@googlemail.com on 11 Apr 2012 at 3:46

• Changed state: WontFix
• Added labels: Milestone-Prototype