Correct left rotor translation which was wrong only for object viewer. #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently saw that V-22 left rotor position was wrong in model viewer (Free flight -> Aircraft -> Details...).
0.0 0.0 80.0
After some tests and look at sar2 code, I understood that moving parts as rotor, gears, ailerons, doors, and so on..., are not drawn in model viewer as in game.
In game, parts are drawn using rotor_new, landing_gear_new, aileron_left_new, rescue_door_new, and so on... parameters, but in model viewer, they are only drawn with translate and rotate parameters. It is why x, y, z and h, p, b rotor_new values are always 'copied and pasted' to translate and rotate values (example: hh60.3d file):
...
# Tail rotor
# blades x y z h p b r prop_wash? flw_con? blur?
rotor_new 2
0.3 -9.1 0.61.5 0 0 1
# r g b a
rotor_blur_color 0.15 0.15 0.15 0.75
begin_model rotor
#$model_flags
translate
0.300000 -9.100000 0.600000rotate
0.000000 0.000000 80.000000# Struts to blades
...
V-22 left rotor is an exception, it don't work in model viewer if translate 'z' value is copied from rotor_new 'z' value: value must be modified.
I don't know if it is possible that copying 'z' value works for V-22 left rotor, but if yes, it would certainly need to modify some primitives in addition to rotor_new values.