PWCG Normandy Beta 2 Released

[PatrickAWlson]

1 hour ago, TheSNAFU said:

I couldn’t seem to get a clear answer to the way tactical markings treat custom skins. My hope for pwcg is that I can chose the custom skins i

want for my plane and my squadron through skin management and they will not be overridden by the new game feature. All other ai planes would have the new markings unless they are also custom skins. 

 

I am hoping that the game doesn't care about in game vs custom.  

[quelcertoleo]

@PatrickAWlson

this stacktrace can be replicated 100% with starts from parked and Allied coalition:

PWCG Error
Wed Oct 12 21:53:31 CEST 2022
java.lang.NullPointerException
	at pwcg.mission.flight.initialposition.FlightPositionParkedStart.calculateAngleForLeadToBeClosestToRunway(FlightPositionParkedStart.java:50)
	at pwcg.mission.flight.initialposition.FlightPositionParkedStart.createPlanePositionParkedStart(FlightPositionParkedStart.java:28)

 

time for some junits

 

have fun.

[justin_z3r0]

having trouble generating a campaign - I'm sure its something I'm doing wrong - can anyone help?

generate campaign remains greyed out after I've filled all information.

[PatrickAWlson]

5 hours ago, Robi89 said:

Regarding the new tactical markings - right now, a custom skin assigned to a pilot will "overwrite" the ingame tactical markings. Will you keep it that way?

 

I am asking because the ingame tactical markings - especially for RAF birds - just don't look right for me. For planes from other squadrons I may only see in passing they're perfectly fine, but for the "hero planes" (me and my wingmen) I honestly prefer even my own rather low-skill skinning efforts.

 

There is a useTacticalMarkings flag parameter associated with a skin.  By default this is false - i.e. don't use tactical markings.  Obvious reason is that most custom skins already have markings.  Dynamic tactical markings are meant to be used with blank skins.  

 

I want to start making blank skins with squadron markings.  This would allow tactical codes to be used with squadron liveries.  

20 minutes ago, justin_z3r0 said:

having trouble generating a campaign - I'm sure its something I'm doing wrong - can anyone help?

generate campaign remains greyed out after I've filled all information.

 

Make the name letters only.  Note to self - put validation in the code to enforce this.

[justin_z3r0]

4 minutes ago, PatrickAWlson said:

Make the name letters only.  

 

Thanks!

[oFlyingDutchman]

Hey Pat, while flying as Britain in late 41', i'm getting missions that i'm supposed to intercept enemies coming to atack my airfield, that being said, after 4 of those missions in a row, i've yet to see any of them. Any chances the bombers are, maybe, spawning too far from the patrol zone that they cant reach the airfield before my flight leader finish the patrol around the airfield?

[blockheadgreen_]

Wondering if there might be an option for a historical RAF 1941 campaign for the Channel front, down the line? Fighter Command operations in 1941 are hugely interesting and iconic on their own right, and I'm not sure I'm a big fan of the idea of losing that to an ahistorical BoB a year later with 1941 aircraft - just feels a bit strange. I imagine 1940 aircraft like the Spit Mk I/II & Hurri Mk I, 109 E-4, etc. are something we'll see down the line as it's too big of an opportunity not to capitalise upon.

[oFlyingDutchman]

Yeah, another mission, this time around, a group of 109's showed up, the cheat debrief showed a flight of stukas, one of he's and one of 109's where supposed to show up, only the fighters came
Edit: Just was it is a know bug, can confirm that so far, 5/5 missions to intercept bombers coming towards my airfield (66 squadron - british - stationed at manston) they didnt even showed up on radar

Edited October 13, 2022 by oFlyingDutchman

[Patricks]

6 hours ago, Lythronax said:

