The ongoing JG42 war

[Nephris]

Next session begins tomorrow evening at 20h MET as usual.
The supply deliveries from home have been completed.
Snow didnt melt up to now.
The desired plane transfers from 25.3 list have been done .
The static bomber at Balabanovo was deleted to prevent crashes.
Time should be set at 11h ... I hope.

Did I forget anything else to mention?

See ya tomorrow in the skies above Moshaisk,Uvarovka,Yukhnov or Volokolamsk.




.

[:FI:Blue2]

It all sounds & looks good from what I can tell, Nephris. Thanks for the transfers! I notice your side was resupplied with some Hs-129s too - a new opponent for us huh?
Hopefully the AI won't be too badly affected, and maybe we will all learn something by trying these manual transfers for a bit.
Couple of questions...
1) Now that we have made manual transfers, if our side loses ground in a mission, do we need to ask you to transfer any squadrons now too close to the front line (i.e. less than 2 transport points) to keep them from being captured?
2) Airfield in N3: is it usable for the campaign? I notice it has no transport points running by it. All the others currently in use have transport points beside them.

[Nephris]

I notice your side was resupplied with some Hs-129s too - a new opponent for us huh?

Yes, beware of the flash, it maybe already too late then
The HS129 is actually a bit too early, as just 3 or 4 machines were used/tested while early spring 1942.
At all,we are using a bit to late build planes for an early 1942 campaign, as the P40E was a 1943 build, the Yak1b came in late 1942 (modded Yak1bEarly caused probs again at spawnpoints like the Ju52 did),the Pe2 Serie84 was delivered in early 1943 to the front....but at the end we need to manage gameplay,historic facts,fun and balancing in one, as Red planes of 1941 or early 1942 are fairly underpowered compared to Blue planes of that age. To keep fun on a leveled plane base we chose that compromise by sacrifising the absolute historical correctness.I hope most of the pilots can deal with it.

So Blue asked for a more efficient tank fighter,like the Il2 with its arsenal of weapons like rockets,AOs, AJs etc, which can wipe a complete tank company at once. I considered the BF110G2 which could also use a 37mm canon but the guys liked to play with a new 4.10 patch plane...although the BF110G2 would be a pendant to the Pe2-84 . So I think the HS129 is a good compromise, as I wouldnt count it as typical threat .... each Il2 will win a dogfight against it.

After all a pilot skill ends a dogfight.

1) Now that we have made manual transfers, if our side loses ground in a mission, do we need to ask you to transfer any squadrons now too close to the front line (i.e. less than 2 transport points) to keep them from being captured?

I turned the option "No transfer" off, so the DCG will imho do the job itself,as it sometimes will also transfers the squadrons ( each AI squadron = available plane type) within the mission, if DCG considers new tasks for an AI squadron in a next mission. A few missions left and we will be smarter in this point.
At first,letz keep an eye on airfields that get threatened to be sure keeping your squadrons ingame

2) Airfield in N3: is it usable for the campaign? I notice it has no transport points running by it. All the others currently in use have transport points beside them.

That airfield isnt connected/integretated to the road system of the campaign, so it cant be used, sry.

[Nephris]

Good evening Gentlemen,

first off I am sorry for todays´chaos, seems like i f***ed the Server Installation.
So we had to play the war on my listenserver, without a tool that counts or punishs
plane limits or the time. That was the reason why we had that much Bf109 F4 in air,
which actually would have been highly decimated after the first mission and we would have flown Bf109E downgrade versions on a Il2SC commanded dedicated envirenment, I didnt count red fighter losses either.

Using the listen server instead also meant, I wasnt able to import your desired transfers today, which must look like sabotage to red war plans . Even more after I tested the mission tuesday or wednesday ...
I set up a new server and things will be fine again ,not forgetting the new transfer list, I am sure there will be some airfields again, you would like to nest in again

I felt sorry for Frank, after he got shot while landing...seriously it wasnt me ... but I know who it was.....
I guess he smelled his first online kill ever, in an easy looking sitting duck. Not a fair gameplay anyways.


Hope you enjoyed ya stay nevertheless. I expected and hoped a few pilots of Java1 would support you, today you ve been outnumbered since a long time. Well maybe the dutch m8s will join next time.

