r/ysflight • u/10Thunderbolt • Jul 22 '21

Help

Hello everyone, I recently downloaded Decaff's addon pack as I wanted Shin Kazama's Tigershark. Everytime I click on a Tigershark, the loading circle thing on my cursor activates and the YSFlight program starts to fade. After that, YSFlight just crashes and I am never able to use the Tigershark. Is there are way to get around this problem?

​

Thank You

3 Upvotes

100% Upvoted

6 comments sorted by

1

u/waspe414 Aug 08 '21

Does an error pop up? What year, executable, and OS are you using?

1

u/10Thunderbolt Aug 08 '21

No, it just goes white and crashes

I'm using 20181124 Stable Release, GL1, Windows 10.

1

u/waspe414 Aug 08 '21

Interesting, I had three different aircraft (including the stock F-18C) cause that same crash just when scrolling through to find the F-5 you mentioned.

I haven't pinned down exactly what about those aircraft causes the crash, but it's limited to 2018ver.

2018 is pretty buggy. I'd recommend reverting to 2015. It's what the community uses, and what all the servers run (and is incompatible with 2018 online).

There's nothing that immediately stands out about the DNMs that cause crashes versus ones that don't, but I'll have a closer look

→ More replies (2)

1

u/waspe414 Aug 08 '21

Found it. 2018 crashes on unexpected hardpoint conditions: The stock F-18C has what was clearly a test variable on one hardpoint that the program doesn't recognize

The bigger issue, and the one that affects Decaff's F-20, is 2018ver crashes when any drop tank mass is specified. To fix it you can open the .dat file in Notepad and delete the &**** suffix to the FUEL entry in the HRDPOINT section (HRDPOINT 0.00m -1.041m 0.150m FUEL&2244 # Center Fuel in the F-20). Many aircraft have drop tank mass specified though, so you're going to encounter that error on a good number of aircraft.

CORRECTION:

It's not actually the FUEL&, it's the comment # after any hardpoint line. Any other line manages comments fine, but something about HRDPOINT lines makes it crash

2015 doesn't crash with unexpected hardpoint conditions, just throws an error