Game version 5.002 discussion: Churchill IV, Tactical Codes, New Propellers, DVD for everything.

[Regingrave-]

20 минут назад, Snoop_Hogg сказал:

I've experienced it both ways (skin applies to whole squadron or just player aircraft) in both the advanced quick missions and the basic quick missions. So whichever way it's "supposed" to work isn't working consistently. It could be I just happen to choose the skin that is being classed as the default for that squadron randomly? Maybe I need to test it further but I definitely was finding yesterday that sometimes my squadron was in the skin I chose and sometimes they were in 'default' skin.

 

Will AQM change so that your squadron isn't always in the default skin? Is that a bug? Seems odd that when I play a mission on the D-Day/post D-day Normandy map the allied planes don't have invasion stripes.

In QM the skin applied to the group, in AQM — to player's plane only. If you encounter something different — please send me a generated mission (_gen.mission) and mgen.log from /data/,  make sure that logging is enabled in the startup.cfg (mgenlog = 1).

 

What allied planes?

[Snoop_Hogg]

6 minutes ago, Regingrave said:

In QM the skin applied to the group, in AQM — to player's plane only. If you encounter something different — please send me a generated mission (_gen.mission) and mgen.log from /data/,  make sure that logging is enabled in the startup.cfg (mgenlog = 1).

 

What allied planes?

Will experiment with it more today, it's possible it was just QM Vs AQM and I just somehow didn't make that connection! ? (But I'm pretty sure that's one of the first things I ruled out)

 

Is that intended behaviour for AQM though? Or is that a bug that will be fixed?

[Deicide]

4 hours ago, Regingrave said:

For custom skins we'll fix that later, in the next update.

 

Is that a career? What date and squadron is that? Do you have _gen.mission left?

  Reveal hidden contents

 

Yes, yes if you tell me where to find it

P38 398th?

Edited October 13, 2022 by Deicide

[Regingrave-]

11 минут назад, Deicide сказал:

Yes, yes if you tell me where to find it

/data/missions/, but only if you didn't generated any other missions after that.

 

1 час назад, Snoop_Hogg сказал:

Is that intended behaviour for AQM though? Or is that a bug that will be fixed?

Yes, that's made deliberately, AQM is intended for more historical scenarios, so the whole squad in the unique skins would be inappropriate for the mode.

[Elem]

2 hours ago, Regingrave said:

The symbols could be there from the previous mission, before the update. Did you played any mission, or just loaded the game?

No, that is immediately after a career mission using the Fw-190A-8. I have done several missions since the update and it's the same each time. Here's another...

 

[Denum]

I think the obvious solution is to stick with official skins for most cases.

 

Haven't had any issues at all, I'm sure they will add more when relevant also. 

 

 

[Regingrave-]

10 минут назад, Elem сказал:

No, that is immediately after a career mission using the Fw-190A-8. I have done several missions since the update and it's the same each time. Here's another...

Is that a custom (user-made) skin? For these we didn't fixed anything yet.

[Deicide]

1 hour ago, Regingrave said:

/data/missions/, but only if you didn't generated any other missions after that.

 

 

Its the original, I did not play again afterwards. Its 20mb, let me know where/how to send it and I will



 

Edited October 13, 2022 by Deicide
PM SENT WITH FILE DOWNLOAD LINK

[JG4_Widukind]

Hi Devs.

Only a Question, will u fix older Bugs befor BON is complet?

here for example my post from 2021.(Focke Wulf A6 Center and Wing bomb and A8 Wing Bombs BOMB Drop Mode is wrong)

 

Edited October 13, 2022 by JG4_Widukind

[Snoop_Hogg]

1 hour ago, Regingrave said:

Yes, that's made deliberately, AQM is intended for more historical scenarios, so the whole squad in the unique skins would be inappropriate for the mode.

Should that not be up to the player? Even if it's restricted to generic skins, I would like to have, for example, My Spitfire squadron with invasion stripes if I'm playing a mission on/post D-Day? Or perhaps could the default skins be changed to be appropriate for the map at least (similar to winter skins on winter maps)?

 

2 hours ago, Regingrave said:

In QM the skin applied to the group, in AQM — to player's plane only.

I think this might indeed be what it was, having just had a quick test now couldn't replicate it - so I apologise, but could have sworn yesterday that I was getting skins applied to the whole group in AQM and vice versa.

 

I'm still getting Allied squadrons with just generic yellow numbers on the sides, in AQM and in career - if I'm escorting or being escorted.

[VBF-12_Stick-95]

47 minutes ago, Denum said:

I think the obvious solution is to stick with official skins for most cases.

 

