Letka_13/Arrow_ Posted February 12, 2023 Posted February 12, 2023 Hello Patrick, I have tested several airfield attack missions in PWCG, but none of them had any destructible objects at the target arfield apart from AAA in Normandy. Nor are there any enemy parked planes placed that could be attacked, there are only trucks at the airfield which are indestructible, this is symptomatic for all attack missions in Normandy that I tested. I am attaching pwc-error log and the last generated mission. Thank you very much for looking at it. PWCG_airfield_attack.ZIP PWCGErrorLog.txt
TimSell75 Posted February 22, 2023 Posted February 22, 2023 (edited) I found some bug in the skin assignments for JG 52 The Skins assigned to II JG52 did not work This seems to be due to "squadronId": 20112052 in the header und "squadId": 20111052 was listed on all the skins. Also all skins had I_JG52 instead of II_JG52 in the name I corrected this and now have correct skins on II JG52 BUT Now the skin assignment on I_JG52 do not work anymore, though the squadron file was unchanged. Do I miss something here? Note: Also the II_JG51.json seems to be not correct, all skins have I_JG52 instead of II_JG51 in the name Edited February 22, 2023 by TimSell75
Nocke Posted February 22, 2023 Posted February 22, 2023 Maybe not an issue, but a question: I have searched through the squadron files, and found only one russian squadron, the 629th Fighter Air Regiment, flying the Spitfire MkIX. All others seem to be flying the MkV until around 1944, and then convert to the Mk14. If I am understanding that correctly, that is, of course ... Wouldn't they convert to MkIX over the channel around 1942/1943, at least some? And could I cause any harm or sideeffect if I just set them to convert to MkIX at some date in the json file corresponding to the squadron in the BoSData/Input/Squadron directory? Thank you!
PatrickAWlson Posted February 22, 2023 Author Posted February 22, 2023 8 minutes ago, 216th_Nocke said: Maybe not an issue, but a question: I have searched through the squadron files, and found only one russian squadron, the 629th Fighter Air Regiment, flying the Spitfire MkIX. All others seem to be flying the MkV until around 1944, and then convert to the Mk14. If I am understanding that correctly, that is, of course ... Wouldn't they convert to MkIX over the channel around 1942/1943, at least some? And could I cause any harm or sideeffect if I just set them to convert to MkIX at some date in the json file corresponding to the squadron in the BoSData/Input/Squadron directory? Thank you! The Spitfire V and IX are considered to be part of the same archtype "spitfire", so the IX will naturally replace the V. The XIV is its own arch type. I did not think that I supplied the XIV to the Russians. If I did that is a mistake.
czech693 Posted February 22, 2023 Posted February 22, 2023 1 hour ago, TimSell75 said: I found some bug in the skin assignments for JG 52 The Skins assigned to II JG52 did not work This seems to be due to "squadronId": 20112052 in the header und "squadId": 20111052 was listed on all the skins. Also all skins had I_JG52 instead of II_JG52 in the name I corrected this and now have correct skins on II JG52 BUT Now the skin assignment on I_JG52 do not work anymore, though the squadron file was unchanged. Do I miss something here? Note: Also the II_JG51.json seems to be not correct, all skins have I_JG52 instead of II_JG51 in the name
TimSell75 Posted February 22, 2023 Posted February 22, 2023 (edited) 54 minutes ago, czech693 said: Yes, it´s the same problem. I also tried to solve it like you, but for some reason fixing the II_JG52.json leads to the circumstance, that the skin assignment for I JG52 is messed up afterwards, though this squadron file was untouched. I tested it vice versa and every time I fix the II_JG52.json, the assignment for I JG52 is broken. I don´t understand the logic but this is the result. So somewere there is still something working in the background... Edited February 22, 2023 by TimSell75
Nocke Posted February 23, 2023 Posted February 23, 2023 2 hours ago, PatrickAWlson said: The Spitfire V and IX are considered to be part of the same archtype "spitfire", so the IX will naturally replace the V. The XIV is its own arch type. I did not think that I supplied the XIV to the Russians. If I did that is a mistake. No, no Mk14 with the russians. But that russian 629th fighter air regiment is the only unit where I found a MkIX explicitly specified in the json file, which is what made me wonder.
Stonehouse Posted February 23, 2023 Posted February 23, 2023 (edited) 2 hours ago, TimSell75 said: Yes, it´s the same problem. I also tried to solve it like you, but for some reason fixing the II_JG52.json leads to the circumstance, that the skin assignment for I JG52 is messed up afterwards, though this squadron file was untouched. I tested it vice versa and every time I fix the II_JG52.json, the assignment for I JG52 is broken. I don´t understand the logic but this is the result. So somewere there is still something working in the background... It can also be due to another squadron json using the same id in the skins area as the one you feel is broken. I haven't rechecked for quite a while but I believe III_JG27 and II_St_G_2 also have issues where the main squad id differs from that nominated in the skin section of the squadron json. Can't guarantee it fixes your issue but worth checking. Edited February 23, 2023 by Stonehouse
czech693 Posted February 23, 2023 Posted February 23, 2023 3 hours ago, TimSell75 said: Yes, it´s the same problem. I also tried to solve it like you, but for some reason fixing the II_JG52.json leads to the circumstance, that the skin assignment for I JG52 is messed up afterwards, though this squadron file was untouched. I tested it vice versa and every time I fix the II_JG52.json, the assignment for I JG52 is broken. I don´t understand the logic but this is the result. So somewere there is still something working in the background... I started a I/JG52 career in PWCGBoS and it pulled up the correct I_JG52 early skin. Go here and get my .json file and paste it in. Make sure to save your original first. https://www.mediafire.com/file/47huj0jh9dl3vnp/I_JG52.json/file
TimSell75 Posted February 23, 2023 Posted February 23, 2023 Thanks for the help czech693! Unfortunately it does not solve the problem. I had no issue with the skin assignment of I JG52 UNLESS I corrected the squadron file for II JG52 like you did. Then it showed correct skins on II JG52 but messes up skins on I JG52 (though this sqaudron file was untouched). So something is going on in the background which I could not figute out yet.
czech693 Posted February 23, 2023 Posted February 23, 2023 What is happening to the skins in I/JG52? Are they defaulting to stock skins?
TimSell75 Posted February 23, 2023 Posted February 23, 2023 7 minutes ago, czech693 said: What is happening to the skins in I/JG52? Are they defaulting to stock skins? Yes PWCG is then using random skins from the default ones.
czech693 Posted February 23, 2023 Posted February 23, 2023 Yeah, that's the hiccup that got me started rooting out the problem with II/JG52 back in December. I just unpacked my 14.1.3 download again and checked I/JG52 squadron.json but it looked okay. Are you using PWCGBoS 14.1.3? Did you download and install Pat Wilson's Me109early and Me109late?
TimSell75 Posted February 23, 2023 Posted February 23, 2023 52 minutes ago, czech693 said: Yeah, that's the hiccup that got me started rooting out the problem with II/JG52 back in December. I just unpacked my 14.1.3 download again and checked I/JG52 squadron.json but it looked okay. Are you using PWCGBoS 14.1.3? Did you download and install Pat Wilson's Me109early and Me109late? Yes the file of I JG52 is ok, the weird thing is, that the skin assignment of I JG52 becomes messed up when you correct the squadron file of II JG52. I never touched I_JG52.json only II_JG52.json. But nevertheless I JG52 then uses random skins instead of the correct ones which it did before. Copying back the original (faulty) II_JG52.json leads to I JG52 using correct sknins again, but then II JG52 is messed up again. So either way, one of the squadrons skin assignment is always messed up.
czech693 Posted February 23, 2023 Posted February 23, 2023 Here's my II_JG52.json file. Paste it in place of the one you have corrected and see if your I_JG52 file then correctly selects Pat Wilson's modified skin files. If it does then the bug is in your II_JG52.json file. https://www.mediafire.com/file/e49pyvd2nwwid6p/II_JG52.json/file
TimSell75 Posted February 23, 2023 Posted February 23, 2023 2 hours ago, czech693 said: Here's my II_JG52.json file. Paste it in place of the one you have corrected and see if your I_JG52 file then correctly selects Pat Wilson's modified skin files. If it does then the bug is in your II_JG52.json file. https://www.mediafire.com/file/e49pyvd2nwwid6p/II_JG52.json/file Thanks for your effort. I have the same result with your file as when I modified the II_JG52.json myself. Now the skin assignment of I JG52 is using random standard skins.
czech693 Posted February 24, 2023 Posted February 24, 2023 One last effort. Put both my I_JG52 and II_JG52 .json files in and see what happens. If it still doesn't work then it's somewhere else in the PWCGBoS.
TimSell75 Posted March 4, 2023 Posted March 4, 2023 On 2/24/2023 at 3:48 AM, czech693 said: One last effort. Put both my I_JG52 and II_JG52 .json files in and see what happens. If it still doesn't work then it's somewhere else in the PWCGBoS. Unfortunately I got the same result as with my edited files. Either one of the squadrons skins is messed up. Thanks anyhow!
Russkly Posted March 5, 2023 Posted March 5, 2023 On 2/11/2023 at 10:52 AM, Russkly said: PWCGErrorLog.txt 2.99 kB · 0 downloads "PWCG could not perform AAR. Unable to find matching logs set for Hurricane 1942-11-18" ErrorReport file is 6Mb (compressed already) and is thus too big to post here. Please advise... Any thoughts, please? I'd hate to think that this career is dead...
PatrickAWlson Posted March 5, 2023 Author Posted March 5, 2023 10 hours ago, Russkly said: Any thoughts, please? I'd hate to think that this career is dead... I need the zip file created from "Report Error".
Russkly Posted March 6, 2023 Posted March 6, 2023 (edited) 14 hours ago, PatrickAWlson said: I need the zip file created from "Report Error". Thanks, Pat. How can I get it to you? It's 6.2Mb even when compressed so too big to attach here. Edited March 6, 2023 by Russkly Sp.
No105_Swoose Posted March 9, 2023 Posted March 9, 2023 Salute! I wonder if you could take a look at a problem I seem to be having with the Spitfire Mark IX in PWCG campaigns? Several AI planes seem to have random, unexplained engine failures followed by crashes. This has happened in several missions. In the attached mission it happened after we had encountered and fought a formation of Bf-110Gs and while on one of the final CAP legs. Maybe it's just my system? But it's frustrating to lose four perfectly good aircraft for no apparently good reason. I really like the Spitfire Mark IX, but will probably transfer to a unit with a different aircraft type to avoid this problem. Thanks. Spitfires Over Normandy 1944-07-03.zip
Varibraun Posted March 9, 2023 Posted March 9, 2023 1 hour ago, No105_Swoose said: Salute! I wonder if you could take a look at a problem I seem to be having with the Spitfire Mark IX in PWCG campaigns? Several AI planes seem to have random, unexplained engine failures followed by crashes. This has happened in several missions. In the attached mission it happened after we had encountered and fought a formation of Bf-110Gs and while on one of the final CAP legs. Maybe it's just my system? But it's frustrating to lose four perfectly good aircraft for no apparently good reason. I really like the Spitfire Mark IX, but will probably transfer to a unit with a different aircraft type to avoid this problem. Thanks. Hi Swoose - I don't think this is a PWCG problem, but something about the way the AI flies some of the Spitfires and killing the engine. I reported it over a year ago and you can follow a bit of the thread below where I was able to get @-DED-Rapidus what he needed as far as tracks for analysis. I am currently flying SpitVs in PWCG BoN and haven't seen it happen yet, so it could be only the later models (I got some good screenshots). You might want to make a report to the Devs in that same thread, but it is discouraging that the problem is still there. I agree that it makes flying a Spit career completely impractical when it is occurring. 1
CartelMonkey Posted March 15, 2023 Posted March 15, 2023 Hey! I'm sure this has been covered but my (admittedly quick) google search did not give me anything recent... Whenever I run JU-52 missions the AI performs terribly. Friendly 52's just spin on the airfield during take-off, and if I engage auto-pilot my plane either crashes into the trees or doesn't follow the mission path. Really want to use PWCG for this plane as it provides a MUCH better experience than normal career mode IMO but so far it doesn't seem to reliable for this aircraft. Is this a known issue or is there something I'm doing wrong?
PatrickAWlson Posted March 15, 2023 Author Posted March 15, 2023 1 hour ago, CartelMonkey said: Hey! I'm sure this has been covered but my (admittedly quick) google search did not give me anything recent... Whenever I run JU-52 missions the AI performs terribly. Friendly 52's just spin on the airfield during take-off, and if I engage auto-pilot my plane either crashes into the trees or doesn't follow the mission path. Really want to use PWCG for this plane as it provides a MUCH better experience than normal career mode IMO but so far it doesn't seem to reliable for this aircraft. Is this a known issue or is there something I'm doing wrong? Can't do anything about those issues. It's the Ai that spins on the field (usually winter - lots of planes do this). Crashing into trees - might be able to pick a more clear airfield but finding just the right field is pretty painful. Following the mission path is a PWCG thing and not AI, but I would need an example of this.
CartelMonkey Posted March 15, 2023 Posted March 15, 2023 1 hour ago, PatrickAWlson said: Can't do anything about those issues. It's the Ai that spins on the field (usually winter - lots of planes do this). Crashing into trees - might be able to pick a more clear airfield but finding just the right field is pretty painful. Following the mission path is a PWCG thing and not AI, but I would need an example of this. Thank you for the response. It's really great how involved you are with your community and I appreciate it. Not sure how to give an example...the mission I ran has since been scrubbed, but the aircraft would lock onto the third waypoint after taking off which was after the objective (dropping cargo). This was while set to auto-pilot...I did notice a green "objective completed" marker after taking off at the start...not sure if that threw off the mission some how.
Dusty926 Posted April 6, 2023 Posted April 6, 2023 Getting an error when attempting to create a German pilot in my FC career. Started it as Entente, and was able to create a French pilot without issue. Region selected and name didn't seem to matter. PWCGErrorLog.txt
PatrickAWlson Posted April 7, 2023 Author Posted April 7, 2023 4 hours ago, Dusty926 said: Getting an error when attempting to create a German pilot in my FC career. Started it as Entente, and was able to create a French pilot without issue. Region selected and name didn't seem to matter. PWCGErrorLog.txt 3.5 kB · 0 downloads Squadron, rank and date?
Dusty926 Posted April 7, 2023 Posted April 7, 2023 2 hours ago, PatrickAWlson said: Squadron, rank and date? I tried it with most of the Jastas I saw available, couldn't get any to work. Same with Rank, but I'll run through the full list of both just to be sure I didn't miss any. Date is 13/06/1917
PatrickAWlson Posted April 7, 2023 Author Posted April 7, 2023 8 hours ago, Dusty926 said: I tried it with most of the Jastas I saw available, couldn't get any to work. Same with Rank, but I'll run through the full list of both just to be sure I didn't miss any. Date is 13/06/1917 Campaigns start on the first of the month. That start date isn't an option. How are you trying to start a campaign with that date? Can you post a picture of your campaign data entry screen? I did start a campaign, using the date dropdown, on 01/06/1917 for Jasta 2 without a problem. I did another one on 01/03/1918 for Boghol 3 without issue. My integration tests create and destroy dozens of campaigns. Usually when campaign creation fails it is tied to a date or a squadron or some other combination of data items. One possibility (my fault for not stating this earlier) - you should delete your old PWCG FC install. This version absolutely will not play nice with remnants of the older version.
Dusty926 Posted April 7, 2023 Posted April 7, 2023 5 hours ago, PatrickAWlson said: Campaigns start on the first of the month. That start date isn't an option. How are you trying to start a campaign with that date? Can you post a picture of your campaign data entry screen? I did start a campaign, using the date dropdown, on 01/06/1917 for Jasta 2 without a problem. I did another one on 01/03/1918 for Boghol 3 without issue. My integration tests create and destroy dozens of campaigns. Usually when campaign creation fails it is tied to a date or a squadron or some other combination of data items. One possibility (my fault for not stating this earlier) - you should delete your old PWCG FC install. This version absolutely will not play nice with remnants of the older version. Sorry, I must've mispoken! The issue isn't starting a campaign as a Central pilot; The problem comes when using the Administer Pilots page to attempt to create a Central pilot when already flying an Entente career. I've deleted all the remaining FC stuff and reinstalled it from scratch, and it's still giving me the same issue.
czech693 Posted April 8, 2023 Posted April 8, 2023 What is the Administer Pilots page? I've create many careers at the same time, both Central and Entente. Also, more than one in either category (ie. two Central careers).
Dusty926 Posted April 9, 2023 Posted April 9, 2023 (edited) Got generated a Scramble mission where all the altitudes were at 0. Also have been experiencing flights continuing to have indecision on where they're going, as well as bombers not dropping their payloads all the time. But whilst I rattle those last two off, the former is the big one. I've attached the mission file here, but if you want anything more from me on it I'll keep my campaign static so as not to lose it. Here's the zip from hitting Report Error. Barely too large for the forums unfortunately: https://www.dropbox.com/s/rbw2o5v0t8e95gr/The Great War Main202304082304777.zip?dl=0 0 Altitude Intercept.zip Edited April 9, 2023 by Dusty926
JG7_X-Man Posted April 9, 2023 Posted April 9, 2023 Help please... I am try to get the dash "-" = "%3b" on all the aircraft in the squadron but I can't seem to figure out. Below is a snippet from .json Squadron file: . . . "unitIdCode": "", "subUnitIdCode": "", "tacticalCodeStyle": -1, "squadronTacticalCodeColorOverride": "BLACK" Does anyone know? I have tired the unitIdCode and subUnitCode but not sure if the syntax was correct.
czech693 Posted April 10, 2023 Posted April 10, 2023 (edited) To the best of my knowledge: UnitIdcode is used for the squadron ID. i.e. 403 Squadron has "unitIdcode": "KH". Goes in front of the national insignia. Look at the .json for 403 Squadron. SubunitIdcode is used for a squadron symbol code. i.e. Gruppe II/JG52 has "subunitIdcode": "-" to use the gruppe symbol. Goes behind the national insignia. Look at the .json for II_JG52. Tactical code style -1 means use the default code style for that aircraft. If using that aircraft for a different nationality you would use a different tactical code number. Look at the .json for 126th Fighter Air Regiment. Uses "tacticalCodeStyle": 2 for Russia. I can't figure out the color override as each of the skins in the .json file has a code color designated. Possibly if it is intended to universally override whatever color is designated in the skin code so that you don't have to individually change them. But, I just used the replace command to change all of them to one color. Edit: Ignore what I wrote. I think I misread you question. You're trying to use the code "%3b" for the subunitIdcode, correct? Have you changed it to read: "subunitIdcode": "%3b" and that didn't work? What does "%3b" represent? I don't see it listed in the German fighter aircraft .txt files. Okay, I found "%3b" in Pat Wilson's tactical code notes. But, my II Gruppe .json's have "-", using the hyphen not "%3b". Edited April 10, 2023 by czech693 1
JG7_X-Man Posted April 10, 2023 Posted April 10, 2023 (edited) @czech693 Thank you for your response! I will validate later today - but I think you are correct Quote SubunitIdcode is used for a squadron symbol code. i.e. Gruppe II/JG52 has "subunitIdcode": "-" to use the gruppe symbol. Goes behind the national insignia. Look at the .json for II_JG52 This maybe what I am looking for. Solved! @czech693 Thank you = the "-" worked! Edited April 11, 2023 by JG7_X-Man
JG7_X-Man Posted April 13, 2023 Posted April 13, 2023 I was looking at making the "taxi from parking takeoff" using the Normandy map but it doesn't seem to work. I created a mission using the Mission Editor using the Normandy and "taxi from parking takeoff" worked. "Taxi from parking takeoff" does work in the Bodenplatte map so I decided to follow the same logic for the Normandy map - but the application failed (i.e. did not launch) I decided to do a side by side comparison of the AirfieldLocations.json from Bodenplatte with the version from the Normandy map and I noticed a major difference in the layout: Altenstadt is from Bodenplatte folder and A-13 Tour en Bessin is from the Normandy folder @PatrickAWlson could this be a reason why taxing from parking takeoff doesn't work using the Normandy map?
PatrickAWlson Posted April 13, 2023 Author Posted April 13, 2023 Taxiing is not supported on the Normandy map.
Firefly_Scout Posted April 14, 2023 Posted April 14, 2023 Hi there, I am new to PWCG (v 14.1.4), still getting used to it ... I like it quite a bit! ? I have flown several missions by now in two Soviet bomber careers with me as the flight leader and keep seeing the two following bugs in every mission: My escort flight keeps circling at the rendevouz point, no matter how close I fly by them. They keep circling there until the end of the mission. What am I doing wrong? Do they need a special order to follow my bomber flight? I am not credited with any hits on the targets even if I see that I have destroyed the bridge or parked airplanes on the enemy airfield. I am sure I hit the right target as per mission briefing! I would be happy if someone had a look on the error log attached below. That mission includes the forever-circling fighter squadron and I have seen in my recorded video that I did hit the bridge target with my fourth bomb but AAR credited me with no target destroyed. That is what happens in every mission: circling escort flight and no destroyed targets credited. Am I doing anything wrong? Nikoloz Tevzadze202304141704654.zip
BB-Madman Posted April 14, 2023 Posted April 14, 2023 Hi Pat, Error during AAR processing. Got this last night. Uninstalled the older version that I was running and installed the newest version. Got it again on my first mission. Thanks. Sorry, can't upload the .zip file.....too big. I searched and found 1 other reference to this from last October (I think) in this thread. PWCGErrorLog.txt
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now