CARRIER FUNCTIONALITIES - Custom carrier...missing arrestor wires textures?

We are trying to replicate the Asobo carrier functionalities to make our own
carriers work… By editing the reference_points.cfg, we were able to have
working arrestor wires for the Super Hornet etc… but they have a very
strange appearance: basically their appearance is a ghostly “semitransparent”
blue with noise… our guess was that there were textures/materials missing.
So we tried by adding: AIRCRAFTCARRIER_METALROPE (albd, norm and comp of
course) to the package… but no luck. What is missing from our carrier to
have them look “right”?

It seems that the problem is also present in the Asobo carrier…

Just a “bump” to this as I have not seen any discussion on this point… there
is a problem in the arrestor wires material, and this affects third party
carriers too. Just in case this can be fixed for SU10…

@FlyingRaccoon Bump

Hello @Indiafoxtecho and @Rotorhead135 My apologies for not answering earlier.
This is an issue on our side, the materials assigned to the cables are
hardcoded. This is tracked and will be investigated. Regards, Sylvain

Stumbled to this post, was seeing about this. Is this documented in the SDK
the editing the reference_points.cfg for this to work for carriers?

Come on guys, please fix this material assignment.

Regards DHS

1 Like

Oct 2023 - The issue persists

Bump in this issue @FlyingRaccoon as it seems to be producing CTDs for some customers. Here are the findings:

  • Customers with AMD Graphics cards (AMD 7800XT test subject) with latest drivers installed

  • MSFS running on DX12
    → When loading any carrier (3rd party or the Landing Challenge), sim freezes and CTDs, but sounds keep running until the sim is manually closed through the task manager.

  • MSFS Running on DX11
    → Sim doesn’t crash at any carrier, 3rd party or landing challenge

  • On our carriers, after removing the stock Asobo arrestors, and running on either DX12 or DX11
    → Sim doesn’t crash

There seems to be a correlation here - Asobo arrestors and DX12 are producing CTDs in a number of systems running AMD graphics.

1 Like

@FlyingRaccoon Bump on this issue. Unfortunately, we have not gotten any response and this issue is affecting some of our customers.

@FlyingRaccoon Hello, is there maybe an update on this issue ? the CTD’s keep persisting with DX12 and AMD Cards due to this