Both sides did well this time.
Red claimed north and south
and Ruza Airfield again aswell.
Blue took parts in the middle
About time for a devastating hit.
ffs this reads like poem...


The map and the single stats are up2date.
Find the thread in our forum via my sig.

Today I tested the stats tool (written in C# or C++) and its first ouput (counting kills).The framework seems to be done
right now it "just" needs to be filled by queries.


Check a small example.
It counts the total Air kills (human + AI) between 19.1.42-05.03.42 (16 missionsh). The coop mission we flew first havent been regarded in this list.
The tool is still alpha and the sceenshot just represents that progress is made behind the doors
Groundkills querie hasnt been activated yet, just the table is prepared.
Right now more queries need to be filled into the framework.

edit:
I did a small "Picasso" representing the road system, troops can use.
Maybe you can get some usefull info of it.


click on image to enlarge

[:FI:Armitage]

Can troops use all rail networks?

[Nephris]

Troops can be un/loaded into trains at locations with a rail station, like Volokolamsk - Volokolamsk_Station.
I updated the map with the rail stations and thus possible load/unload locations.

edit: map updated with used rail system

[:FI:Armitage]

So there are only two railways in operation even though there are many other rail links?

[Nephris]

Well, the northern railways from Nakhabino to Rhzev is working with 7 stations. A train can move just from one to the next station per mission.
The central railways from Lesnoy Gorodok to Vyazma is working with 7 stations.


In current frontline situation blue is able to un/load at 7 stations Rhzev,Zubstov,Pogo..Gorodische and Vyazma_Depot,Vyazma,at the bridge near Ghatzk (forgot the location name) and Uvarovka. Red can un/load in Shahovskaya,Chismena,Novopetrovskoye,Istra and Nakhabino_Depot.

I didnt consider the southern railways. Maybe I can add it, when we change to summer season.

[Nephris]

I just noticed the debriefing in DCG folder of last flown mission, created by DCG, mabe you are interested in it
You can check it usually on the server too, when you are still neutral imho and I didnt forget to set the mark for online debriefing.

Code: Select all

Debrief: 
 
Mission results:
Oberfeldwebel BC Graf Zahl destroyed a tank for his 1st ground target.
Oberfeldwebel BC Graf Zahl destroyed a tank for his 2nd ground target.
Oberfeldwebel Wolf destroyed a stationary object for his 1st ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 3rd ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 4th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 5th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 6th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 7th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 8th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 9th ground target.
Oberfeldwebel BC Graf Zahl was shot down.
Oberfeldwebel Wolf destroyed a tank for his 2nd ground target.
Oberfeldwebel Wolf shot down an IL-2 Series 3 to score his 1st victory.
Oberfeldwebel Nephris bailed out.
Oberfeldwebel Nephris was shot down.
Mladshiy Leitenant =FI=Mikester shot down a Bf-109F-4 to score his 1st victory.
Mladshiy Leitenant =FI=Genosse was shot down.
Oberfeldwebel Wolf shot down a P-39D1 Airacobra to score his 2nd victory.
Oberfeldwebel Roter-Loewe destroyed a vehicle for his 1st ground target.
Oberfeldwebel Roter-Loewe destroyed a vehicle for his 2nd ground target.
Oberfeldwebel Emse bailed out.
Oberfeldwebel Emse was shot down.
Mladshiy Leitenant =FI=Mikester shot down a Bf-109F-4 to score his 2nd victory.
Mladshiy Leitenant =FI=Armitage was shot down.
Oberfeldwebel chaos shot down an IL-2 Series 3 to score his 1st victory.
Oberfeldwebel chaos was shot down.
Mladshiy Leitenant =FI=Mikester shot down a Bf-109F-4 to score his 3rd victory.
Oberfeldwebel StG2 Juuti destroyed a tank for his 1st ground target.
Oberfeldwebel StG2 Juuti destroyed a tank for his 2nd ground target.
Oberfeldwebel StG2 Juuti destroyed a tank for his 3rd ground target.
Oberfeldwebel StG2 Juuti destroyed a tank for his 4th ground target.
Oberfeldwebel StG2 Juuti destroyed a tank for his 5th ground target.
Oberfeldwebel StG2 Juuti destroyed a tank for his 6th ground target.
Oberfeldwebel StG2 Juuti destroyed a tank for his 7th ground target.
Oberfeldwebel StG2 Juuti was shot down.
Oberfeldwebel EJGr.Ost Caspar bailed out.
Mladshiy Leitenant =FI=Mikester bailed out.
Oberfeldwebel EJGr.Ost Caspar was shot down.
Mladshiy Leitenant =FI=Mikester was shot down.
Oberfeldwebel Wolf shot down a P-39D1 Airacobra to score his 3rd victory.
Oberfeldwebel Wolf was shot down.
Mladshiy Leitenant McB shot down a Bf-109F-4 to score his 1st victory.
Oberfeldwebel chaos destroyed a tank for his 1st ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 10th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 11th ground target.
Oberfeldwebel StG2 Juuti shot down a LaGG-3 Series 4 to score his 1st victory.
Mladshiy Leitenant =FI=Pike bailed out.
Mladshiy Leitenant =FI=Genosse bailed out.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 12th ground target.
Mladshiy Leitenant =FI=Genosse was shot down.
Oberfeldwebel chaos shot down a P-39D1 Airacobra to score his 2nd victory.
Mladshiy Leitenant =FI=Pike was shot down.
Oberfeldwebel Nephris shot down a P-39D1 Airacobra to score his 1st victory.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 13th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 14th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 15th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 16th ground target.
Mladshiy Leitenant McB was shot down.
Oberfeldwebel Nephris shot down a PE-2 Series 84 to score his 2nd victory.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 17th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 18th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 19th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 20th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 21st ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 22nd ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 23rd ground target.
Oberfeldwebel BC Graf Zahl was shot down.
Oberfeldwebel Emse crashed.
Mladshiy Leitenant =FI=Nellip was shot down.
Oberfeldwebel chaos shot down an IL-2 Series 3 to score his 3rd victory.
Mladshiy Leitenant =FI=Mikester was shot down.
Oberfeldwebel chaos shot down a P-39D1 Airacobra to score his 4th victory.
Oberfeldwebel Emse destroyed a tank for his 1st ground target.
Oberfeldwebel Emse destroyed a stationary object for his 2nd ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 24th ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 25th ground target.
Oberfeldwebel SirAthlon destroyed a stationary object for his 1st ground target.
Oberfeldwebel BC Graf Zahl destroyed a vehicle for his 26th ground target.
Oberfeldwebel BC Graf Zahl was shot down.
Oberfeldwebel Nephris destroyed a tank for his 1st ground target.
Oberfeldwebel Nephris destroyed a tank for his 2nd ground target.
Oberfeldwebel Nephris destroyed a tank for his 3rd ground target.
Oberfeldwebel Wolf crashed.
Oberfeldwebel EJGr.Ost Caspar destroyed a gun for his 1st ground target.
Mladshiy Leitenant =FI=Pike, having bailed out, hitched a ride back to the airfield.

\nPilot Losses:
Oberfeldwebel BC Graf Zahl was killed.
Oberfeldwebel Nephris was killed.
Mladshiy Leitenant =FI=Genosse was killed.
Oberfeldwebel Emse was killed.
Mladshiy Leitenant =FI=Armitage was killed.
Oberfeldwebel chaos was killed.
Oberfeldwebel StG2 Juuti was killed.
Oberfeldwebel EJGr.Ost Caspar was captured.
Mladshiy Leitenant McB was killed.
Mladshiy Leitenant =FI=Nellip was killed.
Mladshiy Leitenant =FI=Mikester was killed.
Oberfeldwebel Wolf was killed.
\nOther News: 
A T34/76 unit was destroyed near Ruza Airfield (M-13).
A -T34/76 unit was destroyed near Ruza Airfield (M-13).
A PzIIIJ unit was destroyed near Shakovskaya (K-15).
A M3A1Stuart unit was destroyed near Uvarovka Sukov (K-9).
A M3A1Stuart unit was destroyed near Uvarovka Sukov (K-9).
A T34/76 unit was destroyed near Medyn Airfield (L-4).
A -T34/76 unit was destroyed near Medyn Airfield (L-4).
A PzIIIN unit was destroyed near Medyn Airfield (L-4).
A PzIIIN unit was destroyed near Medyn Airfield (L-4).
A PzIIIN unit was destroyed near Medyn Airfield (L-4).
A PzIVF unit was destroyed near Iznoski Airstrip (J-5).
A PzIVF unit was destroyed near Iznoski Airstrip (J-5).
A PzIVF unit was destroyed near Iznoski Airstrip (J-5).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIVF unit was destroyed near Iznoski Airstrip (J-5).
A PzIVF unit was destroyed near Iznoski Airstrip (J-5).
A PzIVF unit was destroyed near Iznoski Airstrip (J-5).
A PzIIIJ unit was destroyed near Ruza Airfield (M-13).
A PzIVF unit was destroyed near Ruza Airfield (M-13).
A PzIVF unit was destroyed near Ruza Airfield (M-13).
A PzIVF unit was destroyed near Ruza Airfield (M-13).
A PzIIIJ unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza Airfield (M-13).
A PzIIIN unit was destroyed near Ruza_Airfield (M-13).
A PzIIIN unit was destroyed near Ruza_Airfield (M-13).
An I-16 Type 18 was shot down.
A T28 unit was destroyed near Ruza_Airfield (M-13).
A M3A1Stuart unit was destroyed near Ruza_Airfield (M-13).
A M3A1Stuart unit was destroyed near Ruza_Airfield (M-13).
A Bf-109E-7 was shot down.
An I-16 Type 18 was shot down.
A P-40E M105 was shot down.
A P-40E M105 was shot down.
A KV1 unit was destroyed near Iznoski_Airstrip (J-5).
A Ju-87D-3 was shot down.
A MiG-3UD was shot down.
A Ju-87D-3 was shot down.
A Bf-109F-4 was shot down.
A P-39D1 Airacobra was shot down.
A Bf-109F-4 was shot down.
A Ju-87D-3 was shot down.
A LaGG-3 Series 4 was shot down.
An I-16 Type 18 was shot down.
An IL-2 Series 3 was shot down.
A P-39D1 Airacobra was shot down.
A Bf-109F-4 was shot down.
A P-39D1 Airacobra was shot down.
A Bf-109E-4/B was shot down.
A T34/76 unit was destroyed near Ruza_Airfield (M-13).
A -T34/76 unit was destroyed near Ruza_Airfield (M-13).
A T34/76 unit was destroyed near Ruza_Airfield (M-13).
A -T34/76 unit was destroyed near Ruza_Airfield (M-13).
A Bf-109F-4 was shot down.
A T28 unit was destroyed near Ruza_Airfield (M-13).
A P-39D1 Airacobra was shot down.
A LaGG-3 Series 4 was shot down.
A Bf-109F-4 was shot down.
A P-39D1 Airacobra was shot down.
A LaGG-3 Series 4 was shot down.
A T34/76 unit was destroyed near Ruza_Airfield (M-13).
A -T34/76 unit was destroyed near Ruza_Airfield (M-13).
A T34/76 unit was destroyed near Ruza_Airfield (M-13).
A -T34/76 unit was destroyed near Ruza_Airfield (M-13).
A Bf-109F-4 was shot down.
An IL-2 Field Mod. was shot down.
A T34/76 unit was destroyed near Ruza_Airfield (M-13).
A -T34/76 unit was destroyed near Ruza_Airfield (M-13).
A T34/76 unit was destroyed near Ruza_Airfield (M-13).
A -T34/76 unit was destroyed near Ruza_Airfield (M-13).
A MiG-3UD crashed.
A T34/76 unit was destroyed near Iznoski_Airstrip (J-5).
A -T34/76 unit was destroyed near Iznoski_Airstrip (J-5).
A MiG-3UD crashed.
A M3A1Stuart unit was destroyed near Ruza_Airfield (M-13).
A M3A1Stuart unit was destroyed near Ruza_Airfield (M-13).
A KV1 unit was destroyed near Ruza_Airfield (M-13).
A Soviet truck convoy was destroyed near Ruza_Airfield (M-14).
A P-39D1 Airacobra was shot down.
A MiG-3UD was shot down.
A Soviet truck convoy was destroyed near Ruza_Airfield (M-14).
A PE-2 Series 84 was shot down.
A Ju-87D-3 was shot down.
A Bf-109E-7 was shot down.
A Bf-109F-4 crashed.
An IL-2 Series 3 was shot down.
A P-39D1 Airacobra was shot down.
A Yak-7B was shot down.
A Yak-7B was shot down.
A Soviet truck convoy was destroyed near Ruza_Airfield (M-14).
A Bf-109E-7 was shot down.
A German train was destroyed near Shakovskaya_Station (K-15).
An IL-4 DB3F was shot down.
A Bf-109F-4 crashed.

edit:
the temp. airfield situation


(click to enlarge)

The referring excel file is also up2date.
Download Excel File
If a squadron has null planes left, the downgrade kicks in.




@Genosse: did u receive the PM?

[:FI:Blue2]

Nephris, thanks for the route map above - very useful. It's so good I would suggest creating such a map at the start of each campaign in the future if you can.
Mother Russia is still licking her wounds from the lashing we took on Sunday. If we "did well," I have no idea how that happened - purely by luck & AI, I think. Hope we can recruit more pilots next time to even things up a bit - that was rough!

This latest map shows you are attempting again to transfer our squadrons - thank you. Do you feel more confident it will work this time, with normal death limits, plane limits, etc.? I mean, did you discover the reason why it failed to work this past Sunday & correct it? Just curious.
Also, since the lines moved, are our squadrons at Peredel (M8) now in danger of being captured? If you say yes, we will request transfers for them.

You might want to check spawn points again for the Pe-2s. We had the old problem again on Sunday - an Li-2 too close to one spawn pointat R14. (I suppose this could happen with the bombers at R8 this time, if the transfers work properly..?)
Thanks again & cheers,
Blue2

[Nephris]

If we "did well," I have no idea how that happened - purely by luck & AI, I think. Hope we can recruit more pilots next time to even things up a bit - that was rough!

Our "bomber" fellows from the "flying blue pig combat squad", were queit thankfull, that we binded you, by the price of almost all of our fighters.
AI is a big variable in this large scale battlefield. If you got ace generated AI, it will rip your tanks apart by one bombdrop. Sometimes I cant judge anymore if I am dogfighting an AI or not, as their fighting characteristics really changed positive since 4.10. Turning tight doesnt work anymore to get on an AI six.
It would be really nice if some of Java1 could join.

Nephris, thanks for the route map above - very useful. It's so good I would suggest creating such a map at the start of each campaign in the future if you can.

Sure thing. Dunno why i didnt provide this info earlier, as those road maps are the ver5y first sketch of a campaign I create. It slept all the time as deactivated layer in my photoshop file to create the overall map aswell.

Do you feel more confident it will work this time, with normal death limits, plane limits, etc.? I mean, did you discover the reason why it failed to work this past Sunday & correct it? Just curious.

Yes. I just f**ed the server installation, reinstalled it, tested the latest mission with the new planes/cockpits and everything worked as it should.Just in case I also installed a backup dedicated sever ... for whatever issue appear to happen ***knock on wood***. Limits will be fine again either.
All plane losses of last sunday etc are counted, the updated excel file above lists the actual numbers of available aircrafts. Means next sunday P39 should be substitued by some Hurricanes and Bf109E4 will substitude some F4.

You might want to check spawn points again for the Pe-2s. We had the old problem again on Sunday - an Li-2 too close to one spawn pointat R14. (I suppose this could happen with the bombers at R8 this time, if the transfers work properly..?)

Yes, I will have to check each spawnplace again, as soon as we switch to a Moscow summer map.
Static planes are positioned in the master mission, from what all coming missions are generated.
If a Mig3 squad is located at Medyn, the static plane turns into a static Mig3.
If a Pe2 gets transfered to that airfield, the static planes turns into a static Pe2.
Of course the Pe2 has a bigger radius, than the once used placeholder from the master mission.
So that is the reason why we sometimes suffer on those static planes.

I will deactivate all Li-2 at R14, but as soon as a truck column passes that airfield again, the static Li-2 will be appear again...just keep tellng me,as long as I didnt fixed the master map.If you suffer too many kills by that, we can rise the death kick count.

Also, since the lines moved, are our squadrons at Peredel (M8) now in danger of being captured? If you say yes, we will request transfers for them.

Good find. I didnt noticed that Blue is able to attack Peredel. I will have to ckeck in my sandbox how DCG behaves with manual transfered squadrons and the "No transfer" Option deactivated. I guess it will move the squads on its own in Danger. However I will take care on your squads at Peredel. Any other transfer wishes?Even if already generated the first mission, we can add the transfer for the second mission at least. Transfers can be planned by date, means I can add a kind of timestamp, the refering squad and the destination, without touching DCG Gui.

expl.
194203060 movesquad 160IAP Medyn_Airstrip - 6th march squadron 160IAP is transfered to Medyn
194203090 movesquad 160IAP Istra_Airfield - 9th march 160IAP is transfered to Istra
194203090 movesquad 175SHAP Medyn_Airstrip - 9th march 175SHAP is transfered to Medyn

That way we can plan transfers in future ... useful or not...we will see

[:FI:Blue2]

Thanks for all the info again, Nephris.
Now that I had a chance to review the recordings a bit, couple more comments / questions.
1) Cycling through Shift-F2 views, there are no "friendly" ground cameras viewable to us on the Red side. Cycling through Ctrl-F2 there are 2 "enemy" cameras we can view, though. However, both of these are located at the M13 airbase, where Red had a LARGE number of tanks stalled in combat for about the past weeks or more. (These same cameras have been there at least that long, and no others anywhere. Just haven't bothered to mention before now.) With that airfield now [finally] recaptured by Red, this issue might go away, but have some questions about it:
- can you view this position from recordings done on Blue side? Or are there other cameras that only blue players can see in their recordings?
- why 2 cameras in one ground location & none elsewhere? If both sides can see only these 2 cameras, we would vote to either place more cameras at other constested locations, or else remove all ground cameras. Is camera placement controlled by DCG, or by something else?
- NICE work by your "blue pig" boys at M13 - they killed ~20 of the 30+ red tanks stalled there with their 3 Ju-88s & escort during one missions on Sunday! But frustrating for us that these tanks took so many missions before finally moving on. Each mission more would arrive there, the mass of Red armor would then quickly knock out all the German opposition nearby (in initial 5-10 minutes of each mission), then would remain stalled there in that one spot for the remainder of the 90 minutes! Any idea why the tanks stalled there so long? Was it just because more German tanks managed to arrive there every mission, or was DCG having a problem at this field somehow?
- I flew an IL-2 to this airfield in one mission on Sunday & expended all my cannon ammo & bombs on 1 surviving Pzkw IV I could clearly see on the ground, but the dang thing would NOT die! When I watched the recording, however, I understood - that tank is a ghost!! It does not appear at all in the recording so I appear to be shooting a spot on the ground the whole time. I'm glad it wasn't my poor shooting/bombing... but this is obviously some kind of bug or something. Ever seen/heard of it before?

2) This was probably just because we were on your listen server, but there was a HUGE paradrop by Red that I saw on the recording. We're talking at least 300 parachutes & probably more. Thought I should mention it in just case you need to know, but no need to respond about it though - just FYI for you.

3) Tell Chaos I love the bright blue, glowing superhero flight suit he wears. Is that thing latex or what? Looks itchy.

[Nephris]

can you view this position from recordings done on Blue side? Or are there other cameras that only blue players can see in their recordings?

Those static cameras, are accessable for red & blue and are automatically created by DCG at each "contested" area. This are the locations where red & blue fight for the upper hand.
I havent found a command to deactivate the genearation of static cameras in DCG, but I could deactivate the outside views completly which would also effect view "taxing on ground".

Any idea why the tanks stalled there so long?

Each location has a certain "troop count" ,that needs to be nulled by one side to make the other move on.
The problem to some location is the gap , that seperates red from blue tanks or red static arms from blue static arms at some locations.This gaps appear due hills or sometimes too many buildings,trenches etc in the line of fire. It can happen, that it needs help from air to clear the way then, which was the result of last sunday.Red cleared (dunno if by help of airforce) at last Ruza Airfield and advances,as the actual frontmap indicated. The mass of tanks was created while the past 3-4 missions, each contested area triggers ground coloumns to that location in a higher chance than other locations.

or was DCG having a problem at this field somehow?

However ,I cant guarantee that this location doesnt have an issue and we need to keep an eye on the next tank battle at Ruza Airfield and for sure DCG is is not perfect.

