Open GoogleCodeExporter opened 8 years ago
This is a known issue and was something I didn't plan for during beta when
these scripts were developed. I didn't know some bosses would change
perspective.
A zoom fix is in the works, but as far as I know there is no way to
automatically adjust for the perspective change in the final phase of the
Belial fight. If I can get the screen data during the fight somehow then I
might be able to set a keybind that can be pressed for that one particular
phase to correct the issue. I will be working on the screen data first.
Problem is I will need to find something that is universal for all resolutions
(16:10 and 16:9 at least) so it may take a while to figure out the appropriate
values. Bear with me.
For now the best thing I can suggest is just do that one phase with a mouse and
keyboard. I know that isn't ideal for those of you suffering from things such
as RSI and carpal tunnel, but it is the only solution I have for now. I will be
working on some updates soon to try and help you all out with this.
If there are any other fights that have perspective changes let me know. I
don't recall any but weird behavior could pop up anywhere.
Original comment by jsig...@gmail.com
on 27 May 2012 at 3:10
A keybind would be acceptable. Like let us bind it to like press down. on
press down I could make do a zoom and adjust res. It would be nice if it was a
toggle. Or i could make the other joy press down zoom out and adjust res.
just make a res variable.
Original comment by tracy.ro...@gmail.com
on 27 May 2012 at 4:32
to make a toggle maybe set a varible, if set then on next press change res back.
Original comment by tracy.ro...@gmail.com
on 27 May 2012 at 4:33
if you want a good way to emulate this fight for easy testing then in options,
click on gameplay then under interface check zoom when inventory is open. this
will do the same thing.
Original comment by tracy.ro...@gmail.com
on 28 May 2012 at 3:56
or just press zoom i guess, haha.
Original comment by tracy.ro...@gmail.com
on 28 May 2012 at 3:59
Original issue reported on code.google.com by
d.tha...@gmail.com
on 27 May 2012 at 10:50