Wondering if there might be an option for a historical RAF 1941 campaign for the Channel front, down the line? Fighter Command operations in 1941 are hugely interesting and iconic on their own right, and I'm not sure I'm a big fan of the idea of losing that to an ahistorical BoB a year later with 1941 aircraft - just feels a bit strange. I imagine 1940 aircraft like the Spit Mk I/II & Hurri Mk I, 109 E-4, etc. are something we'll see down the line as it's too big of an opportunity not to capitalise upon.

 

Get CLoD and enjoy!

[PatrickAWlson]

10 hours ago, Lythronax said:

Wondering if there might be an option for a historical RAF 1941 campaign for the Channel front, down the line? Fighter Command operations in 1941 are hugely interesting and iconic on their own right, and I'm not sure I'm a big fan of the idea of losing that to an ahistorical BoB a year later with 1941 aircraft - just feels a bit strange. I imagine 1940 aircraft like the Spit Mk I/II & Hurri Mk I, 109 E-4, etc. are something we'll see down the line as it's too big of an opportunity not to capitalise upon.

 

My suggestion would be to start your career in January 1942 and skip PWCG 1941.  That way you will be on the correct timeline with the correct aircraft.  Obviously I do not have a a Spitfire Mk I or a Hurricane Mk I, so I cannot do an accurate Dunkirk or BoB.

 

Right now in PWCG, from Oct 1941 to June 1943 represents the channel front.   The most common missions are raids, sweeps, and anti shipping.  The Luftwaffe has mostly moved east.  The Americans have not yet arrived in numbers.  The British are annoying the Germans ands the Germans wish they would just stop already.  If anybody has more suggestions for this time period please post them.  

[VadimOsovsky]

hi @PatrickAWlson! Have you had any thoughts on making a more friendly UI for PWCG? Do you currently have any ideas?

[Russkly]

24 minutes ago, PatrickAWlson said:

 

My suggestion would be to start your career in January 1942 and skip PWCG 1941.  That way you will be on the correct timeline with the correct aircraft.  Obviously I do not have a a Spitfire Mk I or a Hurricane Mk I, so I cannot do an accurate Dunkirk or BoB.

 

Right now in PWCG, from Oct 1941 to June 1943 represents the channel front.   The most common missions are raids, sweeps, and anti shipping.  The Luftwaffe has mostly moved east.  The Americans have not yet arrived in numbers.  The British are annoying the Germans ands the Germans wish they would just stop already.  If anybody has more suggestions for this time period please post them.  

 

You're spot on, Pat apart from perhaps bringing in USAAF coastal raids in late '42/early '43:

 

"German night raids tailed off in May 1941 as Luftwaffe bomber units were deployed elsewhere. Meanwhile, single-engined fighter-bombers continued to carry out sporadic daylight attacks, but these were more of a nuisance than a strategic threat. Fighter Command had again proved its mettle in defence. But it now had a new boss and a new mission. Air Chief Marshal Sir Hugh Dowding, who had been in command during the Battle of Britain, had been edged out in November 1940. In his place came Air Marshal Sir William Sholto Douglas, whose primary objective was to take the war to the enemy over occupied Europe. 

This new offensive saw fighter squadrons embarking on a variety of routine operations, each given a codename. The simplest was known as a 'Rhubarb', in which small numbers of aircraft – usually just a pair – flew at low-level into France or Belgium to shoot up targets of opportunity on the ground. Rhubarbs were normally flown in bad weather so as to avoid enemy fighters, but this alone made them hazardous. Anti-aircraft fire was another danger and the losses suffered far outweighed the damage caused to the enemy.   

Large scale fighter sweeps, known as 'Rodeos', were flown over enemy territory in fine weather at high altitude in the hope of enticing the Luftwaffe into action. But as the RAF had found in 1940, enemy fighters on their own posed a negligible threat and could be safely ignored. Something was needed to persuade the enemy to come up and fight. The result was the 'Circus' – an operation involving several squadrons of fighters covering a small raiding force of bombers acting as bait. 