When I watched the recording, however, I understood - that tank is a ghost!!

Where did u notice the tank? At Ruza_Airfield also?
Was it maybe a StuGIII? Each side creates defense weapons on defending locations.
As Blue has 2:3 relation in tank number to Red, Blue uses a StugIII and 2xpak for defense positions, awhile red uses 2xpak and a BA-2. Maybe this could be the "ghost tank"? And maybe that one was located out of the line of fire for red tanks at Ruza Airfield, so it couldnt advance.
I created a small sketch of the theoretical organisation of the defense systems.

Truck columns (if they arrive at a front area/contested location) turn into defense position and place artillery canons a few hundred meters of the speerhead.
By default defense positions are created on each front location, messured on the speerhead, this guns are created around 100 - 50 m before.
Tanks create the speerhead, means they drive to the last waypoint. This can cause tank queues that stand into each other. Ashame but not changeable but decreasing the tank count, which would decrease the chance of those queues.

We're talking at least 300 parachutes & probably more.

.Thx.
Cant imagine what happened there.... Just checked the eventlog and noticed that both civil planes got lost completely. There were imho 4x Ju52 on their way wich transport each 24 or 36 paratroopers?
The Li-2 got lost aswell btw. Bedor crashing they pop their cargo.
Sounds like shooping tour at Market Garden...

