walter_solito

Thanks Lowengrin for your continue support!

Maybe is better than nothing! I'll test it on my 1932 planned Shanghai campaign for the NEW_DOF when ready....I'll report here the target results....

Thanks to both for the reply! I have thought about because I was suspecting that the recoding would be hard.... My solution , I have to test it when I'll edit the next campaign in my learning process , will be: (remember that this should be a campaign dedicated to hit and run war , so only one player squadron JG2 or JG26 on blue side 'll be active) 1) delete all enemy (red) ground objects from mission - on the target of today day: 2) use timetable command to add a set of 3/4 truck targets in the attack location 3) set that specific location as contested - on the day after: 4) use timetable command to delete the set of 3/4 truck targets 5) set the attack location again red 6) set date to the new attack date - repeat the process for all dates of the attacks.... What do you think about?

Hi! Actually I'm editing a campaign in Shanghai area in 1937....but this is valid also for all my other campaign I'm working on and for a new campaign I'm planning about the tip and run jabo attacks on Britain.... How can I set for a specific date a specific target? There is a shortcut to get such result? IIRC , when I have edited some SCW campaign , where I set some location in timetable as contested accordingly to the course of the ground war , the aerial activity wasn't strictly related to this position or area but only the frontline for sure move there.... If actually no such option could be used directly (an existing timetable command) or by shortcut , I was thinking about a specific command line like: 19370922 AirTarget Hangchou_Bay (attack generic ground targets) or 19370922 AirTarget 16_Chief (attack specific tank/colums/ships targets) This way we can not only specify a more foreseenable course of action but also introduce specific date actions.... I know that this mean work on the core code , but as Lowengrin is editing code for ships and squadrons management , maybe this could be done meanwhile on the way.... Thanks in advance for your time and your precious reply!

Thanks for your continue support and assistance with your masterpiece!

So , IIUC previously and now if not specifically placed in a patrol route to separate warships from convoy and their escort the timetable order is used , while to get ships spawn correctly in a patrol route without the routine check they have to be specifically placed in the patrol route....right?

Only to specify that all works on DCG is actually on hold due too high temperatures and continius power stoppages.....I have to avoid burn my CPU or damage my SSDs....I'll resume works after holidays when external temperatures and my internal brain could be more esily managed!

One more thought is that in the Lonestar situation the carrier isn't in a patrol zone but in a sea route.... So I caould imagine that he could test 2 options: 1) Add the carrier in the shipname.dcg file (if not done) and associate the squadron with that ship name 2) Maybe the carrier have to be added into the sea route the day before creating a dedicated pre path srd section , so the day needed it should be placed by DCG engine sailing in the next part of the srd and could receive the squadron association

Shakaali in his last campaign ( https://www.sas1946.com/main/index.php/topic,75495.msg818263.html#msg818263 ) managed to get the .mis units associated to the correct carrier with the above command line.... I have tested it and the association worked.....

So using this command I have to try set on the transfer date: 19371025 PilotType AI OLD SQUADRON 19371025 PilotType Human NEW SQUADRON Right?

Hi to all! I have no idea if could be possible to transfer the player from his unit into an already exisiting one active in the campaign. If I use the timetable command: NameSquad II_JG540 II_JG770 I get the actual unit changend into a new one but IF I need to have the player start his career with II JG.54 in a campaign where II JG.77 is anyway present and active , there is a way to move the player there while maintaining the latter unit strength (the number of planes II JG.77 actually have available on the transfer day)? Because the only solution I have studied is to have the II JG.77 removed a line before the date player unit must became it , but this way the new unit have the same aircrafts of the older II JG.54.... Thanks in advance for your help!

Hi! I'm not an expert and maybe I'm writing wrong but in my actual carrier campaign I have Shoho CV: chief.ini name: IJNHoshoCVL1936 shipnames.dcg [IJNHoshoCVL1936] CV IJN_Hosho_CVL timetable command: 19370813 MoveSquad IJN_C_Hosho_FS_VT0 IJN_Hosho_CVL The names in bolt are the same between shipnames.dcg and timetable?

Hi! I'm not out of this tread work! Actually I'm expanding the timetable section with historical facts (airfields/carrier switches , paint scheme changes , correct activation/deactivation dates....and so on) I'm posting a new tread right now about a DCG feature....

For a carrier battle you are right! For the specific campaign the carriers act against land base targets and squadrons so they have plenty of mission opportunities other than only escort or CAP....but I was also thinking about another campaign I have developed (on hold because of the work on new WAW is still in progress) about a Malta campaign from 41 to 43 where you have times to escort specific units (german Ju87/88 or italian BR.20/CANT1007 for example) and other a normal panorama of missions....

Yes that's what I was thinking about....this is why I thought that adding some delay could give an interval where the DCG engine could work.... So I try another thing: I'll restart the campaign (I have anyway in mind to do some changes at the timetable) and add the SetEscort command from the first day towards my carrier attack squadron....if I see that the escorted unit 'll remain the same for a fortnight missions (to give the DCG engine time to work on the escort conditions routine) , I'll try to change the escorted unit to another carrier attack unit to test if DCG engine 'll use the new unit or 'll keep again the older (in another fortnight of missions). If all went right and I got escort for the first only and second only unit I'll try to set the SetEscort = none and see what happen in the third fortnight: random unit escorts is good....while escort set only to last SetEscort unit is no good and mean that a interrupt escort command is needed.... Could be right this way? I'll also set the log level to the higher one to better understand what the engine is doing.... BTW as I like this campaign and I'll try to fine tune her , I'll play the most interesting missions so if all is going right with these test conditions I could take a little longer to report...but this also mean that all is going correctly with the SetEscort routine....