In all these operations range was the limiting factor. The RAF fighters could only penetrate about 60 miles in from the enemy coast at its closest point, and had two Channel crossings to contend with. The Luftwaffe had warning of RAF incursions from its own radar and could pick and choose when and where to intercept. The Germans became adept at 'bouncing' RAF fighters from above. And being over enemy territory, any RAF pilots who survived being shot down were usually captured.    

Hitler's invasion of the Soviet Union in June 1941 put pressure on the RAF to step up its attacks and tie down as many Luftwaffe fighters as possible in France. Operations became larger and more sophisticated. The so-called 'summer offensive' saw about 90 major sweeps, mostly between Rouen and Lille, alongside Rhubarbs and attacks against coastal shipping (known as 'Roadsteads'). The results were disappointing, and costly. Some 300 RAF pilots were lost. The famous British ace Douglas Bader, who had lost both his legs in a pre-war flying accident, was one of those shot down and captured. Nor did the attacks prevent the Luftwaffe from moving most of its force eastwards. Only two German fighter units with about 200 aircraft remained in France, and these proved more than enough to counter the RAF. 

 

"The Luftwaffe now also enjoyed a qualitative advantage over the RAF. The Messerschmitt Bf109F was a match for the latest Spitfire – the Mk Vb – and the new Focke-Wulf Fw 190 was significantly superior in performance. The Hurricanes found themselves totally outclassed and relegated to the ground attack role. These 'Hurribombers' had some success on 'Ramrods' – short-range bombing operations against specific targets such as harbours and airfields. But overall, the RAF's offensive operations – especially the Circuses and large-scale fighter sweeps – had become prohibitively expensive, and in November 1941 Fighter Command was ordered to suspend all but the most essential. Routine attacks were limited to coastal areas, well away from the Luftwaffe.

 

"In 1942 Fighter Command resumed its own offensive, but owing to the continuing superiority of the the Fw 190 losses remained high. 280 RAF fighters – mostly Spitfires – were shot down in the first five months of 1942. In June Sholto Douglas was once again told to restrict operations to coastal targets. In the meantime a new stop-gap Spitfire variant, the Mk IX, was rushed into service. Its powerful new Merlin 61 engine meant the RAF finally had a fighter to match the Focke-Wulf.  

Four squadrons of Spitfire Mk IXs were available in August when Fighter Command fought its biggest battle of 1942, supporting the doomed combined operations raid on the French port of Dieppe. The RAF was tasked with supporting the naval assault, but saw a golden opportunity to inflict a decisive blow on the Luftwaffe which responded in strength. In a ferocious day of combat Fighter Command lost 100 aircraft and 52 pilots killed or captured in exchange for only 48 enemy planes, of which 23 were fighters. It was an undeniable German victory.  

 

"The range – or rather the lack of it – of the Spitfire was still a major challenge, especially now that bomber escort duties were becoming an increasing part of Fighter Command's workload. As well as the RAF's own light bomber force, demand now came from the United States Army Air Forces (USAAF) Eighth Air Force, which had started its daylight strategic bombing campaign in the summer of 1942. At first the targets were in northern France, where Fighter Command could provide a degree of cover, but in 1943 the Americans began to strike at more distant objectives in Germany, where they were on their own. The massive increase in Allied bombing attacks meant that the old-style Circus operations were now redundant. The Luftwaffe in the west had been greatly reinforced, and there was no longer a need to coax it into the air – the defence of occupied Europe and the Reich itself was now a German priority.        

Fighter Command's own offensive operations were also stepped up. The Mosquito had already proven itself as the dominant night fighter over the UK, but its speed, range and heavy armament also meant it could be used to advantage on deep penetration 'Ranger' sorties over enemy territory, seeking out enemy aircraft or ground targets. Bomber support was another vital Mosquito role. Some joined the RAF heavy bomber streams and used their radar to hunt enemy night-fighters. Others flew 'Intruder' missions to German airfields, where they lurked in the darkness waiting to pounce on aircraft landing or taking off. The Typhoon was also increasingly used on offensive operations over enemy territory, with shipping, airfields and railways as prime targets."

 

Source: "What Did Fighter Command Do After The Battle Of Britain?", Imperial War Museums (https://www.iwm.org.uk/history/what-did-fighter-command-do-after-the-battle-of-britain)

 

 

[blockheadgreen_]

4 hours ago, Patricks said:

 

Get CLoD and enjoy!

As it happens I've only just uninstalled it permanently...

 

I'll go with a 1942 career and give it a try!

[TheSNAFU]

So I ran a few missions with the historical skins mod off in jsgme that among other things, adds swastikas to German skins. I had custom skins for me and my squadron set in skin management. The new markings did not appear on my plane or my mates but also did not appear on any ai friendly or enemy ac either. I generated entirely new missions for this test. 
 

I sure hope at some point we can enjoy whatever skins we want for our planes and those of our squadron while seeing the new makings on all other ai friendly and enemy planes. 
 

I don’t really understand pwcg skin use other than those I chose for me and my squadron using skin management so perhaps that is where my problem is? 

Edited October 13, 2022 by TheSNAFU

[PatrickAWlson]

5 minutes ago, TheSNAFU said:

So I ran a few missions with the historical skins mod off in jsgme. I had custom skins for me and my squadron set in skin management. The new markings did not appear on my plane or my mates but also did not appear on any ai friendly or enemy ac either. I generated an entirely new mission for this test. 
 

I sure hope at some point we can enjoy whatever skins we want for our planes and those of our squadron while seeing the new makings on all other ai friendly and enemy planes. 
 

I don’t really understand pwcg skin use other than those I chose for me and my squadron using skin management so perhaps that is where my problem is? 

 

Getting dynamic markings to work might take some effort.  I have not altered the code in any way, so what PWCG has is what was developed quite some time ago.  I have not yet had the time to understand the rules and update the code.  Any suggestions as to where to find the rules is appreciated.

[TheSNAFU]

I appreciate that you have your hands full getting a final Normandy build done and the markings is a new feature you haven’t had time to study. I wish I could help with markings but I don’t have the knowledge to do so. Hopefully someone can help you. 

[Robi89]

In my last mission, I came across a flight of Spitfires without the new markings. Every other RAF plane I could see had them.

After finishing the mission, I had a look at the intelligence report and found this:

 

 

For some reasons, the aircraft of 403 Squadron have no tactical codes in PWCG.

 

Also, in the same mission, I spotted some Ju 87s from II./StG77 where only the leader had a tactical code (on a winter camo skin, no less) while the other three aircraft were blank.

[TheSNAFU]

Interesting. I couldn't find an

1 hour ago, Robi89 said:

Every other RAF plane I could see had them.

Interesting, I couldn't find any plane friendly or enemy with the new markings. I wonder what the difference might be. 

[Stonehouse]

19 hours ago, PatrickAWlson said:

 

Getting dynamic markings to work might take some effort.  I have not altered the code in any way, so what PWCG has is what was developed quite some time ago.  I have not yet had the time to understand the rules and update the code.  Any suggestions as to where to find the rules is appreciated.

 

@PatrickAWlson

I am still trying to confirm things and perhaps someone else can go through the same analysis as well, so it is confirmed or denied independently. I've been using the P40 as my test case as it is used by 3 different air forces.

 

I believe the rules are:

• The default skin and any official skin with the word blank in the skin name are able to accept tactical codes
• Any official skins without the word blank in the skin name are not able to accept tactical codes - Note the aircraft setup GUI in game changes for these skins and you cannot enter a tactical code
• Any custom skin is always able to accept tactical codes. 
• If you leave tactical codes unpopulated you just get the skin as is.
• I believe the default tactical code colour for all code positions is black 

 

The below is only brainstorming and to try to give you ideas to consider. Definitely not intending to instruct you on your own code as that would be rude and completely out of line. Please read the following with that idea in mind as I don't intend any offense.

 

Using the above alpha set of rules in respect to PWCG I theorize that:

• The tactical codes would be populated as now by the squadron code from the squadron json plus whatever your code is doing to populate the remaining code positions. You likely need to revisit the colour logic as each code position can have a different colour and for Luftwaffe and bombers should have different colours for parts of the code if you want it historically accurate. You would need to handle different air forces having a different number of positions as Luftwaffe have a lot more code positions than Allied aircraft. 
• You could assume tactical codes are always on and probably the default colour is black as you will 99% of the time provide PWCG with squadrons set to use the default skin or one of the official blank skins. This could save you configuration effort particularly where an aircraft/squadron skin doesn't change much or is just the default skin and one other later skin as you don't have to declare the default skin.
• If you are using the default skin, then I don't think you need to declare any skin in the aircraft skins json or squadron json as long as PWCG assumes tac codes are always on. My own testing indicates that if you do not declare any skin in PWCG for an aircraft you automatically get the default. In fact, this was the situation for the Me410 and Mosquito when you first added them. Neither had a skin entry anywhere in PWCG and so got the default skin. Now they would get default skin plus codes courtesy of the game and PWCG squadron setup and logic as long as the tactical codes are populated at the point of mission creation and so if the PWCG standard position is use codes and a default colour for all letters such as black you won't need to declare anything unless you want a specific colour combo. In the current release version of PWCG you assume tactical codes are off and this is overridden by declaring a skin with "use tactical codes: true". If you flip this around, I believe you will save yourself effort in the long run.
• If you want to use one of the official blank skins, then you would need to declare the skin in either aircraft skins json or squadron json. If you took the position that codes are on and have a default colour unless otherwise advised there is no need to declare whether or not tactical codes are used and the colour unless you do not want tactical codes or you want a specific colour combo.  You would need to declare skins for situations where the skin, while still one of the official blank skins, changes over time. e.g., RAF Hurri 2 squadrons can pretty much only use the official blank skin set and be historically correct but as the war progresses the skin used changes so each time period's skin would need to be declared.
• Custom skins need to be fully declared at either squadron or aircraft level and tactical codes will need to be turned off if the custom skin already has them. If you did want to use tactical codes on the custom skin, you would also need to specify the colour combo and possibly none, some values other than the squadron codes or all code values depending on skin and situation.
• You may want to declare a skin for a historical ace and reserve the tactical code and not allow the PWCG logic to use this for other aircraft in the ace's squadron while the ace is alive.
• I guessing this means a change of GUI for skin set up at the user level in the skin management screen as things declared here by the user are in effect an override for that pilot.
  • I believe "squadron" has been replaced by the PWCG defined skin and tactical codes (even if that is no defined skin in PWCG and PWCG is using the default skin and default colour as above) and so "squadron" is redundant. I'm assuming here the original intent was to have a collection of individual squadron skins declared so each player/AI Pilot had their own tactical code and perhaps for units like the 352nd FG their own "nose art". Now that tactical codes are handled by the game it seems like the main driver for this option is gone.
  • I think "non squadron" and "loose" are really now effectively "personal" skin. Where the skin differs from the skin given by PWCG logic, the user would need to pick the skin from a list of custom and official skins and declare whether tactical codes are used or not. If tactical codes are used, then they would need to declare the colour choice for each code position and possibly the alphanumeric for the code positions other than squadron json ones. So, something similar in concept to what the game plane set up screen offers. Alternatively, you could just let them pick colours and then control population of the positions as normal via PWCG logic and squadron json or just let them choose the skin and whether to use tactical codes and everything else is via PWCG. I'm guessing you want to retain control over the code positions for the squadron at least. I assume here if you let them pick the remaining code values you would want ideally to ensure that your code did not generate a tactical code combination chosen for a personal skin. IE the personal choice reserves the tactical code. So, someone pretending to be Douglas Bader in 242 sqd doesn't see another squadron aircraft with the same tactical codes. That's ideally.......you could just leave it up to users to manage. If you let them pick all the code values including the squadron ones, then I would think they should have to manage duplication/issues. Ditto if they choose a skin to use and opt to not use tactical codes - issues of duplication become theirs to manage as PWCG can't tell what is on the skin. It all depends on how much freedom you want to give on colour and codes as the more freedom you give the more logic and complication there is for you.

 

Edited October 14, 2022 by Stonehouse
typo

[BBAS_PotroastBuckett]

Hey, this may be an offtopic question for this but does the normandy beta also work for other portions of pat wilson? Or is it specifically deisgned to only have Normandy, cause I'd hate to have to use two different PCWG launchers.

[PatrickAWlson]

1 hour ago, PotroastBuckett said:

Hey, this may be an offtopic question for this but does the normandy beta also work for other portions of pat wilson? Or is it specifically deisgned to only have Normandy, cause I'd hate to have to use two different PCWG launchers.

 

It works for all maps. 

[Stonehouse]

@PatrickAWlson

Some more background info for you Pat. I found the explicit control for skins to have access to tac codes. The "blank" in the file name is just for the dev team's convenience as I sort of expected based on my own experience in my work.

 

Anyway, I created a custom skins.tab.eng file this morning and tested the theory and confirmed the "blank" is not the control. I did this by adding a custom skin to this table and once there it shows up as an official skin in QMB. Regardless of the skin file name including "blank" or not I could access tac codes.

 

Looking further I found the real control is in the info.txt file for the aircraft. This is in data\swf\il2\worldobjects\planes\aircraft.

 

So, for the P40 the skin section of the file now looks like the below post 5.002. Note the addition of the 'denyTaccode' flag. If it is 1 then access to tac codes is denied and the inference is that the skin is non generic. I cannot remember if country code was in this table before, I think perhaps it wasn't. I think this may also be useful to you.

 

Spoiler

&paintSchemes=
unlockId,    id,                country,    denyTaccode|
1,    p40e1/p40e1_blank_01.dds,    101|
2,    p40e1/p40e1_blank_02.dds,    101|
3,    p40e1/p40e1_blank_03.dds,    101|
4,    p40e1/p40e1_blank_04.dds,    101|
5,    p40e1/p40e1_blank_05.dds,    103|
6,    p40e1/p40e1_blank_06.dds,    103|
7,    p40e1/p40e1_blank_07.dds,    103|
8,    p40e1/p40e1_blank_08.dds,    102|
9,    p40e1/p40e1_blank_09.dds,    102|
10,    p40e1/p40e1_skin_02.dds,        101,    1|
11,    p40e1/p40e1_skin_03.dds,        102,    1|
12,    p40e1/p40e1_skin_06.dds,        103,    1|
13,    p40e1/p40e1_skin_07.dds,        102,    1|
14,    p40e1/p40e1_skin_08.dds,        103,    1|
15,    p40e1/p40e1_skin_09.dds,        101,    1|
16,    p40e1/p40e1_skin_10.dds,        103,    1|
17,    p40e1/p40e1_skin_11.dds,        103,    1|

 

Edited October 14, 2022 by Stonehouse

[parkerc341]

Weird, tac markings showed up on my '42 RAF spit V campaign, but my 1944 109g6 late campaign doesn't work. 

[PatrickAWlson]

8 hours ago, parkerc341 said:

Weird, tac markings showed up on my '42 RAF spit V campaign, but my 1944 109g6 late campaign doesn't work. 

 

Just completing a rewrite of tac marking application.  Older code was working on defunct rules, so it would be hit or miss.  I examined many planes on all sides to get an understanding of tac markings.  Created many missions to review what the tac markings looked like for various planes/nations.  Rewrote the application process and corrected squadron data files.  the code and data changes are backed up by about 2k lines of test code, so hopefully all will be well in the next drop,

 

If not, just remember, the next release fixes all issues ... kind of like the sign that says free beer tomorrow.

[Russkly]

Flying a 41 Sqn. Spit Vb career in June/July 1941 I have encountered no enemy a/c in the last 3 missions (low alt cap, strategic intercept & intercept) and the combat reports revealed very little activity in general.

 

Air density set to High.

 

Let me know, if you need any files.

 

[TheSNAFU]

Pat, I hope the work Stonehouse did on tac markings helped with that part of your work. In any case shout out to Stonehouse for the efforts! 

[PatrickAWlson]

Beta 2 Fixed
Added Newspapers
Added Normandy iconic missions as single fly missions (Main Menu->Iconic Missions)
Added new 5.002 blank skins
Lots of work in code and configs on tactical codes
Played with the algorithm to try to keep airfield objects away from any area usable by real planes.
Normandy invasion obstacles appear on May 1 1944
Normandy mulberrys appear on June 15 1944
III./ZG 26 flying ME410s out of Dieppe Saint Aubin do not have enough runway.
Eliminated Ju88 North Africa skin
Fixed issue that could prevent AAR from completing.
Fixed issue of Allied AA in the water during landings

 

One of the config changes is not backwards compatible.  Delete PWCG and do a fresh install (i recommend this every time anyway).  Your campaigns ARE backwards compatible.  Just do not delete the User directory. 

[Stonehouse]

Possible enhancement for another day Pat as I'm pretty sure there are manual ways around it already.

Generally, waypoints for CAPs for early 1940s tended to be much higher altitude that later in the war - most missions I am seeing for combat air patrol are 5000-8000ft. Typically, 10-15K feet or even more so was the standard so there was the chance to engage with a height advantage. Later in the war unless on strategic bomber escort patrol altitudes were lower as more and more the Allies had air superiority. Especially after D-day Allied fighters and fighter bombers tended to be < 14K as that gave them a chance to shoot up ground targets of opportunity. So, guess I'm thinking some parameters need to become date sensitive now that PWCG is covering Western front from 1941 to 1945. I don't know if something similar perhaps in reverse happened on the Eastern Front, my guess would likely be it was around 5-10K ft and stayed there.

Edited October 17, 2022 by Stonehouse

[Robi89]

6 hours ago, PatrickAWlson said:

Beta 2 Fixed
Added Newspapers
Added Normandy iconic missions as single fly missions (Main Menu->Iconic Missions)
Added new 5.002 blank skins
Lots of work in code and configs on tactical codes
Played with the algorithm to try to keep airfield objects away from any area usable by real planes.
Normandy invasion obstacles appear on May 1 1944
Normandy mulberrys appear on June 15 1944
III./ZG 26 flying ME410s out of Dieppe Saint Aubin do not have enough runway.
Eliminated Ju88 North Africa skin
Fixed issue that could prevent AAR from completing.
Fixed issue of Allied AA in the water during landings

 

One of the config changes is not backwards compatible.  Delete PWCG and do a fresh install (i recommend this every time anyway).  Your campaigns ARE backwards compatible.  Just do not delete the User directory. 

 

Something in the new code for tactical codes is off. I just ran across a flight of four Hurricanes from 3 Squadron whose tactical codes should have read XM-(Aircraft ID Letter), instead they had codes like this: (Aircraft ID Letter)X-M.

 

 

Oh, and somebody seems to have nicked the Dover CH stations:

 

 

The codes on the German planes I could see looked right (except for the usual wonkiness with double-digit codes on fighters), however a flight of four Bf-110s of II./ZG 26 had no codes.

Edited October 17, 2022 by Robi89

[Eisenfaustus]

7 hours ago, PatrickAWlson said:

Added new 5.002 blank skins

Can those be downloaded in a seperate pack or are they part of the Beta?

[PatrickAWlson]

1 hour ago, Eisenfaustus said:

Can those be downloaded in a seperate pack or are they part of the Beta?

 

They are part of the game.  If you have Downloaded 5.002 then you have them.

[Eisenfaustus]

ah ok - thanks ^^

 

But I seem to be unable to select them via skin management.

 

Edited October 17, 2022 by Eisenfaustus

[CaptainFlemme]

Excellent work Pat !

 

Concerning US markings, there is at least one exception to add on the list : the P38J-25. It as two spots for the "plane identification letter" : one on the tails and one inside the vertical stabilizers. 

 

E.G, for a P38 of "E6" squadron, plane "A", markings would be : "E6AA" and not just "E6A" - "plane ID" letter should be duplicated. Current implementation is adequate, but could be more historical with plane markings on both places (and it's look very nice too!). Anyway, it's a detail, far from being crucial especially if a lot of work is needed to modify the current behavior for just one aircraft model - sorry to bother you with that.

 

Many thanks for your work

1 hour ago, Eisenfaustus said:

ah ok - thanks ^^

 

But I seem to be unable to select them via skin management.

 

Blank skins are used by default by PCWG ;), automatically choosen by  mission date :).

