Need some help with player movement..

[_vince]

so _SETBIT is one of your innovations for QB64
and I am fear that we must wait just some time before we can go on trying your code after downloading the new version of QB64 from github that has into it your innovations!

Why not make a SUB setbit? What are SUBs for anyway? I guess Cobalt is probably using C bit shifting operations but it can all be done in pure QB.

[TempodiBasic]

@Cobalt

I can confirm that the issue is the sincronization between main loop and timer's events!

Here the Petr's code example converted to use a ON TIMER.... after some attempts and a glass of beer I have understood that the difficult to pass variable SHARED to Timer subroutine is the frequency of the timer's events...

so I solve the question with code working... the key is the ratio between time interval of timer's event (in the example .3) and time of delaying the main loop (in the example .1)

Code: QB64: [Select]

1. CONST True = -1, False = NOT True
2. DIM SHARED character_position AS INTEGER, TileLimit AS INTEGER, char_Step AS INTEGER
3. DIM SHARED i AS STRING 'AS INTEGER
4.  
5. SCREEN 13
6. character_position = 160
7. TileLimit = 30
8.  
9.  
10. t0 = _FREETIMER
11. ON TIMER(t0, .3) Make_move ' time of event must be just a little more than delay in the main loop
12. TIMER(t0) ON
13.  
14. DO UNTIL i = CHR$(27)
15.     CLS
16.     LINE (TileLimit, 0)-(TileLimit, 300), 14
17.     LINE (character_position, 100)-(character_position + 32, 132), , B
18.     _KEYCLEAR ' to clear keyboard buffer
19.     i = "" ' to return in the WHILE WEND
20.     WHILE i = "" ' this focus on take input
21.         i = INKEY$
22.         char_Step = 0 ' no movement
23.         _LIMIT 50
24.     WEND
25.     IF i = "a" THEN char_Step = 1 ' movement to right
26.     IF i = "z" THEN char_Step = -1 'movement to left
27.     _DELAY .1 ' we need this to elaborate the input
28. LOOP
29. TIMER(t0) OFF
30. TIMER(t0) FREE
31. END
32.  
33. SUB Make_move
34.  
35.     IF LEN(i) THEN
36.         FOR Move = 1 TO 32 'character size = 32 pixels
37.             ' stopping if it reaches the limit of movement (border of tale or other kind of limit)
38.             IF character_position + char_Step <> TileLimit THEN character_position = character_position + char_Step
39.             CLS
40.             LINE (TileLimit, 0)-(TileLimit, 300), 14
41.             LINE (character_position, 100)-(character_position + 32, 132), , B
42.             _DELAY .01
43.         NEXT
44.     END IF
45. END SUB
46.  

Thanks to read

@ _Vince
I agree
it is a workaround.

[Cobalt]

Why not make a SUB setbit? What are SUBs for anyway? I guess Cobalt is probably using C bit shifting operations but it can all be done in pure QB.

I've a whole set of BIT handling routines on the platter, just can't get into Github to see about pushing them to QB64 yet.
just for ease of use and speed. but yes they can be reproduced in house too. Although I would rather put my effort elsewhere in a program.

[Cobalt]

Although thanks to your guys help, in giving me ideas and things to try I think I've finally got it!!! up way too late last night working it out, but it looks like it works, I've REMed the bithandling out for now if you guys want to try it, you'll need to Re-download the GAMEDATAV1b.dat file cause I had to modify things in it. but you can roam MOST of the world until I get the entry code setup to enter caves, castles, and towns.


okay I lied, I simply deleted that routine for now. (removed stray _SETBIT)

Don't know why that was so hard for me to get the movement working, but

Thanks guys.

[FellippeHeitor]

Still a bunch of stray _SETBIT in this latest code block.

[TempodiBasic]

yes _SETBIT showed at line 463 of code in QB64IDE

[Cobalt]

Still a bunch of stray _SETBIT in this latest code block.

Not sure I consider 1 a bunch?  If I'm holding 1 banana I don't think anybody is going to say  "look Cobalt is holding a bunch of bananas!"

the whole magic learning system is bit based. in reality though better than half of items in the game should be bit flag based.

[FellippeHeitor]

Point is: code still not runnable by everyone.

[SMcNeill]

Just swap in a function SetBit if you’re having issues:

FUNCTION SetBit (variable AS _INTEGER64, bit, toggle)
   b = bit - 1
   If toggle THEN
      SetBit = variable OR (2 ^ b)
   ELSE
      SetBit = variable AND NOT (2 ^ b)
   END IF
END FUNCTION

a = SetBit(a, 3, OFF) ‘Sets the third bit off
b = SetBit(b, 2, ON) ‘Sets the second bit on

[FellippeHeitor]

I've REMed the bithandling out for now if you guys want to try it

Point is: code shared by cobalt is not runnable as is. I’m not the one to adapt it.