![]() |
|
#1
|
|||
|
|||
![]() Quote:
Availability date or more general special events at a certain date are time based information and obviously can't be defined in the FMB and would require a own text file (or for better usability a calendar editor). However so far I have no idea how to combine certain events with the dynamic changing front-line. But this is stuff for the advanced user. |
#2
|
|||
|
|||
![]()
Quite honestly the idea of stuffing most things into the template was proven insufficient by DGen years ago. It was not flexible enough to depict changes of aircraft types (i.e. the switch from Bf 109 to Fw 190 within a sub-campaign, not between two of them) or sudden transfers to other locations for reasons you as a player had no control over, a thing which later happened so frequently (i.e. transfer of parts of Fliegerkorps VIII from Kharkov to Orel during Citadel).
I, personally, believe that only certain things should be defined on the template: - airbase locations (i.e. deactivating air bases which weren't in use at a certain time) - major railway lines (= primary supply lines) - major railyards - if applicable shipping lines (= major supply lines) - major roads (= secondary supply lines) - major harbour installations - minor harbour installations - bridges (weak spots of supply lines) [ - Army Group or Army Level Supply Dump location(s) ] ... basically all things that are mostly static or cannot be moved somewhere else. Anything that is mobile or even semi-mobile should be defined in another file. I mean I am a rivet counter when it comes to historical details and I would invest considerable time into adding such details. But not everyone would do the same and I understand that. But if you cram all such things into the template and don't use external files you're automatically limiting the amount of historical details, accuracy and flexibility your tool can generate. |
#3
|
|||
|
|||
![]() Quote:
I agree it would be practicable to define the locations of cities, rail yards and harbors for every map (the default definition can be overwritten by every campaign). But this would be a "map template" (location of map characteristics) opposed to a "campaign template" (location of units). I still have some problems with adding "scripted events", of course I can define that unit x was transferred to airfield y at date z. However, what happens if airfield y is already in enemy territory? We see that "events" won't work in combination with a dynamic frontline. Of course a dynamic frontline is not desired if you want to create a historical campaign. So basically if you want to create a historical campaign you want to define the frontline and location of air units and maybe even for ground units. I don't think you want to define that for every day but let's say for every week. Between these dates the frontline may develop dynamically. But what happens if a unit is destroyed? Will it reappear with the next define situation? I think it would be very possible to add "reinforcement events" to a dynamic campaign that define which air or ground units become available at a certain time. It may be even possible to define a "preferred location" for them that is used if it is in friendly territory. It would be cool to add some "special events" where a scripted mission is loaded, e.g. to stage a scripted paratrooper operation or a key assault. But then again this would produced problems with the dynamic front line. One solution for the front line dilemma would be to link the events to the front situation, i.e. they only happen if the corresponding area is still in own hands. Last edited by 41Sqn_Banks; 04-03-2012 at 06:46 AM. |
#4
|
|||
|
|||
![]() Quote:
Quote:
Quote:
|
#5
|
|||
|
|||
![]() Quote:
If looses are dynamic but front line is static there could be a situation that one side has lost all ground units but still the front line doesn't move. Or a vital air unit can't operate anymore because it lost all aircraft in a unlucky operation. How to have static locations/transfers of air units of the front line moves dynamic? In addition it's not possible to simulate the whole ground war in detail for performance reasons. As far as I can see at the moment the only practicable way would be to have a scripted definition of the exact locations of air and ground units for certain dates, e.g. 1 August 1940, 7 August 1940 and 14 August 1940. Between those dates everything happens dynamic, but when one of the dates is reached the scripted definition is applied and basically resets the dynamic changes to the ones defined for the date. The only exception could be the squadron of the player where looses and experience of the squadron mates remains throughout the campaign. This would result in a basically static campaign progress with randomized missions and dynamic development of the own unit. Last edited by 41Sqn_Banks; 04-03-2012 at 09:03 AM. |
#6
|
|||
|
|||
![]()
I took some time to really think about this but quite honestly all I can offer is an opinion and some snippets.
Quote:
Quote:
Historically ground warfare was heavily dependant on different sets of factors such as training, doctrine, Command&Control, Communication and whether one side was on the strategic offense or defense. The Red Army of 1941 was numerically powerful but totally unprepared for the Blitzkrieg style of war practiced by the Wehrmacht. The germans won a lot of battles not through firepower but through coordination, movement and training. We can't simulate those advantages in a flight sim ... Which in turn means the impact of a player should be confined to the location he is in and the timetable for the advance/retreat could be shifted only minimally. Quote:
1.) A unit may have lost too many aircraft and/or its crew is suffering from fatigue so RAF FC may decide to move it to a secure location to recuperate and bring a fresh squadron to the battle area. Same goes for the LW. 2.) The LW may want to concentrate certain assets in one area for increased impact on operations, just as it happened to the fighter units which were concentrated in the Pas-de-Calais area in August/September 1940. |
#7
|
|||
|
|||
![]()
Dev update. I will host a test server that runs the latest build in a few days. The server will not run 24/7 but for a couple of hours on maybe some days a week.
I have not decided yet if I will include spawn points or instead run a coop script that allows selection of AI aircraft. |
![]() |
Thread Tools | |
Display Modes | |
|
|