Notes |
|
(0006974)
|
Griggs
|
2017-11-05 16:23
|
|
|
|
(0006995)
|
Griggs
|
2017-11-10 10:22
(edited on: 2017-11-10 10:23) |
|
this is really easy to fix actually:
-for BRDM-2: in rhsgref_BRDM2 in class ViewPilot
initFov = 0.7;
minFov = 0.42;
maxFov = 0.85;
-for BTR-60/70/80: in rhs_btr_base in class ViewPilot
initFov = 0.7;
minFov = 0.3;
maxFov = 1.0;
-for BTR-80A: in rhs_btr80a_msv in class ViewPilot
initFov = 0.7;
minFov = 0.7;
maxFov = 0.7;
-for T-80B: in rhs_tank_base in class CommanderMG in class OpticsIn
initFov = "0.7/1.2";
minFov = "0.7/1.2";
maxFov = "0.7/1.2";
-for T-80BV: in rhs_t80bv in class CommanderMG in class OpticsIn
initFov = "0.7/1.2";
minFov = "0.7/1.2";
maxFov = "0.7/1.2";
-for T-72B: in rhs_a3t72tank_base in class CommanderMG in class OpticsIn
initFov = "0.7/1.2";
minFov = "0.7/1.2";
maxFov = "0.7/1.2";
BUT as far as I know all these parameters need to be
initFov = "0.7"; (or 0.75, as in infantry, idk that one for sure)
minFov = "0.25";
maxFov = "1.1";
In case of balance I need to admit that there are no such mistakes in USAF vehicles.
|
|
|
|
thing is that those params affect output of "zoom" UI element. Some of the scripts are relaying on it and that's the reason why it's made this way. There is workaround for that but I didn't have time to apply it everywhere |
|
|
(0006997)
|
Griggs
|
2017-11-10 12:16
|
|
oh... okay, I alse had spotted same zoom mistake on M1 Abrams Loader slot, just in case |
|