| |
Stablizer
Registered: Jan 2016
Posts: 19 |
Coding on a PC for the 64?
I've seen various editors out there, currently starting to use the C64Studio for this, but it seems like getting charsets, graphics, music, etc, is a bit problematic when going at it this way, isn't it?
Would love to get some pointers to reading material on the subject (have done some searches already, but haven't come up with anything notable really).
Thanks!
-Stab |
|
... 179 posts hidden. Click here to view all posts....
|
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
Quote: using that "binary bullshit" is part of coding 65xx assembler imho as it forces you to learn about memory mapping which you sooner or later want/need anyway, e.g. when you need to split a prefigured gfx file format such as .kla into bitmap/colram/screen data or wanna cut off unneeded charset data
this has nothing to do with memory mapping, its how much you fuck to get the data you want
kickass will do that .kla split for you in 1 line. with other assemblers you have to fuck with some other tool to get the damned thing sliced up.
kickass will import for you koala from pc formats, or sprites, or music from a .sid. |
| |
Endurion
Registered: Mar 2007
Posts: 73 |
There is a help available (default F1). Pressing F1 while on an opcode shows info on it.
At the bottom of the help start page is a link to AAY, a very neat compendium of the C64s Kernal and VIC/SID registers.
Also note, when you're using a solution you can set the assembler type to a different one (DASM, PDS syntax) in the properties (right-click in Solution Explorer) |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
Quote: this has nothing to do with memory mapping, its how much you fuck to get the data you want
kickass will do that .kla split for you in 1 line. with other assemblers you have to fuck with some other tool to get the damned thing sliced up.
kickass will import for you koala from pc formats, or sprites, or music from a .sid.
Wrong.
* = koala_bitmap
!bin "pic.kla",$1f40,2
* = koala_screen
!bin "pic.kla",$3e8,$1f42
Looks pretty clear to me. No manual splitting needed. |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
indeed, anyhow I seriously think about using kickass even if just for prechewing gfx data. it can solve about any task, not just this split thing. |
| |
Axis/Oxyron
Account closed
Registered: Apr 2007
Posts: 91 |
I always tend to use the most simple and slim solution. In my case Notepad++, DreamAss, Subversion and some self-made scripts for Notepad++ to build and execute via hotkey. Thats not as luxurious as some duper-duper studio whatever solution. But, when I run into trouble, theres always a 5 minute way to fix it. And thats worth alot, because you always run into trouble someday. Most likely the day of your deadline. |
| |
Monte Carlos
Registered: Jun 2004
Posts: 359 |
I'm currently using Codeblocks http://www.codeblocks.org/.
If interested, i could send you the hilighters and output parsing configuration. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Quote:it can solve about any task
if only |
| |
Perplex
Registered: Feb 2009
Posts: 255 |
I prefer many small tools that do one thing each and do it well, and that can be combined in a limitless number of ways that even the authors themselves never thought about. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
indeed |
| |
Stablizer
Registered: Jan 2016
Posts: 19 |
agreed |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | ... | 19 - Next |
