If It's Not One Thing... (DPC+ Issues, Again)

[Cybearg]

... it's another.

 

So it so happens that one of my hard drives died last night. Removing it fixed the problem, but I reinstalled Windows 7 64-bit anyway, just to be safe. I have downloaded all current updates, including Microsoft .NET 4 Framework.

 

As some of you may recall, I had been having issues with DPC+ games not compiling for me, but now they work again in Windows 7.

 

However, now there's a new issue: in DPC+ games, sprite/missile colors don't seem to be working correctly. The attached DPC+ game, which should have the following player colors:

omega.bas

omega.bas.bin

 

player0color:
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
$2C
end

 

and the following missile color:

 

COLUM0 = $0E

 

Instead of the sprite/missile being yellow, I get a solid white player0 sprite and a missile that turns black when it's past the player's sprite.

 

 

 

The same also applies to the other attached DPC+ game, where the player 0 sprite should have these colors:

aliengame.bas

aliengame.bas.bin

 

player0color:
$46
$46
$44
$42
$40
$42
$44
$44
$42
$0E
end

 

but instead of a multi-colored reddish sprite, it is solid black:

 

Any idea what's wrong this time?

 

For reference: my vbB and bB directories were NOT deleted, so these are the exact same files that worked with proper colors before.

Edited April 6, 2013 by Cybearg

[+iesposta]

I copied omega.bas into my temp project directory in VbB.

It would not compile.

I created a new project directory.

It compiles just fine. omega.bas.bin

Try creating a new project folder, put omega.bas in there. . . ?

 

Do you have the newest /includes/custom/bin/custom2.bin file?

And add the 2 semicolons in the DPCplus_kernel.asm file? http://atariage.com/forums/topic/210115-dpc-player-missiles-going-dark/#entry2717687

 

- There is no command: "bank 7"

[Cybearg]

Use the original DPCplus_kernel.asm in the /includes/ folder

Find and change this by just adding the two semicolons with a text editor or wordpad:

sec

lda #<(P0COLOR-1)

;sbc #0

sta DF0LOW

sta temp2

lda #>(P0COLOR-1)

;sbc #0

sta DF0HI

That fixed it, by jove!

 

Thanks!

[+iesposta]

Keep making fun 2600 games!

[Cybearg]

Keep making fun 2600 games!

It becomes very difficult to keep at it when things seem to conspire against you.

 

For instance, the other day my computer had a jolly death, so now I had to reinstall Windows and pull some bad hardware. I saved my 2600 stuff, but lost a crap-ton of other things that are leaving me feeling a tad grump over the whole ordeal.

 

If I had lost my 2600 stuff, I would have thrown in the towel right then and there.

Edited April 8, 2013 by Cybearg

[+iesposta]

Spiceware had a good idea. Bonus. It's free.

Create a Blog post and upload your files there. Keep it in draft mode or unpublished or private and you can always download them anywhere.

[+Gemintronic]

It becomes very difficult to keep at it when things seem to conspire against you.

 

For instance, the other day my computer had a jolly death, so now I had to reinstall Windows and pull some bad hardware. I saved my 2600 stuff, but lost a crap-ton of other things that are leaving me feeling a tad grump over the whole ordeal.

 

If I had lost my 2600 stuff, I would have thrown in the towel right then and there.

 

Sorry to say this but you needed a fresh install of Windows. Now you can get the latest bB and VisualbB install in correctly.

 

A side effect of posting your source code on AtariAge is that even if your town gets bloobersnatch deztroyed you can re-download your source and keep going.