Haven't had any issues at all, I'm sure they will add more when relevant also. 

 

 

 

NOT

[Denum]

Just now, VBF-12_Stick-95 said:

 

NOT

Unfortunately you can't start adding stuff to a product yourself and expect it to work perfectly.

 

It's silly to even expect that.

 

 

[Elem]

1 hour ago, Regingrave said:

Is that a custom (user-made) skin? For these we didn't fixed anything yet.

Yes, in this case, but it happens with any skin, including default. After any mission in any career, the tactical markings are overlaying the default when back in the hanger. They remain there even after restarting.

[Snoop_Hogg]

Have also had in AQM multiple allied squadrons with the same side code, as if it's just generated one code for my squadron and one code for all allied squadrons. I was flying mosquitoes on bridge bombing mission, Normandy (post D-Day) My Tempest escort and a pair of USAAF P-47-D28s were both wearing cream JJ side codes (I can't even see cream as an option for P-47s so I don't know what's going on there!) I've had this a couple of times. 

[Regingrave-]

26 минут назад, Elem сказал:

Yes, in this case, but it happens with any skin, including default. After any mission in any career, the tactical markings are overlaying the default when back in the hanger. They remain there even after restarting.

I can't reproduce your problem with any of the official skins. What plane and career is that?

Please send me your _gen.mission where the issue appears.

[Snoop_Hogg]

the _gen.mission files are too large to attach here there's a max size of 5MB - where should we send them?

The relevant bit from the _gen.mission file, I guess, is these two aircraft were generated in the same mission (this is a pretty common configuration, if you're doing a bombing mission you have an escort squadron, and sometimes there's a couple of planes flying about doing CAP or whatever):

 

USAAF P-51D escort squadron, cream (ie RAF) tactical codes DV

Spoiler

Plane
{
  Name = "";
  Index = 6576;
  LinkTrId = 6577;
  XPos = 113904.320;
  YPos = 500.000;
  ZPos = 137453.062;
  XOri = 0.00;
  YOri = 187.66;
  ZOri = 14.80;
  Script = "LuaScripts\WorldObjects\Planes\p51d15.txt";
  Model = "graphics/planes/p51d15/p51d15.mgm";
  Country = 103;
  Desc = "";
  Skin = "";
  AILevel = 4;
  CoopStart = 0;
  NumberInFormation = 0;
  Vulnerable = 1;
  Engageable = 1;
  LimitAmmo = 1;
  StartInAir = 0;
  Callsign = 73;
  Callnum = 1;
  Time = 60;
  DamageReport = 50;
  DamageThreshold = 1;
  PayloadId = 0;
  WMMask = 1;
  AiRTBDecision = 1;
  DeleteAfterDeath = 1;
  Spotter = -1;
  Fuel = 1;
  TCode = "DVA";
  TCodeColor = "666";
}

 

Pair of USAAF P-38s, again with cream DV tactical codes

Spoiler

Plane
{
  Name = "";
  Index = 6613;
  LinkTrId = 6614;
  XPos = 123718.562;
  YPos = 4000.000;
  ZPos = 129066.039;
  XOri = 0.00;
  YOri = 180.00;
  ZOri = 14.80;
  Script = "LuaScripts\WorldObjects\Planes\p38j25.txt";
  Model = "graphics/planes/p38j25/p38j25.mgm";
  Country = 103;
  Desc = "";
  Skin = "";
  AILevel = 4;
  CoopStart = 0;
  NumberInFormation = 0;
  Vulnerable = 1;
  Engageable = 1;
  LimitAmmo = 1;
  StartInAir = 0;
  Callsign = 12;
  Callnum = 1;
  Time = 60;
  DamageReport = 50;
  DamageThreshold = 1;
  PayloadId = 0;
  WMMask = 1;
  AiRTBDecision = 1;
  DeleteAfterDeath = 1;
  Spotter = -1;
  Fuel = 1;
  TCode = "DVA";
  TCodeColor = "666";
}

 

[Regingrave-]

22 минуты назад, Snoop_Hogg сказал:

the _gen.mission files are too large to attach here there's a max size of 5MB - where should we send them?

The relevant bit from the _gen.mission file, I guess, is these two aircraft were generated in the same mission (this is a pretty common configuration, if you're doing a bombing mission you have an escort squadron, and sometimes there's a couple of planes flying about doing CAP or whatever):

Use Google Drive or other cloud services, you can send the link in PM.

[Snoop_Hogg]

