POH 0.8.0-Problem

[nacy]

Problem red or blue?

[BlackWolf]

Thanks.

Unfortunately is a known problem. Because of the size of POH (4x times the normal), the code of Falcon does not create correctly the occupy map.

If you want to change this map you will have to use Mission Commander or TacEdit.

We tried to come up with a solution but no luck.

Enviado desde mi Aquaris M5 mediante Tapatalk

[Cloud 9]

Falcas said a while back that he knows how to fix this for MC, but has yet to accomplish it?? Maybe someday?

C9

[Fresco]

Yes, he has already fixed it in MC

[Cloud 9]

@Fresco:

Yes, he has already fixed it in MC

If it’s fixed in MC then how come it’s not in the game??

C9

[Decimalminimal]

@Cloud:

If it’s fixed in MC then how come it’s not in the game??

C9

BMS as it own mysteries mate. Yep only MC can deal with this situation for now.

[nacy]

@BlackWolf:

Thanks.

If you want to change this map you will have to use Mission Commander or TacEdit.

Enviado desde mi Aquaris M5 mediante Tapatalk

I do not use Mission Commander, let alone TacEdit.

[BlackWolf]

@nacy:

I do not use Mission Commander, let alone TacEdit.

Then you will have to rely on someone else to change your occupation map.

Enviado desde mi Aquaris M5 mediante Tapatalk

[Mystic_J]

Albacete AB ramp start points (small pt) are very close to each other, although in editor they do seem fine placed. This is due to the fact that all the taxi and small pt have max height, width and length values of zero (0) instead of 10000. If you import an objective, by default these values are zeroed. Other airbases have the same problem too.

[Nuno Santos]

@Mystic_J:

This is due to the fact that all the taxi and small pt have max height, width and length values of zero (0) instead of 10000.

Thanks for the feedback, Mystic.
Could you elaborate a bit more on this? I’m not sure I fully understand the problem.

[Mystic_J]

Check every customized airbase in POH and make sure that all the pt (taxi pt, small pt, large pt, AAA pt, SAM pt, etc.) have the value of 10000. Use Ctrl+A to highlight them all and change the value to 10000

[Nuno Santos]

Thanks, mate.
The procedure is clear, what I didn’t get is what the “10000” values means in terms of pt behaviour.

Based on your explanations, I believe that they became all “0” when we updated all the DB from 4.32 to 4.33, so this bug must be old.

We probably have the same issues in the seaports, but I’ll have to check.

Thank you

[Joe Labrada]

@Mystic_J:

Albacete AB ramp start points (small pt) are very close to each other, although in editor they do seem fine placed. This is due to the fact that all the taxi and small pt have max height, width and length values of zero (0) instead of 10000. If you import an objective, by default these values are zeroed. Other airbases have the same problem too.

@Mystic_J:

Check every customized airbase in POH and make sure that all the pt (taxi pt, small pt, large pt, AAA pt, SAM pt, etc.) have the value of 10000. Use Ctrl+A to highlight them all and change the value to 10000

Thanks a lot for the report and the solution!!!

[Jackal]

Good morning, Gentlemen.

Should I guess that this issue would be fixed in a future patch or something like, then?
I’m asking this also because, to be honest, I wouldn’t be able to do that for myself…

With best regards,

[Nuno Santos]

Easy fix, not to worry, mate

[Arty]

@Nuno:

Thanks, mate.
The procedure is clear, what I didn’t get is what the “10000” values means in terms of pt behaviour.

Based on your explanations, I believe that they became all “0” when we updated all the DB from 4.32 to 4.33, so this bug must be old.

We probably have the same issues in the seaports, but I’ll have to check.

Thank you

Here u r m8:

https://www.benchmarksims.org/forum/showthread.php?23664-How-to-s-on-converting-your-4-32Theaters-to-4-33&p=340643&viewfull=1#post340643

@biker:

Hi Dave,

pretty much all wrong.

The new *.PDX file holds the new extended PD data, just like Switch told you…

Extended PD data means:

• Z -> Lifting the point above terrain level (e.g. on a pedestal) -> Spawning ACs, Helis or vehicles at that Z level is not yet implemented
• Max Height -> Code does check if AC can fit into this parking point (e.g. if a HAS has limited height)
• Max Width -> Code does check if AC can fit into this parking point (wing-span)
• Max Length -> Gues what
• Root Idx -> We now do support taxiway branches (ATM only from branch into the main taxi trunk)
• Branch Idx -> Not yet supported

Little vid for the explanation of the taxiway branches:

Finally there is no need to copy this file into your theater (if you do so, all your modifications on PD will be lost).
If it does not exist, it will be generated if you use BMS Editor (start it, select your theater, restart, open any objective and then save to database).

In the MonoLogs you also can see if the standard or extended data is used…

Hope this helps.

BTW because of the missing *.PDX it never should crash, we then use old *.PD file with default values for the new variables!!!

Cheers
Biker

[Nuno Santos]

Well, I guess I must have skipped a few classes along the graduation course… hehehe

As usual, thank you Arty for pointing in the right direction

[Arty]

well u didn’t missed anything…
All those are in the monster black Falcon bible…

The damn manual that we all theater developers use and no one is devoting the time to write it down and end it after 7 lives… :lol:

I must add it to the hot list for future reference.

[nacy]

@BlackWolf:

Thanks.

If you want to change this map you will have to use Mission Commander

Hello.
You can do a tutorial with Mission Commander?

[Dracfalcon]

When I contact AWACS or Wingman, I only get the written response…no verbal. Also, I have to use the COM1 button to turn the volume down for “Victor”. COM2 button doesn’t seem to do anything. Anyone else have this issue? Thanks