Jump to content

Lowengrin

Members
  • Posts

    1,115
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by Lowengrin

  1. After you generate a new campaign, are you going into the game settings and changing those settings? (What I do in this case is always load an old campaign with all the settings that I want and going to the mission screen then backing out BEFORE I start the new campaign and it captures all my game settings from the old one.)
  2. The timetable on/off only refers to the ground campaign and whether the campaign moves automatically (as per the timetable) or by the movement of ground forces. Unfortunately all the functions in the timetable are triggered by date so you're kind of hooped. I'm not sure if the code for the following commands triggers on the date in question or if it triggers even after the date has passed. You could try seeing if they trigger even if the date has passed (and then add them and remove them as necessary). 19410814 AlwaysActive True II_JG770 19410815 AlwaysActive False II_JG770 19410815 PilotType Any II_JG770 19410816 PilotType AI II_JG770 19410817 PilotType Human II_JG770
  3. The error log narrows it down to the car column routine. I'm guessing there's some math in my code that doesn't catch some bad parsing....
  4. I don't see anything obvious from the log file although it's missing information on squadrons and their missions being generated. I hope you've sorted it out since posting though. (I've been on holidays so haven't been checking the forum.)
  5. X means that it was destroyed and will respawn at a spawn point. Importing into 3.49 shouldn't cause any issues (that I can think of).
  6. No, that it's repeating is either an error in your campaign or a bug in DCG. It should be: XXX_Chief Vehicles.somevehicletype @location $NameofUnit (NameofUnit defaults to some generic thing but can be set in the timetable.dcg file.)
  7. Yes, that is possible. Did it spawn on the following mission?
  8. If you are using full auto generation and you selected your campaign through the game's menu, you do not have to exit the game and hit the DCG generate mission button. Just hit start for IL2 and it should generate it for you. (So long as you have pointed DCG to your IL-2 game folder.)
  9. You can always find the latest beta on this forum. Look for the "DCG 3.xx Open Beta Test" thread (where .xx is the version being worked on). Right now, you can find it here: http://forum.jg1.org/topic/3836-dcg-349-open-beta-test/?p=31447
  10. ~C is for "contact". The Germans are at Abbeville Bridge and the Allieds are next to them at Abbeville. And, yes, ~R is for retreating. Trains won't spawn if there's a chance they will run into another train.
  11. No, it does not. And with the information present, it's hard to say why. The dcgerror.txt might have had a clue though.
  12. Have you tried the latest 3.49 beta?
  13. That &0/&1 relates to whether radios are turned on or off. The airfields.dcg was designed prior to the radio feature so these should be deleted from any airfield flight patterns. As idefix44 has noted, the static "ships" are really test runway objects. The six types are: Ship$RwyCon Ship$RwySteel Ship$RwySteelLow Ship$RwyTransp Ship$RwyTranspWide Ship$RwyTranspSqr In your campaign, I assume the planes are tied to squadrons assigned to these runways.
  14. Hi, I have some questions for you. In your campaign template file (the mission file used to generate the campaign), do you have a static_103? If so, what is it? As for the "&0 &1", are you using the airfields.dcg file for your campaign? If so, note that it only has the first five fields/columns. If you're not using the airfields.dcg file, you may have just found a bug.
  15. That's great news. Happy flying!
  16. It is. Something else is wrong, but I have no idea what.
  17. Assuming you're advancing at a rate of one mission/day, I'd stick them in a couple days in advance just to be safe.
  18. Never? That's not intentional. I'll have a look.
  19. Did you start a campaign with a non-human flyable plane?
  20. Are you adding them on the fly? As in, adding them to the timetable at the same time you expect them to appear? For example, if the next mission will be July 8, 1942, you're putting them in the timetable.dcg after flying the July 7th mission? If so, you're too late because that mission will have already generated.
  21. If you're editing the territory.dcg through a text editor, then you need to change the allegiance as well as troop numbers. The lone number right after the name is the allegiance. 1 = Allied 2 = Axis 0 = Contested/Neutral So Gatow Airfield below is Axis controlled with 20 troops located there. Gatow_Airfield 2 allied=0 axis=20
  22. Latest beta (#14) will hopefully address the underscores in pilot names and ferries not appearing in MDS missions.
  23. It only happens with MDS missions. I'll fix it.
×
×
  • Create New...