I think what might have happened here is that for RAF P-51Bs "DV" would indeed be a valid squadron code (129 sq) somehow that's been called up for USAAF P-51Ds and then it's also been applied to the other non-player squadron (guessing that's a second, related issue)

[Snoop_Hogg]

4 minutes ago, Regingrave said:

Use Google Drive or other cloud services, you can send the link in PM.

Cheers - PM'd you

 

I'll keep an eye out for the yellow number bug I was experiencing as well

[VBF-12_Stick-95]

1 hour ago, Denum said:

Unfortunately you can't start adding stuff to a product yourself and expect it to work perfectly.

 

It's silly to even expect that.

 

 

 

There are thousands of custom skins that are available to the community.  They have been around since the beginning in 2014.  There's been no problem since then using them easily.  Many in the community fly as squads with specific skins for each pilot.  It is still workable to have the custom skin show properly, it's just a PITA since the update and needs fixing, not ignoring.

[tbauchot]

Hello,

Thank you very much for this big update, but the chalk cliffs of "Cap Blanc-Nez" are still absent !

You promised me to remedy this, but obviously this project has been forgotten !
So, I would be very grateful if you would be kind enough to relaunch this request. ?

Best regards , Thierry.

[Denum]

24 minutes ago, VBF-12_Stick-95 said:

 

There are thousands of custom skins that are available to the community.  They have been around since the beginning in 2014.  There's been no problem since then using them easily.  Many in the community fly as squads with specific skins for each pilot.  It is still workable to have the custom skin show properly, it's just a PITA since the update and needs fixing, not ignoring.

 

Again, even if the community did it. It's not their responsibility to drop everything and address it. 

 

You make mods work with the game, the game has no responsibility to be made to work with mods imo. 

 

Perhaps skinners will need to avoid tactical codes on the aircraft skins in the future. 

 

If I select official skins with any numbers on them I haven't had anything applied to my aircraft that shouldn't be.

[RNAS10_Oliver]

Quote

Perhaps skinners will need to avoid tactical codes on the aircraft skins in the future.

?

 

I must be misunderstanding that sentence because what am reading there is nuts.

[Elem]

1 hour ago, Regingrave said:

I can't reproduce your problem with any of the official skins. What plane and career is that?

Please send me your _gen.mission where the issue appears.

My apologies! It does NOT happen with the default skin as that is the only "official"  skin that accepts the codes, and the others are not affected, so it is only user made skins, which is all I tend to use. The career is a BoM Bf109E-7, but it happens in all my careers using user made skins.

[Regingrave-]

6 минут назад, Elem сказал:

My apologies! It does NOT happen with the default skin as that is the only "official"  skin that accepts the codes, and the others are not affected, so it is only user made skins, which is all I tend to use. The career is a BoM Bf109E-7, but it happens in all my careers using user made skins.

The issue with custom skins is fixed, will be in the next update.

[354thFG_Leifr]

43 minutes ago, tbauchot said:

Hello,

Thank you very much for this big update, but the chalk cliffs of "Cap Blanc-Nez" are still absent !

You promised me to remedy this, but obviously this project has been forgotten !
So, I would be very grateful if you would be kind enough to relaunch this request. ?

Best regards , Thierry.

 

I thought something looked a little 'off' with that part of the Calais coast, and the bloody chalk cliffs are missing!

[ilmavoimat]

I noticed that the P8 compass in the Churchill works as it should i.e. a magnetic compass, can the dev team now revisit the P8 in the British cockpits to make it work correctly in the not too distant future?

[Rothary]

I like the new spinning prop effect, but it does result in the spinner often looking awfully slow, in some cases I'd say quite ruining the visual effect its paint design would be expected to have

 

 

[ITAF_Rani]

The update is stunning,super great job Devs, many thanks !!

Edited October 13, 2022 by ITAF_Rani

[Denum]

50 minutes ago, RNAS10_Oliver said:

?

 

I must be misunderstanding that sentence because what am reading there is nuts.

 

Doing historical skins with the codes left blank so the in-game tactical codes work with it?

That's not nuts. It could have been the reality. 

 

Making the main product work is the primary concern. Third party skins don't fall under that envelope. That's just how it is. 

Edited October 13, 2022 by Denum

[RNAS10_Oliver]

1 hour ago, Denum said:

 

Doing historical skins with the codes left blank so the in-game tactical codes work with it?

That's not nuts. It could have been the reality. 

 

Making the main product work is the primary concern. Third party skins don't fall under that envelope. That's just how it is. 

 

It's nuts (again unless I'm misunderstanding something) because it's not feasible. You're not going to end up with accurate representations of those historical aircraft through doing that. The systems understandably too limited and the range of markings on historical aircraft are too varied. The devs themselves have acknowledged that fact themselves both in the patch notes and in this thread. To suggest that skinners (and devs) should make historical skins but leave out the codes is basically just suggesting that they should not make historical skins IMHO.

 

Go ahead and show me these in game using just blank skins and the tactical markings tech.

 

Spitfire Vb

Spoiler

 

Bristol Fighter

Spoiler

 

Bf 109 K4

Spoiler

 

Both the devs and skinners have purpose made blank skins that are compatible with the tactical markings tech. That's where the markings tech should end up being used on and not on top of historical custom skins. I'm fairly sure the devs have not intended the tech to outright replace custom historical skins.

Edited October 13, 2022 by RNAS10_Oliver

[Zeev]

Yet again new update for the tactical numbers but no explanation how to use it.
Its already third update for this feature yet I cannot understand how to access this feature.

Improve the ui ux of the game 

 

All the other additions are a welcome change. 

Edited October 13, 2022 by Zeev

[LukeFF]

28 minutes ago, Zeev said:

Yet again new update for the tactical numbers but no explanation how to use it.
Its already third update for this feature yet I cannot understand how to access this feature.

 

The codes are right there in the same place you select your skin. 

[VBF-12_Stick-95]

2 hours ago, Denum said:

 

Again, even if the community did it. It's not their responsibility to drop everything and address it. 

 

You make mods work with the game, the game has no responsibility to be made to work with mods imo. 

 

Perhaps skinners will need to avoid tactical codes on the aircraft skins in the future. 

 

If I select official skins with any numbers on them I haven't had anything applied to my aircraft that shouldn't be.

To compare a custom skin to a game mod is a leap of logic. 

I'm sure all skinners, who jointly spend thousands of hours free of charge to bring historic liveries to IL-2 aircraft for the community, will heed your wisdom and comply.
 

[VBF-12_Stick-95]

43 minutes ago, LukeFF said:

 

The codes are right there in the same place you select your skin. 

 

True enough for MP.  Offline is another matter.  First you have to select an Official Skin of the nationality that you want to fly, along with your load out.  After clicking Start you have to go into "Plane" Setup to make changes to a custom skin and remove/change TAC Codes.

If only it could be like MP where you make all your selections for plane mods, skin, TAC Codes, etc. before clicking Accept.  This would eliminate the need to make adjustments in the "Plane" Setup every time prior to spawning.

Don't get me wrong, love the implementation of TAC Codes, just not the way it's currently handled offline.  Hopefully it will change.

[Denum]

1 hour ago, VBF-12_Stick-95 said:

To compare a custom skin to a game mod is a leap of logic. 

I'm sure all skinners, who jointly spend thousands of hours free of charge to bring historic liveries to IL-2 aircraft for the community, will heed your wisdom and comply.
 

 

If you have to add it to the game it's a mod. 

 

How much time is spent on it is irrelevant. 

 

If a future update made all the existing user created skins no longer work because of new technology or programming they likely would say "sorry but thats the way it is" and that would be that. 

 

 

 

Edited October 13, 2022 by Denum

[VBF-12_Stick-95]

27 minutes ago, Denum said:

 

**snip**

 

If a future update made all the existing user created skins no longer work because of new technology or programming they likely would say "sorry but thats the way it is" and that would be that.

 

 

Well I have faith they would work with their customers, not just discard precious content.  That is unless they don't need their customers in the future in which case your logic is sound.

[Roland_HUNter]

Occasionally, the Peshka gunner will shoot or resurrect after injury or loss of life, and even after the loss of life, when the crew of the plane was about to bail out, the dead gunner bailed out alive.
There have also been cases where he did not revive, but kept firing.

This happened on the first test where I didn't think this bug really existed, so I didn't record it.

At this point, for some reason, I can't recreate the problem.

Anyone have any idea what might be causing this?
Or, does this error also occur in multiplayer mode?

 

[Avimimus]

Q: Are there any plans to rework the damage textures for the Flying Circus Vol.1 aircraft?

 

I'm finding it very hard to spot the DVD due to all of the 'fake' bullet holes... and honestly, I don't think those damage textures are needed anymore. It would seem that the moderate damage texture states could probably be completely removed now. Could that be a reasonable medium term solution?

[RNAS10_Oliver]

Just now, Avimimus said:

Q: Are there any plans to rework the damage textures for the Flying Circus Vol.1 aircraft?

 

I'm finding it very hard to spot the DVD due to all of the 'fake' bullet holes... and honestly, I don't think those damage textures are needed anymore. It would seem that the moderate damage texture states could probably be completely removed now. Could that be a reasonable medium term solution?

 

Unfortunately, they are still needed. As the DVD tech does not function for anyone on FC in multiplayer as rifle calibre rounds are excluded from DVD tech there due to network usage. So the original damage textures are still at the moment required.