Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typhoon Sub breaking surface at mission start #190

Open
Jesterv2 opened this issue May 6, 2020 · 5 comments
Open

Typhoon Sub breaking surface at mission start #190

Jesterv2 opened this issue May 6, 2020 · 5 comments
Assignees
Labels
- Verified Minor Bug- Category: Indicates that this issue is a minor bug that needs to be resolved. Future Release Indicates that this issue is planned for implementation at a later date.

Comments

@Jesterv2
Copy link

Jesterv2 commented May 6, 2020

If you have an encounter in the campaign with surface ships and the starting depth is 50ft, then the sub will stick its sail out and you'll be detected immediatly.

How can i fix that?

@T40-95
Copy link

T40-95 commented May 6, 2020

If I remember, the Typhoon’s masts still deploy at 65ft deep. You could also look through the code and look for something that says “Typhoon StartingDepth = 50” and change that to 65? I wouldn’t know

@Jesterv2
Copy link
Author

Jesterv2 commented May 6, 2020

Thanks! I'll see if I can find anything like that

@Jesterv2
Copy link
Author

Jesterv2 commented May 6, 2020

couldnt find anything of the likes. i did find the parameter ''SubmergedAt= 0.25'' but changing that didnt seem to do anything.

@ramius-99 ramius-99 self-assigned this May 6, 2020
@ramius-99 ramius-99 added - Verified Minor Bug- Category: Indicates that this issue is a minor bug that needs to be resolved. Future Release Indicates that this issue is planned for implementation at a later date. labels May 6, 2020
@ramius-99
Copy link
Collaborator

I thought i'd fixed this long ago, guess not.
It will be fixed for next batch of updates.

@Jesterv2
Copy link
Author

Jesterv2 commented May 6, 2020

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Verified Minor Bug- Category: Indicates that this issue is a minor bug that needs to be resolved. Future Release Indicates that this issue is planned for implementation at a later date.
Projects
None yet
Development

No branches or pull requests

3 participants