glowing superhero flight suit he wears

Actually he is known as the Blue Lantern....

I just checked DCG behaviour on manual transfers with "No transfer" Option deactivated.
DCG moves the squadron on its own, even if I manually moved the squads before.
That means ,we would need to activate the "No transfer" Option to get full access on squad transfers or accept certain DCG made transfers, without the need to take care of threatened squads.
I checked it on the example "I-16 at Peredel", which got transfered within the mission to Istra by DCG with "No Transfer" deactivated.


edit:
I reworked the master template.
-moved static planes at airfields to proper places
-added runway light for red & blue for requests (TAB->ground control ->request runway lights)
-added Großdeutscher Rundfunk & Radio Moscow (just in case you would like to add your own music files to your local folder)
-added Beacon for red and blue


adding music to the radio station
the music you can listen in the radio ingame is not broadcasted via the network.
That means you can listen to whatever you want to.
Thislink points to some packages of radio files,
which go into \IL-2 Sturmovik 1946\samples\Music\Radio\Grossdeutscher_Rundfunk
If you want to create your own files you need following settings in your audio editing tool
a freeware tool like audacity etc is fine.

Code: Select all

Extention : .wav
Audio format : mp3
Channels : (the same as source)
Sample Rate : 44100Hz
Encoding : LameEnc / 192 Kbps, 44100Hz Stereo

