This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
warcam started at distance < 0 breaks zoom when stopped #4830
Labels
Milestone
Comments
|
Forgon uploaded file warcam stopped after start at distance -250, leading to a zoom value of 2^32^-256 |
|
Forgon uploaded file patch file created with |
|
Forgon2100 <forgon2100@...> changed status from |
|
Forgon2100 <forgon2100@...> changed owner from `` to |
|
Forgon2100 <forgon2100@...> changed resolution from `` to |
|
Forgon2100 <forgon2100@...> committed [46] In Warzone2100/warzone2100@46b191a: |
|
Forgon changed type from |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
resolution_fixedtype_patch (an actual patch, not a request for one)| by ForgonStarting the warcam in debug mode at a distance < 0 and stopping it afterwards
set the zoom to a value of approximately 2^32^ minus the negative distance (see attached image
[raw-attachment:warcam_zoom_bug.png]).
This was a type error: The distance, a float, was stored in an uint32_t (or
UDWORD, as defined in './lib/framework/types.h:103'). The problem had been
introduced in
`
commit 1c580714051c3baeadea53e4c3dd494a8c10e443
Author: per per@wz2100.net
Date: Tue Jan 15 22:36:51 2013 +0100
'
The attached patch fixes the problem.
Issue migrated from trac:4830 at 2022-04-16 13:08:54 -0700
The text was updated successfully, but these errors were encountered: