+CyranoJ #1 Posted February 5 JagStudio is an advanced development suite for the Atari Jaguar that allows you to code using Assembler, BASIC or C and is based around Reboot's powerful RAPTOR API. Regardless of your programming capabilities, Beginners to Advanced coders can utilize this flexible package that will fully suit the needs of anyone looking to program exciting new games for the Jaguar. The benefits of using JagStudio are the Hardware Abstraction Layers (HALs) and the combination of external modules available to use. This allows you, the developer, to get on with writing your games while taking advantage of the Jaguar's powerful chipset without worrying about tedious, underlying mundane routines. The same results that once took days or weeks to achieve can now be done in a matter of minutes, thanks to the power of JagStudio! You are one click away from 64-bit creativity! The current release of JagStudio along with any previous versions can be obtained at its homepage: https://jagstudio.reboot-games.com Some of the features of JagStudio are: Code in your language preference of Assembly, BASIC or C. (Assembly and C are currently in Beta... help us make them better!) Commands have been renamed (from rB+) to reflect the individual modules they control and prefixed as such: rapPrint, u235PlaySample, etc. RAPTOR API Debug Function brings useful program variable visibility to the forefront, aiding ease of game development. GameDrive support along with MRQ file creation. ROM builder now adds FAST GPU depack by default for quicker startup times. Ability to build and split ROMs up to 6MB into HI/LO for EPROM burning. Updated both RAPTOR and U235 Sound Engine APIs to current versions, bringing additional benefits of both in a single updated package. Added universal JagPad Input - A single call that works with either U235 or ZeroSquare sound engine so projects can be easily converted between the two should your needs change. Many enhancements and bug fixes to the original rB+ code (eg, you can now include files >4mb, all files unpacked using GPU by default) All documentation and examples have been updated with a simple rB+ to JagStudio conversion guide to bring your old projects over to the fully updated JagStudio. Includes project examples for all supported languages (Assembly, BASIC and C) for anyone looking to get started quickly. We plan on keeping this alive and active, with ongoing improvements and new features and look forward to seeing what you all make with it. If you have any questions, please feel free to ask in this newly created sub-forum. Happy coding, everyone! The JagStudio Team. @CyranoJ @Sporadic @Clint Thompson A huge "Thank-You" to ggn for creating rB+ upon which all this is based. Please do not pester him with support requests for JagStudio. 32 12 Quote Share this post Link to post Share on other sites
SlidellMan #2 Posted February 5 Does it include Pro Controller support for those who wanted to develop with it in mind? Quote Share this post Link to post Share on other sites
LordKraken #3 Posted February 5 Great work! This is going to boost the homebrew community! Thanks for adding C, Basic is fun but well, I'm getting to old to go back to basic I've noticed a small issue, the first time I compile a project, virtual jaguar starts with a black screen. Then if I kill VJ and rebuild the project it works. I'm suspecting that VJ starts before the ROM is actually copied at the expected location, but I'll check that later today. By the way are you open to contribution? 4 Quote Share this post Link to post Share on other sites
+Sporadic #4 Posted February 5 12 minutes ago, SlidellMan said: Does it include Pro Controller support for those who wanted to develop with it in mind? The Pro controller extra buttons just map to standard Jag pad buttons. So it works by default. Eg. The shoulder buttons map to number pad 4 and 6 iirc. 1 Quote Share this post Link to post Share on other sites
+Sporadic #5 Posted February 5 2 minutes ago, LordKraken said: Great work! This is going to boost the homebrew community! Thanks for adding C, Basic is fun but well, I'm getting to old to go back to basic I've noticed a small issue, the first time I compile a project, virtual jaguar starts with a black screen. Then if I kill VJ and rebuild the project it works. I'm suspecting that VJ starts before the ROM is actually copied at the expected location, but I'll check that later today. By the way are you open to contribution? Did you just test with one of the example projects to see that issue? Any in particular? Quote Share this post Link to post Share on other sites
SlidellMan #6 Posted February 5 So far, I tried building it with an added "Built With Jag Studio", but keep getting this error: zero_audio.s 3: Warning: CLR.L opcode ignored... build/ramassets.inc 6: Error: cannot open: "build/Built_With_Jag_Studio_160_Trans.png.gfxdata" Build error! Quote Share this post Link to post Share on other sites
+Sporadic #7 Posted February 5 21 minutes ago, SlidellMan said: So far, I tried building it with an added "Built With Jag Studio", but keep getting this error: zero_audio.s 3: Warning: CLR.L opcode ignored... build/ramassets.inc 6: Error: cannot open: "build/Built_With_Jag_Studio_160_Trans.png.gfxdata" Build error! This has highlighted a gap in the docs You need the graphics file to be a .BMP image, PNG won't work. I have attached a converted one for you. I just opened in Paintshop Pro 7 and saved as BMP. If you convert it to a bmp and then use something like this in your assets.txt then it should build; ABS,SPR_NAME,gfx_clut16,ASSETS\GFX\Built_With_Jag_Studio_160_Black.bmp Built_With_Jag_Studio_160_Black.bmp 1 1 Quote Share this post Link to post Share on other sites
matmook #8 Posted February 5 1 hour ago, LordKraken said: Great work! This is going to boost the homebrew community! Thanks for adding C, Basic is fun but well, I'm getting to old to go back to basic I've noticed a small issue, the first time I compile a project, virtual jaguar starts with a black screen. Then if I kill VJ and rebuild the project it works. I'm suspecting that VJ starts before the ROM is actually copied at the expected location, but I'll check that later today. By the way are you open to contribution? Well, this happens to me all the time on the first VJ call, (not with JagStudio and the binary is already in place). I think it's more a VJ issue than a JagStudio issue. Quote Share this post Link to post Share on other sites
SlidellMan #9 Posted February 5 @SporadicThank you for pointing that out. Since I helped you out with Nitrous, it was only reasonable that you would help me. Quote Share this post Link to post Share on other sites
swapd0 #10 Posted February 5 1 hour ago, SlidellMan said: Does it include Pro Controller support for those who wanted to develop with it in mind? There are no difference between a pro controller and a normal controller, it's impossible to detect which one is connected. 1 1 Quote Share this post Link to post Share on other sites
Clint Thompson #11 Posted February 5 RELEASE THE BALLOONS!!! I’ve been preparing a few video tutorials for this that I’ll be uploading soon to help the absolute beginner, hopefully to help further clarify on setting up for getting off the ground and going. The QuickStart guide and included examples are a good place as any to poke around and have all the necessary information to do mostly everything you need. If anyone has any questions, please freely ask in the forums or if you’re not comfortable asking publicly, I’m more than happy to assist in any way I can and am only a private message away. 9 3 Quote Share this post Link to post Share on other sites
+jgkspsx #12 Posted February 5 This is amazing. Malban’s VIDE has been a game-changer for the Vectrex development community and it looks like this will be the same for the Jag. Wonderful work! 1 Quote Share this post Link to post Share on other sites
+CyranoJ #13 Posted February 5 4 hours ago, LordKraken said: I've noticed a small issue, the first time I compile a project, virtual jaguar starts with a black screen. Then if I kill VJ and rebuild the project it works. This might be the BIOS setting. Please make sure it is configured as below in settings: 1 Quote Share this post Link to post Share on other sites
+BitJag #14 Posted February 5 Thanks for continuing to refine these tools. Going to have to give this a spin soon. Awesome to see these tools becoming more accessible over time. 3 Quote Share this post Link to post Share on other sites
LordKraken #15 Posted February 5 @CyranoJ seems it solved the problem thx! 1 Quote Share this post Link to post Share on other sites
+Sauron #16 Posted February 5 Very nice that this supports both Basic and C! Now only if you could add in support for FORTRAN and COBOL.... 1 4 Quote Share this post Link to post Share on other sites
+CyranoJ #17 Posted February 5 45 minutes ago, Sauron said: Very nice that this supports both Basic and C! Now only if you could add in support for FORTRAN and COBOL.... You joke, but the way we've built this if we can find an extendable compiler it might be possible. I'm partial to a bit of Pascal, myself. However, I suspect that Assembler, BASIC and C cover 99.999999% of everyone. Warp 10 is impossible 4 1 Quote Share this post Link to post Share on other sites
Mark2008 #18 Posted February 9 On 2/5/2021 at 5:32 PM, CyranoJ said: You joke, but the way we've built this if we can find an extendable compiler it might be possible. I'm partial to a bit of Pascal, myself. However, I suspect that Assembler, BASIC and C cover 99.999999% of everyone. Warp 10 is impossible Assembler, Basic and C does sound perfect. However, if Lua or Python showed up, that'd be something. I'm probably not going to have time for Jag, but wow, saw this on the home page, what a cool thing.... Quote Share this post Link to post Share on other sites
+Gemintronic #19 Posted February 9 One of us BASIC or C users could probably write ourselves a LUA interpreter and include it in our projects. Store the tokenized LUA code in eeprom / save memory. Thought of something similar for Atari 2600 projects using a SaveKey (or Genesis with battery backed RAM). Why cause real programmers headaches with GOTO usage when you can make unreadable self modifying code as well? 1 1 Quote Share this post Link to post Share on other sites
jefffulton #20 Posted February 12 @Albert I'm going to need a game me Drive for this. When do you think they will be available? Quote Share this post Link to post Share on other sites
Albert #21 Posted February 12 1 minute ago, jefffulton said: @Albert I'm going to need a game me Drive for this. When do you think they will be available? I'll continue to receive waves of Jaguar GameDrives as we work through the long waiting list. Not sure how long it will take to churn through the list. Should have the next batch within a month. ..Al 1 Quote Share this post Link to post Share on other sites
jefffulton #22 Posted February 12 Thanks, @Albert !!! So the next game you need to get Paul Lay to do is the Atari 8bit Galaga. That reminds me, I have to go purchase your latest A8 games. i was saving the $$ for the Jag game drive or the 7800 Multicart, but I can't find those and YOU have the other goods I want. 😃 Rock star! Quote Share this post Link to post Share on other sites
Lavalamp #23 Posted February 13 Would be nice to have Visual Studio Code integration like the awesome Atari Dev Studio for 7800 Basic. 1 Quote Share this post Link to post Share on other sites
SlidellMan #24 Posted February 13 One feature I do look forward to: Jaguar CD support. Quote Share this post Link to post Share on other sites
Clint Thompson #25 Posted February 13 4 minutes ago, Lavalamp said: Would be nice to have Visual Studio Code integration like the awesome Atari Dev Studio for 7800 Basic. I’m not sure what the differences or benefits are but that seems unlikely. The BASIC portion of JagStudio is highly effective and quite easy in the grand scheme of things. Highly recommend you take a peek. 1 minute ago, SlidellMan said: One feature I do look forward to: Jaguar CD support. You can create a 2MB program that will load from JagCD using Jiffi. Outside of that and memory track module support, I believe that’s all you’re going to see now that the focus is shifting to SD. It doesn’t make sense to support a mostly dead format where a superior option exists tbh. Quote Share this post Link to post Share on other sites