Dont forget to turn your ingame music on or increase the volume.

Some planes are able to navigate on radio streams only, and doesnt need Beacons, does anyone knows which ones that are?

[:FI:Armitage]

Hi Nephirs,

re the log files and the large number of unknow objects that are not counted or missing from the stats.

I wrote a little c# program and I can match the unknows in 99% of the cases which should make for more accurate stats.

There are a few things I can do
1: take the original log file, replace all of the statics/unknowns with the correct object and rewrite the log file
2: create a custom parse file and out the details in what ever format you want (also ready for db insertion if you want)
3: I can also extract information such as
A: flight time, cloud height, basic weather info, wind direction etc.
B: Weapons, fuel load out etc
C: Lights/Smoke trails on/off and duration

Tell me what you would like and I will produce the output file.

[:FI:Sneaky_Russian]

Some planes are able to navigate on radio streams only, and doesnt need Beacons, does anyone knows which ones that are?

Only covered FW190 and B25 on the JO course (theres another starting in May). JU 88 has radio pointer in compass
Well, any radio navigation will need some sort of beacon/ radio source. Don't confuse Non Directional Beacons (NDB) with Lorenz Blind landing ( Ultrakurzwellen-Landefunkfeuer for short? ). NDBs can be placed anywhere, but blind landing has to be placed at the end of a runway. Only aircraft with a seperate radio compass ( in addition to the magnetic/gyro compass), and/or ADF will be able to use the NDBs or radio stations to navigate.
Any Aircraft with a radio should be able to tune to the landing beacons and hear the dash (right), continuous (centr) , dot (left)
I started a spreadsheet , but been slacking since "B"