August 24, 20215 yr comment_71117 11 hours ago, Lowengrin said: Yeah, the SetPaint command is campaign specific and DCG "forgets" about it when it switches campaigns. I'd just drop the SetPaint command into the next subcampaign. Err... yes, but that is not quite what I meant. Extract from a timetable: [Burma_1942] 19421221 NewPlane 28Squadron0 HurricaneMkIIb 19421221 SetPaint 28Squadron0 = Hurricane MkIIB BR125, 3 PRU Agartala, India, Nov 1942.bmp [Burma_1942] 19440522 NewPlane 28Squadron0 Sea_HurricaneMkIId 19440522 SetPaint 28Squadron0 = Hurricane MkIIc Night fighter tail flash.bmp 19440522 SetPaint 684Squadron0 = Mosquito4PRU.bmp If I start playing from Burma 1942 I get: 28Squadron0 flying Hurricane Mk IIB (correct) using skin Hurricane MkIIB BR125, 3 PRU Agartala, India, Nov 1942.bmp (correct) No 684Squadron0 (correct) Advancing to Burma 1944: 28Squadron0 flying Sea Hurricane Mk II D (correct) using default skin (incorrect) 684Squadron0 flying Mosquito IV (correct) using skin Mosquito4PRU.bmp (correct). If I start playing from Burma 1944 I get: 28Squadron0 flying Sea Hurricane Mk II D (correct) using skin Hurricane MkIIc Night fighter tail flash.bmp (correct) 684Squadron0 flying Mosquito IV (correct) using skin Mosquito4PRU.bmp (correct). That's what I meant (I think 🤔) Report
August 24, 20215 yr Author comment_71121 It should work UNLESS the date that your campaign advances to Burma 1944 is before 19440522 and that's not an error in your timetable... [Burma_1942] 19421221 NewPlane 28Squadron0 HurricaneMkIIb 19421221 SetPaint 28Squadron0 = Hurricane MkIIB BR125, 3 PRU Agartala, India, Nov 1942.bmp [Burma_1942] Shouldn't that second [Burma_1942] be [Burma_1944]...? Report
August 24, 20215 yr comment_71127 45 minutes ago, Lowengrin said: Shouldn't that second [Burma_1942] be [Burma_1944]...? Oops, of course it should... Stupid copy-paste error while I was picking lines from the actual timetable (what's wrong with me today - I've been making errors like that all day today... 🥴) 45 minutes ago, Lowengrin said: It should work UNLESS the date that your campaign advances to Burma 1944 is before 19440522 and that's not an error in your timetable... Ok, I'll keep on testing. I may well be mistaken. Report
August 24, 20215 yr comment_71131 Paul, I'm afraid there is something fishy with the SetPaint command. I checked the advance of the real campaign I'm currently playing. The campaign files are here: https://www.mediafire.com/file/byify6ta6xpn235/Burma.rar/file The .mis files DCG created are here: https://www.mediafire.com/file/191mudqb9tm3wx7/DGen_B_Burma_1941doe0.rar/file Check the first mission after changing from Burma_1941 to Burma_1942, which would be 194212210.mis If I'm not mistaken, the skins in the 194212210.mis do not match with the skins in the timetable.dcg, nor with the skins in the Burma_1942.mis Report
November 6, 20214 yr comment_73111 On 8/24/2021 at 10:09 PM, Shakaali said: Paul, I'm afraid there is something fishy with the SetPaint command. Addition to this. I cannot make SetPaint work with AddSquad command either. From a campaign I'm working on: 19400127 AddSquad 4IAP0 19400127 NewPlane 4IAP0 I_15BIS_SKIS 19400127 MoveSquad 4IAP0 Solomanni_Airfield 19400127 ActivePlanes 4IAP0 = 16 19400127 FlightSize 4IAP0 = 4 19400127 SetPaint 4IAP0 = I-15Bis_Lt Abramov_Blank.bmp On January 27, 1940 4 IAP appers to Solomanni airfield with 16 I-15Bis skis and uses 4-plane flights. But unfortunately uses default skins. Report
November 6, 20214 yr Author comment_73113 Without debugging, I suspect it's the space in the name of the skin. Try renaming the skin's bmp and the setpaint command so the space between Lt and Abramov is an underscore. I-15Bis_Lt Abramov_Blank.bmp Report
November 7, 20214 yr comment_73114 1 hour ago, Lowengrin said: Without debugging, I suspect it's the space in the name of the skin. Try renaming the skin's bmp and the setpaint command so the space between Lt and Abramov is an underscore. I-15Bis_Lt Abramov_Blank.bmp Tested. Still no correct skins. 😧 By the way, should the order of timetable commands affect? I also tested: 19400127 SetPaint 4IAP0 = I-15Bis_Lt_Abramov_Blank.bmp 19400127 AddSquad 4IAP0 19400127 NewPlane 4IAP0 I_15BIS_SKIS 19400127 MoveSquad 4IAP0 Solomanni_Airfield 19400127 ActivePlanes 4IAP0 = 16 19400127 FlightSize 4IAP0 = 4 Still no skins, but is there a difference? Report
November 7, 20214 yr Author comment_73116 Yes, the order makes a difference here. The unit must be added before any other changes are made to it. I'm not sure why it's ignoring the paint command and I'll have to do some debugging to find out. Report
November 7, 20214 yr comment_73117 27 minutes ago, Lowengrin said: Yes, the order makes a difference here. The unit must be added before any other changes are made to it. Yes, I thought that would be logical. I just was not sure which way timetable commands are read. 🤔 29 minutes ago, Lowengrin said: I'm not sure why it's ignoring the paint command and I'll have to do some debugging to find out. Thank you. This is not very important, of course, as campaigns work perfectly with incorrect skins, too. And SetPaint works perfectly in the beginning of a campaign. It just bugs me when something does not work correctly in such a good product DCG is. Just noticed... that was your 1,000th post here 🙂 Report
November 8, 20214 yr Author comment_73147 Okay, it took me a few minutes but now I remember how SetPaint works. In the timetable file, in front of the name of the file, you have to specify whether the new skin has markings on it or whether you want the game to apply the markings by inserting a "1" or "0" before the name of the file. So the command should look something like this: 19400127 SetPaint 4IAP0 = 0I-15Bis_Lt_Abramov_Blank.bmp Report
November 9, 20214 yr comment_73152 Good grief. After a quick test it seems to work 😃 That was completely new to me. Thank you very much! Report
January 6, 20224 yr Author comment_74257 You need to look back at the previous page. Too many people have posted since I last uploaded it. (Or just click the little arrow below and to the right.) Report
July 16, 20224 yr Author comment_78289 Yes, 15 is the latest. As you may have guessed, I'm not currently working on it. I won't say I've stopped, because I'll still do bug fixes should they come up. But I'm not adding new content. Report
November 18, 20223 yr comment_80448 On 7/17/2022 at 12:36 AM, Lowengrin said: Yes, 15 is the latest. As you may have guessed, I'm not currently working on it. I won't say I've stopped, because I'll still do bug fixes should they come up. But I'm not adding new content. I don't see where to download 3.50. Report
November 18, 20223 yr Author comment_80455 The attachment is here (it had been bumped to a previous page). https://forum.jg1.org/applications/core/interface/file/attachment.php?id=4155&key=0ff7ad4e35144a702d84404b79efc103 Report
January 27, 20233 yr Author comment_81566 Hi, the link above is working for me (but only when logged into my account). Report
March 30, 20251 yr Author comment_98245 Beta 3.50 (build #16) increases the allpayload data file to 20,000 records. Report
March 31, 20251 yr Author comment_98249 Another quick update (build #17). Added an error message for cases where the upgrade for a plane type doesn't actually exist in the class.dcg data. It's very specific but was causing the dreaded '"" is not an integer error.' Edited April 1, 20251 yr by Lowengrin Removed download. Report
April 1, 20251 yr Author comment_98265 Found a bug where, when generating a new campaign, if the only friendly base is too close to the front, DCG opts not to give the player's squadron any base (so never generating a mission). This build (#18) should/maybe/might correct this issue (and/or create new ones). Edit: Build #19 is now available. Edited June 15, 20251 yr by Lowengrin Removed download. Report
April 1, 20251 yr comment_98267 2 hours ago, Lowengrin said: Found a bug where when generating a new campaign, if the only friendly base was too close to the front, DCG opted not to give the player's squadron any base (so never generating a mission). This build (#18) should/maybe/might correct this issue (and/or create new ones). IL2DCG350b18.zip 4.85 MB · 3 downloads Much appreciated ! Report
Create an account or sign in to comment