Edited October 17, 2022 by CaptainFlemme
Typo

[Eisenfaustus]

43 minutes ago, CaptainFlemme said:

Blank skins are used by default by PCWG ;), automatically choosen by  mission date :).

That makes a lot of sense of course ?

 

Thank you - and great work @PatrickAWlson

[PatrickAWlson]

6 minutes ago, CaptainFlemme said:

Excellent work Pat !

 

Concerning US markings, there is at least one exception to add on the list : the P38J-25. It as two spots for the "plane identification letter" : one on the tails and one inside the vertical stabilizers. 

 

E.G, for a P38 of "E6" squadron, plane "A", markings would be : "E6AA" and not just "E6A" - "plane ID" letter should to be duplicated. Current implementation is adequate, but could be more historical with plane markings on both places (and it's look very nice too!). Anyway, it's a detail, far from being crucial especially if a lot of work is needed to modify the current behavior for just one aircraft model - sorry to bother you with that.

 

Many thanks for your work

 

I have not yet gotten to each individual aircraft's quirks but I appreciate the information.  The LaGG and PE2s also have oddities that are modeled: fuselage or tail.  Appreciate the info. 

 

`

[TheSNAFU]

Flew two missions with the latest beta and the experience was good. Had dogfight action in both, units engaged as expected. Ships below and were firing AA at the enemy aircraft. I saw markings on the German planes (JU88's) but not on a flight of 4 British Spits at another location who were engaged with other Germans (FW 190's) that had markings. Also didn't see markings on parked planes on my field though I don't know if I should have or not. Screens loaded faster or at least it seemed they did. After the mission when I got the combat report there was no debrief. I pressed the button but nothing happened in the text box or map. 

 

Pat, it looks like you've made a lot of progress with this version. Thanks very much for your work on this awesome program. It remains the only way I play this sim.  

 

 

[PatrickAWlson]

@TheSNAFU Parked planes are static objects so will not have anything other than what they have.  

[Jake]

I think but I'm not sure if this question has already been asked regarding the beta. 
Can I continue to fly my old campaigns in Russia with this beta and the markings of the respective aircraft finally change here as well?
I can't find the answer or my eyes are going bad.?
Thank you for this great work!

[Letka_13/Arrow_]

With the latest beta, I am still getting Russian skins without tactical markings for RAF Hurricane MKII in May 1943, 74th Squadron  I hope it can be corrected.

 

Edited October 17, 2022 by Rudolph

[Hotaru_Ito]

1 hour ago, Jake said:

I think but I'm not sure if this question has already been asked regarding the beta. 
Can I continue to fly my old campaigns in Russia with this beta and the markings of the respective aircraft finally change here as well?
I can't find the answer or my eyes are going bad.?
Thank you for this great work!

 

Yes, you can. I've been flying my existing JG51 campaign in Stalingrad and it's working great. As of this second beta, the German blank skins and tactical codes are working fine, at least in the one mission I've flown so far. We even seem to have correct Gruppe codes now. Very cool.