Herzlich willkommen in unserem Gästebuch!

Zum Eintragen hier klicken.

Zeige Einträge 13 bis 24 von 205

Seite: [«] [[1(2) [3[4[5[] [»]

Name Kommentar

s IP angucken

erstellt am 26. Juli 2021 um 6:34 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hi Georg,

I looked through your ScrollWorkshop. Nice!.

In 2013? you did a tutorial on SUPERNATURAL,
Is it too possible for you to make a TUTORIAL on a Fast Horizontal Shoot'em up, like X-OUT?. Double buffering screens. Maybe 2 or three levels for example.

Kind regards


Kommentar von Endurion:
Whoa, now that's quite a big ask fröhlich

For that I'd have to create an actual game. Could be interesting though.

s IP angucken

erstellt am 24. Juli 2021 um 15:25 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hi George ,

Please could you example of double buffering , ie screen flipping and scrolling at the same time. . Ie like X-Out.....



Kommentar von Endurion:
Hi Syed,
I actually have something like this, download from https://www.georg-rottensteiner.de/webmisc/ScrollWorkshop.zip

It's a solution with several projects of scrolling in various stages. There's samples with double buffer and color RAM scrolling, horizontal or vertical.

Nothing ground breaking, and no sprites, but maybe a start.

Have fun!

TheHighlanders E-Mail Adresse s IP angucken

erstellt am 20. Juni 2021 um 22:47 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
I can't get debugging to work correctly with C64Studio and the latest Vice3.5 version (downloaded 20-june-2021).

When I use the settings as suggested in the C64Studio help file, execution is interrupted, but on the wrong address. This is regardless of how I set the break point.

These are the settings I use:
-initbreak 0x$(DebugStartAddressHex) -binarymonitor -binarymonitoraddress

I've tried several things but nothing appears to work.

The assembler output window says this:

Calling Cbääärogram Files (x86)GTK3VICE-3.5-win64binx64sc.exe with -truedrive +virtualdev -initbreak 0xa871 -binarymonitor -binarymonitoraddress -moncommands "C:UsersGebruikerAppDataLocalTemptmpBEA6.tmp" "C:devprojectsC64SpriteMultiplexerjmain.prg"
Connection attempt 1 succeeded
Breakpoint at address $A871 has ID 1, enabled True, temporary False
-is an unknown breakpoint
Breakpoint at address $812 has ID 1, enabled True, temporary False

Namely the "-is an unknown breakpoint" seems to indicate a problem.

Do you have any idea what could be wrong?

Kommentar von Endurion:
Hmm, I see that the message "is unknown breakpoint" appears, but that's not the issue. That's me not properly mapping VICE breakpoint IDs to local breakpoint IDs.

I couldn't repeat the problems you have though. It breaks where it's expected to. What makes you think breaks at the wrong address? If it's the $A871, that's my internal setup breakpoint, that's correct. Is $812 the breakpoint you want to hit?

Maybe you can mail me a small snippet that exhibits the issue and/or a video. Anything that helps me recognize the problem is good.

Edit: I just fixed the wrong "is an unknown breakpoint" message, and now I run in the same issue. I remember, it's a bug with VICE 3.5, it's unfortunately still open (https://sourceforge.net/p/vice-emu/bugs/1427/).
So for now, when you want to use the binary interface you need to stay at VICE 3.4 for now.

s IP angucken

erstellt am 27. März 2021 um 3:40 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten

:-( Exact same error this time I tried Wine build 4.1 (most recent dev build is 6.4 or so) I have corefonts and dotnet35sp1 package only in that PoL box. I wouldnt be surprised that mono is lurking somewhere here though I think I remember I got similar messages until I got C64PrgStudio working a while ago. I have a PoL log I could send you too ! Mail me on the mail address in the first post if you have time !

I get this "fixme" error (supposedly not critical (?) wine error)
0009:fixme:font:get_nearest_charset returning DEFAULT_CHARSET face->fs.fsCsb[0] = 20000000 file = L"/usr/share/fonts/truetype/fonts-gujr-extra/aakar-medium.ttf"
Could it be Im missing that font inside of the wine box ?

Kommentar von Endurion:
In case anyone wonders, we found the issue, C64Studio now runs fine under Wine on Linux. Have at it! fröhlich

s IP angucken

erstellt am 25. März 2021 um 17:08 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hello !
I tried again with all rules of the art, installing dotnet35sp1 - this time in the PlayOnLinux system. This time the below error messsages right after splashscreen shows.


I wouldn't be surprised if there was a font error, or MONO error - but I have removed Mono I think (the open .net implementation that is not the best - have to do that on A. Jordisons package too.)

Well I hop you can see the link - if not mail me - on the first post I have my email.

Now FOOD !
Greets !

Kommentar von Endurion:
Awesome, that helps. With that message I could find the cause and work around it. Weirdly that error doesn't appear for me, so I had to resolve to working around.

I've uploaded a wip version to https://www.georg-rottensteiner.de/webmisc/C64StudioRelease.zip

Could you try and see if it works better that way? Unfortunately I can't test, but I'm eager to get it running.

We can also take this to email if you prefer.

Best regards,

s IP angucken

erstellt am 25. März 2021 um 4:36 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hello again !
I tried the commands below but to no avail !
The splash screen shows up and then I get an error message. I got further than last time I tried though!

Do you know what version / build of Wine that worked ? Or what Windows are best ? I see the software needs .NET 3.5 sp1 but could it be that I need some more packages ?
(Some other MS VC++ runtimes ? GDI+ ? Fonts ?)

I could possibly try the sequence of commands again inside the PlayOnLinux system that can run different versions of Wine on the same computer ! Sometimes different versions are better for something and another version are better for other software. (PlayOnLinux is like a virtualbox for Wine I think ! ) Anyway cheers and keep hackin' !!
Greets Dag !

Kommentar von Endurion:

Sorry, I just received that list of commands in a forum thread without further details.
Regarding the packages, I'm already using just vanilla .NET 3.5. There shouldn't be much more that's required.
Can you show me which exception you receive? Maybe it's something I can take a peek at. The C64 true type font loading usually is one of the main issues on startup.

Dag Jacobs. Norways E-Mail Adresse s IP angucken

erstellt am 21. März 2021 um 1:20 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hello !
I would be very happy if I could manage to run your C64 Studio on Linux under Wine.
The C64 prgstudio from A. Jordison runs somewhat ok. But would be nice to see your software running also ! I tried once and got a error message that it said I should forward to you.
Wine on Linux is getting better and better so it might happen it could run some day !

Greets Dag E. !

Kommentar von Endurion:

I had some info that this worked:
o Linux:
WINEPREFIX=~/.winedir WINEARCH=win32 wineboot
WINEPREFIX=~/.winedir winetricks dotnet35sp1 -q
cd ~/.winedir/drive_c/Program Files/C64StudioRelease
WINEPREFIX=~/.winedir wine C64Studio.exe

Is there any specific exception you're running into?

Wouter Bovelanders E-Mail Adresse s IP angucken

erstellt am 31. Januar 2021 um 15:33 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hi Georg,

I have a feature request for C64Studio. I would like to be able to right click on a label and have a list of references to this label. So that I can then double click on a reference and jump to it. It would be neat if that list of references stayed open until I closed it, so that I can quickly inspect all references.

Right now I can click on a label and jump to its declaration. But I'd like to be able to go in the other direction. Find all usages of a label. Right now I can copy and do a Find for it, but I'm lazy.

Hope you think that would be useful.

Kommentar von Endurion:
That sounds quite useful actually, I'll see what I can come up with.
Thanks for the idea!

George Kirkhams E-Mail Adresse s IP angucken

erstellt am 20. Januar 2021 um 4:42 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hi Georg

Apologies, I can't work out how reply to your message below so I thought I'd just repost.

It's great to hear this is something you may look at doing at some point in the future. fröhlich

Yes the CPU is a standard WDC 65C02. A good article listing the additional instructions is:


Also my channel URL was incorrect previously - the correct one showing some of my Commander X16 work:


Let me know if I can be of any assistance or you need anything from me. fröhlich

Best regards,


Kommentar von Endurion:

Thanks for the donation!
I'm currently working out the issues with the new addressing modes. May take a day or two to have it up and running.

We can continue the messages via email. Might be easier fröhlich

If you have some sample code using the new opcodes/addressing modes and the assembled binary for comparison, that might be useful.

We'll be in contact!

George Kirkhams E-Mail Adresse s IP angucken

erstellt am 18. Januar 2021 um 10:38 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
Hi Georg

I just wanted to say I've been using your C64 Studio product for a while now and really enjoy it and think it's a very useful tool. However I've been using it to develop assembly language programs for a new 8 bit computer - the Commander X16. Examples of my work can be found here:


It's still in the advanced prototype phase and Michael Steil has produced an emulator for it. More details can be found here:


The heart of the machine is a WD 65C02. I was wondering if you could extend your C64 Studio to cover the additional opcodes, e.g. PLY/PHY, PLX/PHX, INCA, BRA etc and the new addressing modes. I have currently implemented a few using Macros but it would be great if it could natively compile them.

Anyway completely understand if you're busy with other projects but thought I would ask.

Keep up the great work!



Kommentar von Endurion:
First of all, thanks for the feedback! fröhlich
Interesting regarding the new opcodes.

I have only half assed support for other processors, but that could be a good exercise. However I can't promise anything, nor how fast I could make it happen.

Especially adding new addressing modes is not completely trivial.
I'll think about it fröhlich

Is there a full list of the supported opcodes? On a first quick glance I couldn't find it. Ah, it's a generic WD 65C02. Fine then fröhlich

The BASIC could actually work already with the new BASIC dialect support. You can add a new text file listing all BASIC commands and their one or two byte token values.

Julians E-Mail Adresse s IP angucken

erstellt am 23. Dezember 2020 um 12:25 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten
(Antwort auf den letzten Kommentar)
Bei mir steht als Startadresse $0884 und als Ende $08Ax, da stimmen die 43 also, zumindest in etwa, aber ich nutze noch die Version 6.4. Vielleicht sollte ich mal updaten ...

Abgesehen davon, eine kleine Anregung: Wenn man keinen Step setzt, wird ja automatisch 1 genommen. Wie wäre es, wenn automatisch -1 genommen wird, wenn der Startwert größer als der Endwert ist? Man könnte nebenbei noch eine Warnung angeben, aber eben keinen Fehler.

Julians E-Mail Adresse s IP angucken

erstellt am 22. Dezember 2020 um 17:49 Uhr MEZ   Eintrag löschen  Kommentar hinzufügen  Eintrag bearbeiten

ich hätte da eine Frage:

!for i = 3 to 0 step -1
!for j = 0 to 39 step 1
!byte (i * 40) + j

Wenn ich mir das so angucke, würde ich sagen, dass das 4 * 40 Bytes sein müssten. Tatsächlich sind es aber nur 43 und absurderweise verbrauchen die Lines mit !end jeweils 3 Bytes. Da ist irgendwas schiefgegangen ... oder ist das so richtig?

Kommentar von Endurion:
Da ist leider die Anzeige mit den Bytes pro Zeile nicht korrekt. Nehme ich direkt als Bug auf, danke!

Wenn du auf die Adressen der beiden !ends guckst, werden dann insgesamt doch die erwarteten 160 Bytes erzeugt.

Mit dem Aufaddieren der Bytes einer Zeile, die mehrfach verwendet wird, habe ich offenbar doch noch Probleme fröhlich

Seite: [«] [[1(2) [3[4[5[] [»]


Gästebuch Hauptseite | Meine Hauptseite

powered by unzes gb 3.1.1
© 2001 - 2003 by Daniel Köhler