Jump to content


Photo

Some Static Aircraft not showing up...


  • Please log in to reply
24 replies to this topic

#1 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 30 July 2016 - 04:22 PM

Guys I need some help with this...

 

Some active unit static aircraft are not showing up in game and I think I have found the issue:

 

Bf 109F-0 active on a given airfield

Static aircraft attribute =  vehicles.planes.UltimateBf109Static$BF_109F0

 

the static aircraft naming convention of some modded aircraft are different from the original eg = vehicles.planes.Plane$BF_109F2

 

Is there a way to fix this so that all static aircraft show up regardless of naming convention?

 

Something like vehicles.planes.*$BF_109F2 would solve this -if it's a coding thing?



#2 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 02 August 2016 - 04:35 AM

Unfortunately it's something I haven't got around to addressing.  I either need to add another column to the class.dcg file or add another data file.  Maybe just a file for exceptions....

 

You could try and make a folder in the skins for it and then modify the id in the class.dcg to match.



#3 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 02 August 2016 - 12:25 PM

Thanks for the response Paul!

 

I like the idea of exceptions file. I am not quite sure I understand what you mean :) I have a skin folder for the BF_109F0 which works. DCG just isn't giving me the static model parked on the airfield.



#4 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 03 August 2016 - 04:06 AM

What I'm saying is make a new folder with the static model's id as its name.  Then put that same id in the class file in the column for the skin id.



#5 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 03 August 2016 - 05:34 AM

Never mind, my idea won't work if it's because the change is before the planes name.

 

I'll have to make an exception file.



#6 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 03 August 2016 - 04:26 PM

Thanks Paul! :)



#7 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 04 August 2016 - 05:01 PM

Paul - So how does this actually work?

 

Plane$BF_109F0 = UltimateBfStatic$BF_109F0

 

When DCG looks for a class ending in "Plane$BF_109F0", substitute it for "UltimateBf109Static$BF_109F0"?

 

As is, you designed DCG to detect the kind of aircraft stationed at given aerodrome and substitute any static aircraft present in the .mis with the corresponding aircraft stationed there.

 

If I have a vehicles.planes.Plane$BF_109F4 in my mission.mis as a static aircraft at a aerodrome but assigned a vehicles.planes.UltimateBf109Static$BF_109F0 to that airfield how does the exclusion file help DCG do it's magic?

I did a test a got a DCG error last night - I am at work so I can't provide any details.



#8 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 04 August 2016 - 11:16 PM

Data removed.



#9 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 05 August 2016 - 04:11 AM

Plane$BF_109F0 = UltimateBfStatic$BF_109F0

 

When DCG looks for a class ending in "Plane$BF_109F0", substitute it for "UltimateBf109Static$BF_109F0"?

 

That's how it's supposed to work.  Of course, one thing I forgot to add was when it gets destroyed and appears in the event log, what to do with it.  :unsure:



#10 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 05 August 2016 - 04:12 AM


These are all the non uniform static entries. DCG crashes and ask for the $BF_109F4.

 

Is this after the mission?  Or is this pulling non uniform statics from a template mission to create the campaign?



#11 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 05 August 2016 - 01:17 PM

The game crashes during mission creation - I tab into task manages and see that DCG failed and get a screen with "$BF_109F4" (...which is a uniform static).

For some reason after DCG crashes and I close it via task manager - IL-2 kicks me to the online screen - which it hasn't ever done before.



#12 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 06 August 2016 - 05:48 AM

Thanks Paul - beta6 has got me up and running again. I tried to manually change the naming of the static aircraft in the stationary.ini but IL-2 crashed, so I guess your exception file will have to do :(



#13 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 06 August 2016 - 06:31 AM

I need to do more work on it.  Bare with me.



#14 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 06 August 2016 - 02:02 PM

Thank you Paul!



#15 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 08 August 2016 - 11:53 PM

Paul - I updated DCG beta 7 but the staticplanes.dcg isn't doing the trick :(

 

This an excerpt the .mis of the 1st mission generated:

 

[NStationary]
  16_Static vehicles.planes.Plane$BF_109F0 2 107908.77 161819.80 265.12 0.0 de 1
  17_Static vehicles.planes.Plane$BF_109F0 2 108259.51 161915.33 265.12 0.0 de 1
  18_Static vehicles.planes.Plane$BF_109F0 2 108550.53 161783.53 265.12 0.0 de 1
  19_Static vehicles.planes.Plane$BF_109F0 2 108830.47 161889.75 265.12 0.0 de 1

  .

  .

  .

  .

 

This is what's in my staticplanes.dcg:

 

Planes$BF_109F0 = UltimateBf109Static$BF_109F0

 

Thanks for helping out with this SNAFU some aircraft modder have crated by not thinking about the ramifications of not keeping standard IL-2 nomenclature



#16 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 09 August 2016 - 04:13 AM

Dumb question but you have a Bf109F0 in your class.dcg file?



#17 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 09 August 2016 - 02:57 PM

Not a dumb question - yes, and it works (mission generating and skin transfer).

BF_109F0     Mdtt Bf109F0, 1941   de 2 1 1 194001 194112 BF_109F2 Bf-109F-0  none 5000 Meters  410.00 kph  800 km      410.00 kph

Question: In your test, did the staticaircraft.dcg change the entries in the initial .mis mission file?

 

If not, I wonder if the staticaircaft.dcg entries should be reversed?

 

Like so? UltimateBf109Static$BF_109F0 =  Planes$BF_109F0



#18 Lowengrin

Lowengrin

    Advanced Member

  • Members
  • PipPipPip
  • 613 posts

Posted 10 August 2016 - 04:23 AM

Good question.  Because my template missions don't have modded planes, I never considered reversing them.  I'll do some testing and see how it goes.



#19 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 10 August 2016 - 01:06 PM

Thanks! I will test too - can't pry my eyes away from the Olympics :unsure:  



#20 JG7_X_Man

JG7_X_Man

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 10 August 2016 - 11:52 PM

Hey Paul - tried beta8, no dice.

 

The stationary.dcg still creates " xx_Static vehicles.planes.Plane$BF_109F0 2 166245.38 171742.31 235.12 0.0 de 1 1.0 null 1"

 

I edited the staticplanes.dcg switching the positions both ways to no avail.

 

I can manually edit the generated mission yyyymmddX.mis from  xx_Static vehicles.planes.Plane$BF_109F0 to xx_Static vehicles.planes.UltimateBf109Static$BF_109F0 and the aircraft appear in the mission, but

since it isn't not adding the correct name in the stationary.dcg, it doesn't carry over to the next mission.

 

I tried to manually edit the stationary.dcg but they were "x"ed out and replaced with an xx_Static vehicles.planes.Plane$BF_109F0 entry. I hope this isn't frustrating you. :)
 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users