Printable View
Bank problem again.. but this time it does find the bank ONLY IF it's facing north more than south.. if the compas is south, southeast or southwest it can't find the banks (so basically it can't see them from behind)
so far I just disable smart & move the camera to north and then it finds the bank instantly
I just committed a fix (hopefully) for this. I don't have an account to test it with right now, but update and let me know how it goes.
Thanks for the bug report. :)
does override update work if the auto update doesn't register any changes yet? (if that makes sense)Quote:
Originally Posted by NCDS
I got version 804, just DL'd it gonna test.. let me know if that's the wrong one and how to get the one with your fix
No it does not... I was told when asking this question that changes are registered by Wizzup's server every hour or so, therefore it may take some time...Quote:
Originally Posted by grats
Edit: Actually it may if the autoupdate doesn't check every hour or less...
oh so they don't update the files on wizzups server.. it has to grab them elsewhere?Quote:
Originally Posted by Yago
well so far it's working so I can't say if it didn't work or not lol, it hasn't turned the camera to have south faced up yet so nothing has gone wrong, we'll see
The updaters check wizzups server...
yes and? was my question not specific enough?Quote:
Originally Posted by Yago
I asked if wizzups server gets the updated info elsewhere.. obviously wizzups server doesn't tap into the brains of the person who wants to edit it and just magically gets it.. :duh:
I got that question answered when the bug is still there.. the answer is "no, they do not update directly to wizzups server"
That's as far as I know... probably github or something...Quote:
Originally Posted by grats
First of all, the camera should always be faced north when opening a bank because it's always set to north when walking (or should be anyway). Second of all, after we've made a commit to github, you should expect your auto-updater to update within an hour. I don't know if the delay is in the updater or Wizzup's server. You just need to know if it's within an hour.
didn't update till this morning =/ (so like 10+ hours)Quote:
Originally Posted by Coh3n
running it now to test..
it definitely doesn't face north when it runs
well it was doing ok but then it got stuck, it looks like the fix was to turn the camera a little bit when it gets to the bank if it can't find it at first (that's what I noticed it do) but it should just turn the camera north.. because it didn't turn the camera enough to see the bank.. or maybe turn the camera every time it checks
That can be adjusted. I have it turn the camera randomly between 265 degrees and 85 because you said as long as it faces more north than south it will work. I can make it face more north though, that's no big deal. I just figured it looks more bot like to face north every time you walk anywhere.Quote:
Originally Posted by grats
If you want to try it out yourself adjust line 100 and 101 in Banking.simba then when you have the correct combination post or send a pull request. Otherwise I can change the numbers and commit, but I don't have an account right now to test it with and make sure it works.
oh ok yea I'll figure out the ones that work ;-)Quote:
Originally Posted by NCDS
yours worked some times but when north pointed to 8 o-clock it would move it (sometimes) counterclockwise, so it would make it point to like 5 o-clock.. then that's still north facing down =[
I think I figured out why it didn't work.. the compass angles don't really work like they should I guess? I've been just spamming MakeCompass(RandomRange(x, x)); with diff numbers to see where it would go with each and if you go over 100 it goes past 9 o clock and goes down to 8 and 7 o clock the higher number you go.. no matter if it's MakeCompass(RandomRange(100+, x)); or MakeCompass(RandomRange(x, 100+));
so what I learned was when I did
MakeCompass(RandomRange(75, -75));
it then stayed above 9 o clock and 3 o clock, keeping it north the whole time no matter how many times I pressed it
so after learning that I did 85 (making it near 9 o-clock but not too close) and -85 (making it near 3 o-clock but not too close)
I think we thought this was its angles:
http://i.imgur.com/idS0X.gif
when it doesn't seem to work like that really.. because if you do 100-300 it'll go between those two 101,102,103 etc.. and if you do 300-100 you'd think it would go 99,98,97 all the way around to 360,359,358,357 then down to 300, but it doesn't do that
I'm so confused but i guess negatives kind of make sense.. anyway
MakeCompass(RandomRange(85, -85));
is working 100% correct now
so like this:
http://i.imgur.com/ICgAZ.jpg
shit I meant to edit that in the other post
That compass is backwards..
http://img388.imageshack.us/img388/4171/3rdjf5.png
Doesn't matter though, I'm going to look in to why it's not making the compass north while walking to begin with.
E: Merged your posts.
simbas compass is backwards thanQuote:
Originally Posted by Coh3n
when I just did
MakeCompass(RandomRange(35, 50));
MakeCompass(RandomRange(55, 70));
I did all of them all the way around to see where stuff was because it wasn't working how NCDS had wrote it in the script to be up north, yet it was going south instead
that's why I was saying it doesn't make sense
That's from NCDS's update, and is actually the complete opposite of setting it north. That will make the compass somewhere in-between 85 and 275 degrees, which is the entire southern part of the compass. Here's what randomRange(85, 275) does:Simba Code:MakeCompass(RandomRange(85, 275));
http://img62.imageshack.us/img62/2176/rscompass.png
Also, you were talking about 3 o'clock/9 o'clock, etc. I don't know if you were getting it confused, but the angle you put in the makeCompass() parameter isn't the angle that the little N gets pointed to, it's the angle of the compass. For example, if the N was at 9 o'clock, the compass angle is 90 degrees.
By the sounds of things, using randomRange(-85, 85) works. I didn't know makeCompass could take a negative angle, but again, the compass is supposed to be made north while walking, so I'm not sure what's happening. I'll look in to it.
yes I know, I competely understand it.. that's exactly what I was saying.. 9 o-clock = compass points to 90 degrees (N is the pointer..) which on this chartQuote:
Originally Posted by Coh3n
http://i.imgur.com/idS0X.gif
90 degrees = 9 o-clock
I was just saying it's weird because you should be able to say as you said:
randomRange(85, 275)
http://img62.imageshack.us/img62/2176/rscompass.png
but if you did
randomRange(275, 85)
I think it should do the opposite side.. that's just how I think it should be, instead of using negative numbers
your pic is backwards though.. simba counts the other way
9 o clock = 90 degrees, not 3 o-clock = 90degrees
3 o-clock = -90
Oh I see, sorry I completely misunderstood your image. :p Have you tried using (275, 85)? MakeCompass can always be edited to work that way as well.
yes I was messing with the compass for about 15 mins I made a tiny script that all it did was open smart and then do myQuote:
Originally Posted by Coh3n
procedure anglez;
begin
MakeCompass(RandomRange(75, 50));
end;
and it had the login stuff etc
so I basically pressed play, saw where that went
changed it a little
pressed play, saw where that went
changed it a little
till I figured out how it works (which in this case it ONLY goes from 1 number to the other by going downward (as your image shows) and never can get a northern random angle without using a negative.. the second I tried negative numbers it started working
so basically
MakeCompass(RandomRange(75, 50)); = MakeCompass(RandomRange(50, 75));
there is no diff
It'll be because of the way the comparison is done. It'll be like randomRange(lowNumber, highNumber). The lowNumber can't be greater than the highNumber (it only makes sense in a compass scenario).
oh yea I get that nowQuote:
Originally Posted by Coh3n
negative numbers make sense IMO, if you want to cross the 0 on the very top middle, you must use a negative to get to the other side (crossing the 0) but if you want to cross the the 180 with two numbers you just use positives
http://i.imgur.com/U0Fih.jpg
it was just confusing at first, when I figured it out, because nothing else in simba really uses negative numbers
gonna go play some starcraft 2, I've used my brain too much today
the 85, -85 has been working for hours by the way, I'm messing it up on purpose and it works 100%, so that is good to add to MSI banking.simba
I feel like it should be randomRange(-85, 85), not the other way around because if you look at it like it's on a number line, there's no in between 85 and -85, there's in between -85 and 85. Know what I mean?
yea, no you are correct, simba should read the circles this way:Quote:
Originally Posted by Coh3n
http://img62.imageshack.us/img62/2176/rscompass.png
and not this way:
http://i.imgur.com/idS0X.gif
it just seems to be backwards if it counts 'counterclockwise' rather than counting 'clockwise'
I don't know anything about changing it, but I know how to test stuff and figure out what it does :P
Sorry, did you say you tried using randomRange(-85, 85)? If not, test that out. I've always done it that way and it's worked.
yea it worksQuote:
Originally Posted by Coh3n
-85, 85 = 85, -85
208, 50 = 50, 208
for the compass random range there is no difference currently
Okay thanks a lot! I'll take care of this right now.
E: Thanks for testing grats, this is fixed in the latest version.