Denial

We're back baby! Can you believe it's been nearly two years since the last release of CBM prg Studio? Well I'm really pleased to announce the release of version 3.14.0.

Here's a list of some of the new features (the bug fix list is too long for this post!):

* Git integration.
* Connect SID tool to MIDI devices.
* Screen editor digitiser tool.
* Sprite editor character import.
* Resize VIC20 screen designs.
* BASIC 7 abbreviations.
* Screen compression.

It hasn't been two years in the making though as I've only recently got back into developing this project after a long break.

I've teamed up with another developer (no the project isn't open source) and we have some very interesting plans for future releases, including more frequent releases.

Finally, for long-term users, thanks for your patience. I'm sure you'll think it's been worth the wait.

The download link is in my signature.

Can't wait to give it a try. I have a good hand full of projects in the works.

I get this every time I try to open sid under tools.

Thanks for reporting this. The best I can say is that it work on my machine! I'm looking at it now.

OK I've uploaded a new version, here's the direct link:

http://www.mediafire.com/file/ntnsjydkw ... 6.zip/file

I also got a similar crash in the screen designer. I'm going back to the old version.

Can you post a screen shot of the crash dump and what you were trying to do? E.g. were you opening an existing screen design or creating one from scratch?

Sorry, couldn't reproduce it. Will advise if it happens again.

CBM Prog Studio is acting weird with a simple basic program that I have written for the VIC-20.

I keep getting errors, they seem to be memory related. I created a simple Space Invader demo with a turret moving back and forth along the bottom under joystick control.

I had an Invader marching back and forth and I could fire a projectile at it. That's as far as I got as I was going to use it as a sample to try and recreate it in assembly. So I started working on my assembly version and it's going just fine, but when I went back to try out my basic version of the program it no longer worked.

I thought it might have somehow become corrupt. so I was cutting and pasting pieces of it from an old previously working version and I get to a point where it stops working and throws up errors. I will send you the file in an email.

You'll see it works but if you add a line [448 return] then it crashes. I try to add an additional 3K in VICE but it still doesn't work. The weird thing is, it was working before with a lot more code at one point so I'm not sure what's going on.

Thanks for any help,

Brian Kumanchik

I have downloaded your archive, but it only contains your BASIC file. The CBM PRG Studio project file would probably be more useful when looking for an IDE problem. What I have done is to create a new unexpanded Vic20 project and added your .bas file to the BASIC folder. I can edit, build and run the program without any errors. I don't use BASIC very much so I'm not sure how much of it is supposed to work at the moment. But it does run and sets up and displays your characters. The defender character at the bottom moves left and right with the joystick and fire produces the first frame of a weapon animation.

I would suggest that your problem may be caused by something that has changed in the CBM PRG Studio project file. Try creating a new project and adding your .bas file. Hopefully that will sort things out.

Just a quick note to say version 4.1.0 of CBM prg Studio has been released. It's mostly a bug fix but there are new features to further support the Kick Assembler and the Mega65 machine.

Enjoy!

Don't fancy watching 'Strictly' tonight? I've just released version 4.2.0 of CBM prg Studio. The main new feature is an overhaul of the project explorer which allows a much more flexible project structure. Please read the release notes (link on the start page) before creating or loading new projects.

Thanks again for your continue support!

Download in my signature.

Unix users might be pleased to learn that it fires up in WINE.

Thanks for that, I'm pleased to hear it too!

OK, if it works in Wine then I am going to give it a whirl.