retroshaun

Yeah I am definitely in for at least a couple - maybe more. Probably 1 backlit but the others non (closer to original).

Hope I am not too late to place a pre-order? I will take 3 screens please

I would be in for sure.

Count me in for one also!

Please add me for one card. Thanks!

Working now.

Hi guys, My first foray into Odyssey 2 / VP coding isn't going well! I am simply trying to assemble hello.a48 using AS 1.41r8. I think I have it set up correctly, following the readme docs, but all I get is assembling HELLO.A48 PASS 1←[K > > >HELLO.A48(38) : error : error in opening file←[K fatal error, assembly terminated Everything is set up in the system path and I am running AS from the project folder containing the .a48 file. What am I missing? There doesn't appear to be a good solid beginners guide floating around that I can see. Thanks! S

I would take one for the 5200 if you get more in stock. Thanks!

No fix, I just wasnt understanding how to point the editor at the correct files. My own silly mistake. File->Select Title Source Directory and point it to the titlescreen kernel folder you extracted.

*Ignore me - fixed!

This isn't how you use dim. The item on the right of the equal sign should be a predefined bB variable, and the purpose of the command is to give that variable another name. (to make your code readable.) For the code you wrote here, I'd expect bB to set the label "ey" to memory location 10, which is a TIA hardware register... screwy results will naturally follow. Check out the dim section of the bB guide at Random Terrain's site for more info. [edit] also worth mentioning that there's no reason you can't directly manipulated player0y; "player0y=player0y+1" works just fine. Ahhh OK I got it - I was reading some stuff on DIM in another post and I guess what was written there was incorrect. That would explain it Yes I realized I could increment player0y directly but I need to track the value for another use. Thanks! EDIT: All is working just fine now, thanks!

No I was at work (long story on the internet thing!). At home now so all is well. I think theres a fundamental thing I am simply not "getting" about DPC+. I am playing around now with this code, simply setting the default Y position in a var and assigning that to player0y with... "unexpected" results. I can cycle through 0, 10, 20 etc but when I hit, for example, 60... the sprite disappears completely. Most odd. How is the screen space addressed? I have screen res and init set up as follows, and I admit to not really understanding the bank code at present, which may well be the problem! set kernel DPC+ set smartbranching on set optimization inlinerand set kernel_options collision(playfield,player1) set tv ntsc goto StartInBank2 bank2 bank 2 temp1 = temp1 StartInBank2 DF0FRACINC = 32 DF1FRACINC = 32 DF2FRACINC = 32 DF3FRACINC = 32 DF4FRACINC = 64 And the main sprite update code is: dim ey = 10 player0x = 30 main gosub moveSprites player0y = ey drawscreen goto main moveSprites ey = ey + 1 return Like I said - its **very** basic at this point as I am only experimenting. But as its set, this doesnt display the sprite. If I initially set player0x to, for example, 200... it works as expected.

OK... another probably stupid question. I have a playfield set up in DPC+ with the screen res set with DF(0-3)FRACINC. All looks good. I have now added 3 sprites (player 0-2) and all I am doing is displaying them in a line across the screen and then I have a subroutine to increment their Y position so they effectively move down the screen, top to bottom. The weird part is, if I start them anywhere on the visible screen, they don't move at all!! However if I start them off screen (for example at Y=200) then they move just as expected, starting right at the screen top and moving off the bottom then cycling to the top again. What the hell?

Awesome - thats what I figured AND I figured the DF0-3 too, and its now working. Thanks for confirming

Not right now its on a non-internet laptop But the error is simply: Syntax Error at Line 18 (which simply says pfheights: ) I am sure this is something stupid!

Hey everyone, I am starting to mess around with VisualbB a little and really haven't gotten too far just yet. I managed to get sprites and basic playfields working, now I wanted to try a playfield in DPC+ (higher vertical res). So my first question (of many, no doubt!) is... why does pfheights: give me a syntax error? Is this something that doesn't work with DPC+ perhaps? Thanks.

OK got it! Thanks Jeff By the way is the latest build number 554 or is there something newer? I was hoping to get the Use DPC+ Sprites option, which I dont have at present.

Not a bug. What I think you are seeing is you are trying to set either the Player or Playfield color equal to the background color. The background color is shared between the sprite and playfield designers and you can't have the same, let's call it a pixel color, equal to the background color. Check your player color it's probably already $00. Actually I am new to the editor but I am already getting this same issue. I accidently changed my sprite background and now I cannot change it back, regardless of what colors I have set as player color, playfield color , playfield background etc. This really does seem like a bug and is kinda frustrating as now the best I can get is a "dark grey" sprite background! I tried new projects too, and the default is always the same altered background color. Any chance of a fix / workaround for this, or simply clear up my confusion? Thanks!

After a recent relocation across country I am left with a 2600 but no PSU or joysticks! I am sure they are somewhere in a mound of boxes but right now I just wanna get my hands on some and start playing games again! Anyone have these they would be willing to part with? I can Pay Pal payment. Would rather avoid ebay if possible! :-)

I'll take a copy as soon as they are ready - put me down for one

Yeah I tried that. I can't even get it close. The first stripe in the test pattern is meant to be bright red and on my cab it displays black. When I boost the red on the monitor, that stripe and all the border etc go to a overall "overbright" red. Its as if the red areas arent even being sent a red signal, thats teh way it appears. Is this possible? Could there be a board or (more likely?) wiring fault causing there to be no red sent to the monitor?

I took a little time (finally) to look at my Buck Rogers today, finally taking the back off to adjust the monitor as I always thought it looked way too green. After setting everything to a pretty much neutral setting (R, G, B, contract, brightness all centered) it looked better but something didnt seem right from my memory of the game. After firing up Mame I can see that theres simply no red in the picture at all. If I blast the red adjustment up the monitor definately goes very red overall, but the parts that should be red (main title screen logo, engine thrusters, lights on the enemy ships etc) are black. What could cause this? Is this a monitor or board issue? I even questioned if it could be a bootleg board, is this possible? I have no desire to mess with monitors too much so if thats the problem then I'll look at a replacement or even finding someone to repair it. Thanks!

I just picked up a Stern Scramble today - its a little grubby (been sat in a very bad garage for years) and I'm actually surprised it works at all! However, there are definate problems... The main issue is that the game keeps resetting. Sometimes you can start a game and after the first big mountain the game either completely resets or the screen corrupts (fills with pink and some of the rocket towers from the final stage), THEN resets. Sometimes it runs in attarct for a little while before resetting, other times it sticks on the grid pattern. Not having looked at this at all I guess its either a PSU issue or a board fault. Whats the best starting point? Measuring the PSU output? Do I test on the board test points, chips or straight at the PSU outputs? I'm relatively inexperienced with repairs but know the basics. Its its teh PSU then I guess a switcher is a good fix? Aside from that, the next issue is theres no sound - maybe the above (PSU?) problem is related, or the wiring as it look a little messy. I do have speaker hum / buzz though so I guess its getting power. Thanks for any assistance.