Jump to content

nanochess's Photo


Member Since 11 Jul 2011
OFFLINE Last Active Yesterday, 9:22 PM

#3853745 The Official Intellivision Revolution AIR RAID thread

Posted by nanochess on Yesterday, 7:40 AM

What the heck is that?
I should probably know this.... :?

The cartridge with T shape?

#3853593 Deset Bus - Official Endurance Contest

Posted by nanochess on Fri Sep 22, 2017 11:07 PM

Ok, this is coming too far... :rolling:

#3851325 IntyBASIC Backtab Tiles Find and Change?

Posted by nanochess on Tue Sep 19, 2017 8:06 AM

Then you don't need to use ON FRAME GOSUB. (BTW if each object is 5 tiles, object 3 cannot be 10-14 but 15-19)


object_number_1 = 0
object_frame_1 = 0
object_number_2 = 3
object_frame_2 = 0
' This code expects the GRAM cards already rendered in screen.
WHILE your_code_has_not_ended
    DEFINE 0,1,VARPTR object_tiles((object_number_1 * 5 + object_frame_1) * 4)
    DEFINE ALTERNATE 1,1,VARPTR object_tiles((object_number_2 * 5 + object_frame_2) * 4)
    object_frame_1 = (object_frame_1 + 1) % 5
    object_frame_2 = (object_frame_2 + 1) % 5
    IF cont1.button THEN
        IF debounce = 0 THEN
            object_number_1 = RANDOM(5)
            debounce = 10
        END IF
    END IF
    IF debounce <> 0 THEN debounce = debounce - 1

#3850293 IntyBASIC Read Array Limited, "Foreach"?

Posted by nanochess on Sun Sep 17, 2017 5:15 PM

I would use a constant for length and use both for DIM and FOR

#3849200 Oregon Trail for Intellivision

Posted by nanochess on Fri Sep 15, 2017 10:13 PM


Black does look the best.  I bet more people would buy if black was the default.  Keeping blue as default is just silly at this point.


Oscar, how about it? 



Black rules.  Blue sucks.  If you think otherwise, you are wrong.


Ok, guys you both like black, so we made this as an option.


I should write a short history about every BASIC language having blue background, Atari 8-bit, MSX, Oric, etc. Kids programming happily with blue background, etc, etc. Nobody complaining, etc, etc.


So I like blue and it's my favorite color and I use my developer prerrogative to start it as default ;) and every beta tester didn't complain and there were 8 beta testers... so "liking+doesn't matter versus unlike" is equal to blue > black, or 90% people prefers blue ;)


Sorry guys, we won :P but both of you got your option ;)

#3848051 Is Java any benefit to programming for the 2600?

Posted by nanochess on Thu Sep 14, 2017 12:30 PM

Not a good language. If you don't have any programming language background I would suggest to go for Batari or directly 6502 using the tutorials.

#3847418 Worth $80?

Posted by nanochess on Wed Sep 13, 2017 4:39 PM

Dollar per cartridge, I like it. :)


I would bargain given the dusty look "look pal, I've to clean everything, it's pretty dirty, besides some cartridges doesn't have labels, maybe some even doesn't work" :evil:

#3846917 CV - Video Vertical Banding

Posted by nanochess on Wed Sep 13, 2017 6:07 AM

I would suggest cleaning with alcohol the zone around 3.579545 crystal and also inside the RF module.

Also using the Finger Tester 3000 ™ you pass your finger near the VDP and capacitors to check for floating pins (broken caps mainly)

#3846335 Oregon Trail for Intellivision

Posted by nanochess on Tue Sep 12, 2017 12:28 PM

Saddle up!



:o :o :o :o :o


I take my hat off to Mark! :) :thumbsup:

#3844493 IntyBASIC SCREEN and Offset?

Posted by nanochess on Sat Sep 9, 2017 9:13 PM

Let us suppose you have your 7x11 image in a single BMP file measuring 56x88 pixels, and same with other image.


intycolor -b -n image1.bmp image1.bas image1

intycolor -b -n -o32 image2.bmp image2.bas image2


Note the use of offset 32 in second image, why? because both images must use non-conflicting GRAM, otherwise you'll see trash in the change (another option would be to put the frame in black while defining GRAM)


Supposing each image used only 16 GRAM.


DEFINE 0,16,image1_bitmaps_0
DEFINE 32,16,image2_bitmaps_0
    SCREEN image1,0,26,7,11,7  
    FOR c = 0 TO 60: WAIT: NEXT c
    SCREEN image2,0,26,7,11,7
    FOR c = 0 TO 60: WAIT: NEXT


This code will overlap the image alternating between the two at location 26 of screen.


Note how the code gives the X size and Y size in cards, and ALSO the final argument is the width of the source image in cards.

#3844486 Oregon Trail for Intellivision

Posted by nanochess on Sat Sep 9, 2017 9:01 PM

What's this. attachicon.gifIMG_0740.PNG

Bow to the king! you're faster than the roadrunner! :o

#3841089 Oregon Trail for Intellivision

Posted by nanochess on Mon Sep 4, 2017 7:59 PM

Making everyone happy was kind of hard...dinosaurs, aliens, and sharks, then we discovered one of the testers meant "Indians," not "aliens"...nanochess added the Indians but we had a hard time getting their elephant's ears correct...

Hey! I thought we had agreed to not talk about the aliens game we're making 8)

#3840979 Anteater rom, still missing?

Posted by nanochess on Mon Sep 4, 2017 4:57 PM

I love when old dev threads get bumped. Is this still in development? ;-)

Still in development :)

#3840817 INTYBASIC 1.2 problems

Posted by nanochess on Mon Sep 4, 2017 11:12 AM

I ran into something that might be explained by the above. A sample program using the compiler version 1.2.8:

 SIGNED a,b,c,#f
 PRINT AT 0 COLOR $0007,"D=ABS(C)*2:"
 PRINT AT 12 COLOR $0007,<>d
 PRINT AT 20 COLOR $0007,"#E=ABS(C)*2:"
 PRINT AT 33 COLOR $0007,<>#e
 PRINT AT 40 COLOR $0007,"#G=ABS(#F)*2:"
 PRINT AT 54 COLOR $0007,<>#g
 GOTO loop
It displays D=150, #E=65174 and #F=150. Perhaps that is expected behavior given the above?

In my case, I can use 16-bit variables all the way but for those cases where the value is known to fit within 8-bits, I would prefer to use one of those.

(Edited due to the AtariAge forum eats anything that is below code fragments unless BB Code mode is switched off)

The behavior is all right.

Let me explain the IntyBASIC expression processing:

1. Every arithmetic is done internally in 16 bits (the register size)
2. SIGNED affects the reading of 8 bits variables (extending them to signed 16 bits, default is reading as unsigned)
3. SIGNED/UNSIGNED affects a single flag while processing expressions that switches between signed comparison and unsigned comparisons.
4. The PRINT <> operator always shows the 16-bits numbers as unsigned.

So the advantage of SIGNED with 8 bits variables is that it allows to add negative numbers to 16-bit variables without using the precious 16-bit space to preserve the value or manual sign-extending operations.


  #a = #a + b   ' b can be -128 to 127
The advantage of UNSIGNED with 16 bits variables is that it allows to calculate carry very easily.

  UNSIGNED score

  DIM score(2)

  points = 5
  IF score(0) + points < score(0) THEN  ' Carry over (easy with UNSIGNED)
    score(1) = score(1) + 1
  score(0) = score(0) + points
Applying UNSIGNED to a 8-bits variable doesn't make anything because is the default behavior.

Likewise applying SIGNED to a 16-bits variable doesn't make anything because also is the default behavior.

#3840813 Oregon Trail for Intellivision

Posted by nanochess on Mon Sep 4, 2017 11:06 AM

Five days in a row testing/changing bits in the game, colouring pictures, including an enhanced rendition of the Yellow Rose of Texas and today looks like everyone is satisfied finally :)