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

MiG-15bis: Values out of range #387

Open
charliefoxtwo opened this issue Oct 8, 2023 · 4 comments
Open

MiG-15bis: Values out of range #387

charliefoxtwo opened this issue Oct 8, 2023 · 4 comments

Comments

@charliefoxtwo
Copy link
Member

charliefoxtwo commented Oct 8, 2023

NS-430

Util.lua: value -1.000000 is too small for NS430:NS430_COM_FLIP_FLOP (address 1536 mask 8)

MiG-15bis

Util.lua: value 131070.000000 is larger than max 65535 for MiG-15bis:AIR_DILUTER (address 9252 mask 65535)
Util.lua: value -14440.000000 is too small for MiG-15bis:PANELS_LIGHT (address 9270 mask 65535)
Util.lua: value -65535.000000 is too small for MiG-15bis:ENGINE_STOP (address 9274 mask 65535)
Util.lua: value -1.000000 is too small for MiG-15bis:MACH (address 9382 mask 65535)
Util.lua: value -1.000000 is too small for MiG-15bis:THROTTLE_FRICTION (address 9216 mask 4096)

FIXED AIR_DILUTER

Range is set to { -1, 0 } but should likely be { 0, 1 }

FIXED PANELS_LIGHT

Range is set to { 0.23, 0.82 } but should likely be { 0.1, 0.9 }

ENGINE_STOP

Default is set to -1 in dcs luas and actual range is 0 to 1. Not much we can do here?

FIXED MACH

Seems to be a rounding issue - value starts ever so slightly below 0.12.

FIXED THROTTLE_FRICTION

This control is a tumb in bios, but should be a potentiometer.

DCS-BIOS.log

@jdahlblom
Copy link
Contributor

jdahlblom commented Jan 2, 2024

Just checked this and there is only the ENGINE_STOP being reported now and insight shows it is defaulted to -1 at start. When moved it is within range 0 - 1. Damn hard control to see in the cockpit.

@charliefoxtwo
Copy link
Member Author

Yeah these are just bugs in the dcs initialization I believe. I wonder if ED would fix them if we reported them... Probably not lol

@jdahlblom
Copy link
Contributor

We should mark them all in red as this, maybe some official DCS person would notice.

@charliefoxtwo
Copy link
Member Author

I suspect it's just very low on their priority list as nothing in the game itself is actually broken, just data export is slightly incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants