False camera visual interpretation with big 'fovy' #919
Comments
|
for some reason limits were not being enfocred when editing properties. This should be fixed now in next push. |
reduz
added a commit
that referenced
this issue
Dec 7, 2014
-=-=-=-=-=-=-=-=- -Fixed Export UV XForm (should work now). #923 -Fixed enforcement of limits in property editor. #919 -Fixed long-standing bug of export editings in script inheritance. #914, #859, #756 -Fixed horrible error reporting in shader language. #912 -Added kinematic collision with plane (please test well). #911 -Fixed double animation track insert when using 2D rigs. #904 -VKey updates offset parameter in sprite edition. #901 -Do not allow anymore a script to preload itself. (does not fix #899, but narrows it down) -Avoid connection editor from overriding selected text. #897 -Fixed timer autostart. #876 -Fixed collision layers in 3D physics. #872 -Improved operators in shader #857 -Fixed ambient lighting bug #834 -Avoid editor from processing gamepad input #813 -Added not keyword #752 Please test!
|
close if fixed |
|
Fixed in rc2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce set camera Fovy to 100. Editor cuts it down to max value 89 and...
camera is visualy pointing UP, but views ok -> downwards.
The text was updated successfully, but these errors were encountered: