Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store

joeyaage

Members
 View Profile  See their activity

  • Posts

    158

  • Joined

  • Last visited

 Content Type 

Posts posted by joeyaage

    Nuon Game System Talk & Discussion

    in Classic Console Discussion

    Posted

    On 3/19/2023 at 12:34 PM, CyranoJ said:

     

    Does your step-down do 110v/50hz or 110v/60Hz though?

     

    Also, please can you confirm if the SD2300 can read DVD-R?  (I know it can't run homebrew nuon)

    I have a working Toshiba SD2300 in the UK and use a Maplin step down transformer 240v/50Hz down to 110v/50Hz. I checked the schematics myself and the Toshiba works at 50Hz or 60Hz as long as voltage is 110v. The SD2300 happily reads DVD-R and can now play signed homebrew...

     

    • Thanks 1

    new original game - codename jagYONG

    in RAPTOR API

    Posted

    I seem to be stuck on collision detection this time. I have these two subroutines called from the main loop. I don't think it ever goes to .was_hit after the bmi instruction. 

    What_Was_Hit:
			lea		RAPTOR_sprite_table+(ID_ai_player*sprite_tabwidth),a0				; point to RAPTOR object table
.chk_hit:	tst.l	sprite_was_hit(a0)													; check if this object was hit
			bmi		.not_hit															; skip if not
.was_hit:	move.l	#-1,sprite_was_hit(a0)												; clear RAPTOR collision flag
			jsr		change_direction
.not_hit:	move.l	#$99900000,BG														; set background colour
			rts																			; exit

Check_Collisions:
			clr.l	raptor_result														; reset the RAPTOR collision flag
			move.l	#ID_player,raptor_sourcel										; Object ID for first bullet
			move.l	#ID_player,raptor_sourceh									; Object ID for last bullet
			move.l	#ID_ai_player,raptor_targetl											; Object ID for first enemy
			move.l	#ID_ai_player,raptor_targeth										; Object ID for last enemy
			lea		RAPTOR_GPU_COLLISION,a0												; now call the RAPTOR collision handler
			jsr 	RAPTOR_call_GPU_code
;			tst.l	raptor_result														; check the global collision flag
;			bmi		.no_hit																; if -ve, then nothing collided
;			bsr		change_direction													; otherwise lose a life
;			bra		.no_hit

.no_hit:	rts

    Binary and source included (no data files, so won't assemble).

    jagyong23.zip

     

    Original games are funny, I keep running into existing games...jagYONG23.thumb.PNG.70dc6b41d8259079b43807ce21638a85.PNG

    • Like 2

    Command Line Tools

    in Jaguar GameDrive Development

    Posted

    My JagGD is Firmware V1.10 Menu V1.07 ASIC V1.07 Stub V1.03

    This time I plugged in the GD, windows searches for drivers and finds them so windows thinks the device is installed and working. Jaggd.exe -r returns with "Jaguar Gamedrive not connected). Here is what is installed...

    JaguarGDdevice.PNG.27c949dce003fbb509808af634bf907f.PNGJaguarGDdevice(Interface1).PNG.6480dff4b0f1be1def35547cd9bf3618.PNG

     

    when I run zadig, I get this...zadig_jaggd.PNG.2676610631af0881f72319d503abb27b.PNG

    If I list all devices in options, then I can select 'Interface 1' and it is already installed but not with WCID (odd..).

    I tried to install this as well. After a long wait it is seconds from aborting and says 'successfully installed driver' but it shows "Driver (NONE)". Tried a reboot but makes no difference.

    All I get is 'Jaguar Gamedrive not connected" from jaggd.exe.

    • Like 1

    Hellgate

    in RAPTOR API

    Posted · Edited by joeyaage
    additional information

    Okay so have updated Hellgate to Raptor 2.0.20 (still adding "bits fly off" explosions/materialisation). Now I want to get up to date and assembled with Raptor 2.0.30 (It does not work, yet).

     

    HELLGATE52.ABS

     

    Things I need to do...

     

    text/particle layer not displaying text when assembled with Raptor 2.0.30. Think it might be related to problems I came across when numbering Raptor object ID's. I have reworked this, doesn't work yet. I have three lists. Originally, I had a text layer 'partlist.s' included in each list. Thought that might be confusing which layer Raptor was using so removed them. Still doesn't work. Might work on game screen but already unplugged my Jagpad...

     

    Next time.

    • Like 2

    Command Line Tools

    in Jaguar GameDrive Development

    Posted

    8 minutes ago, cubanismo said:

    Sorry to continue hijacking, but yikes! If it really is a non-beveled PCB, take some time to gently sand a bevel onto it using some medium-grit sandpaper resting a hard surface (thin piece of plywood, a metal spatula, etc. Nothing fancy). Just hold it at roughly a 45 degree angle (Doesn't have to be perfect) against the edge of the cartridge PCB, go back and forth an inch or so about 3 times on each side of the PCB, look at it, repeat until it looks like a regular jag cart, then clean it thoroughly (soft cloth + isopropyl is best, a water-damp cloth will do in a pinch if you let it dry thoroughly afterwards) to get all the dust off before inserting it again.

     

    Don't risk your Jag cart connector over it, especially as the stock of connectors seems to be drying up. I can still build more Skunkboards. I don't personally know how to build cartridge connectors.

    There is some lovely bevelling on the corners but maybe the 2 top long edges could do with some bevelling. That polish skunkboard is a nightmare. Is it feasable to use the skunkboard components as a doner for a proper skunkboard PCB. Where did all those skunk PCB's on ebay go.

    Command Line Tools

    in Jaguar GameDrive Development

    Posted

    4 hours ago, cubanismo said:

    Before everyone starts getting scared of Zadig, it's very, very hard to brick a skunkboard on accident. Will it truely not boot (no green screen on the Jaguar) or is it just that your PC won't recognize or talk to it via JCP? If it's the former, anyone with a BJL system (like me) can restore it unless it has also been physically damaged. If it's the latter, it's not bricked, and very likely sorting the drivers out will get it working again.

    Hey, great news! My skunkboard (one of the polish copies - stretching the pins, gulp) is fully working on my windows 7 machine. Thanks cubanismo for spurring me on to try again.

     

    Command Line Tools

    in Jaguar GameDrive Development

    Posted

    Okay I understand zadig a bit better now. It just replaces windows drivers.

    Zadig recognises Retro HQ Jaguar gamedrive (Interface0 and Interface 1). ie, windows thinks there are two devices in the one Retro HQ jaguar gamedrive device. Interface 0 accepts the WCID driver whilst Interface 1 only lets you install the basic driver. I have tried both types of WinUSB driver (version 6 something). Zadig times out from the driver installation as a FAIL. I have tried multiple times and once had to reboot and discovered that the base drivers had been installed and the device was reported as working! However, JagGD.exe reported that the device is not connected ???.

    I also have tried my PC (Windows 8.1) in different USB ports and the device does not even recognise. (It may have been in device manager but there was nothing on the control panel).

     

     

    Command Line Tools

    in Jaguar GameDrive Development

    Posted

    I tried using Zadig before after trying to get my windows 10 thinkpad working with my skunkboard. I tried following CJ's instructions but to be honest rushed it before understanding what i was doing. I now have a bricked skunkboard!!

    I have tried 2 different leads also.

    I could try a different windows system. Wibndows 8.1 or Windows 10 available but I prefer my Windows 7 laptop for development.

     

AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2023 AtariAge

×
×
  • Create New...