Pete's QBASIC Site

Have a variable which has say 10 in it, and each frame subtract 1 form the sprites Y coordinate, and subtract 1 form 10... then when 10 is 0, start adding 1 to the variable that had 10 in it and add 1 to sprites Y coordinate... will give you some jumping ability... nothing smooth...

the thing is the main module doesn't even have 200 lines of code... and no other part exceeds the 64K limit, at least none has enough code to exceed it...

And I need to make a Windows version of my tracker anyway, so FB is the best option for that... first a pmode DOS version, then a Win version...

There is NO way to reduce the code... its already hyper space and speed optimized...

it seems I need to start digging FreeBASIC... any recommendations on getting started ?

I have the second issue then... can't fit stuff to OBJs...

Now I need the command line switches and stuff of BC.EXE and LINK.EXE...

Routines need full access to the arrays/variables

I have nearly no data in the file, its all code... there's not much variables either... maybe half a KB. There's array's, but they all are less than 5...6KB. I also use 512KB of XMS but that doesn't matter... I think I'm having too much code... COMMON SHARED HANDLE%, MBASE%, speed%, SCOUNT%, QUIT%, ...

I've got them before actually, but managed to get rid of them by moving some code to SUBs (I think I hit the 64k code per SUB limit). Now I got it again, so I moved more code to SUBs, and the error remains... I can run it in IDE, but not compile... Source file is 68.6KB big, consists of almost 3000 ...

64K per sub limit reached ? Move some more stuff to subs... I wasn't able to compile my MD tracker, I moved half of the code to a sub and all problems are solved. BTW, you might want to use this method for timing (not too good either, but seems to work) : count frames, and after each second check ho...

procedure limitation ? I don't really think having about 10 extra lines of code will do anything undesirable, at least not anything else than speed... speaking of speed, you should make the game 60FPS not 30... its pretty choppy...

nothing's wrong.... I need to try sometihng... EDITCOPY, EDITDELETE, buffer empty, EDITCOPY, do something else then EDITDELETE, fine...... I'll put some extra between the two calls.... EDIT : Did weird stuffs, and nothing helped.... kinda seems like the array is wiped after EDITDELETE... now trying ...

the Patterns& array is global too, I've forgotten the line in first post... it ALWAYS contains pattern data for all channels in all cases. EditCopy does not have to modify the Patterns&, it has to copy certain amount of data form certain area to CopyPaste& array. That's for copying, CUT ...

Yes, that's what I do

???? ECH% = EDITCH% + EDITCH% > 6 ????? Your EDITDELETE won't work as it will kill both channels, it only needs to do so for one (one is first WORD, other is other...), depending on on ECH%. ECH% marks the Dimension in array, and EDITCH% the channels, and ECH% 6 contains 2 channels (EDITCH% 6 and 7)...

tiny optimization

i% = 27917
i% + (i% AND 255) * 256 + i% \ 256
PRINT i%

EDITCH% is the current channel i'm on the tracker and ECH% is there because there's 2 channels in 1 in one of the dimensions of the Patterns$ array... just a stupid way my tracker works after one addition. COPYLEN% is already 1 unit smaller so need to make it smaller. EDITCH% is ALWAYS in the range ...

DIM SHARED OrderTable%(255, 6) 'Order table DIM SHARED CopyPaste&(63) 'CopyPaste buffer COMMON SHARED HANDLE%, MBASE%, speed%, SCOUNT%, QUIT%, TMFROW%, ORDERROW% COMMON SHARED TMFLEN%, TMFPAT%, EXITS%, PAGE%, MX%, MY%, MB%, COCTAVE% COMMON SHARED KEYS%, TRACKPOS%, SAC%, PLAYMOD%, SEGM%, OFFSET&...

I have it, but I don't recall it working for DOS stuff, at least not in 9x... I think it even moved windows mouse and was fully active when some DOS stuff was focused...

this is awesome !!!

I didn't toy much around with it, but the scrolling is little choppy on my machine (Celeron 1117, 512MB RAM, VIA onboard GFX crap (which works well for DOS stuff), Win98SE).

You should add joystick support too, games like that aren't fun to play on a keyboard !!!

x86 CPUs shoulnd not have any trouble moving 2/4/8 bytes form odd mem locations... 68K will give you Address Error, but not x86... none of the GFX routines i know would work if x86 wouldn't like odd addresses and even data...

Michael Calkins wrote:TmEE: I'm a little curious about using POKE without DEF SEG... Is it already in the correct segment?

Variables are in the same segment as the code is, usually... if there's any issues, just set up DEF SEG.