Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

Community Reputation

450 Excellent


About BitJag

  • Rank

Contact / Social Media

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

6,816 profile views
  1. @dilinger It seems like adjusting the source for variable DPI scaling would be the good long term solution. I dug into the Qt environment variables in the past, and recently in case of Qt changes, to see if there might be some possibility that some global option could be adjusted to fix it. There doesn't seem to be a quick fix when it comes to environment variables at the moment. I used this documentation as a resource. https://doc.qt.io/qt-5/highdpi.html . With the exception of the hack suggested above, adding in the functions to handle scaling is beyond me at this point.
  2. I have ran into this problem a few times running VJ in Linux, specifically Kubuntu 18.04 and later over the last few years, where the image of the game being played doesn't fill the window size or fullscreen properly. I have found a solution modifying the source for VJ, but I wanted to ask if there might be a simpler way of altering the code to achieve the same fix. I also wanted to make this post with the solution I have been using in case anyone else out there might be running into the same problem, and there isn't a better way to do this currently. Below is an image of what I am experiencing when opening VJ, and it holds true when playing a game windowed or in full screen. I am using version 2.1.3(final) source from the git repository. Here is a solution I am currently using to fix this. Before building Virtual Jaguar perform the following modifications to the source code: /src/gui/mainwin.cpp - Add the following line in the function MainWin::SetFullScreen, below the line where int newWidth is initialized. The line looks like this "int newWidth = (int)(aspectRatio * (double)r.height());". newWidth *= 2.2; Then alter the line just below, that looks like this "videoWidget->offset = (r.width() - newWidth) / 2;", multiplying r.width() by 2.2. It should now look like the line below. videoWidget->offset = ((r.width() * 2.2) - newWidth) / 2; /src/gui/glwidget.cpp - Now we need to multiply width() and hieght() function calls by 2.2, do this by altering the following lines. outputWidth = width(); --> changes to --> outputWidth = width() * 2.2; unsigned outputHeight = height(); --> changes to --> unsigned outputHeight = height() * 2.2; EDIT: I forgot to mention that the value 2.2 is a bit arbitrary according the the global scaling on your desktop. I actually don't know how to find the exact value you need according to a specific global desktop scaling. But raising and lowering the value should get what you are looking for. For example, 2.2 is scales the image a bit beyond the window and fullscreen borders, so I dropped it down to 1.75, and if fits great now.
  3. BitJag


    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.
  4. @agradeneu @CyranoJ Beautiful!
  5. Here is my small review of this wonderful modification. I have only played a few games with it including Pitfall, Ultra Vortek and Xenon II. Each of these were much more enjoyable with this controller. I imagine it will be difficult for me to go back to a normal pro controller or standard controller after using one of these. A blessing and a curse.
  6. The drop shadow method works as mentioned by @Sporadic . Below is a manual and possibly more precise method in Gimp in case you need it. These steps below essentially break down the process that an automatic drop shadow plugin might perform to the basic tools/filters that most raster programs have these days. These specific instructions are for Gimp, but are applicable for any program that has these basic tools. Layers (with per-layer opacity adjustment), alpha selection/color selection/lasso tool, fill tool, and gaussian blur. Make sure that the subject you want to add the dark halo to is on a layer that is has transparency. Create a white layer beneath it so we can see the halo effect. Create a new layer between our subject layer and the white background layer that is empty/transparent. Right-click on the layer with you subject and select "alpha to selection". If your program doesn't have a quick alpha selection option, you can use a select by color, or manually select the outline of your subject with a selection lasso tool. Make sure our empty transparent layer is selected, then use the bucket fill tool to fill the selection with black, or whatever color you wish. Then deselect everything. top menu>select>none. Apply a gaussian blur. top menu>filters>blur>gaussian blur. Adjust the blur value accordingly, matching X and Y values (amount of blur will be different depending on your image resolution). And then click OK. This probably won't be dark enough for what you need, keep reading. Duplicate the now blurred black layer two or three times using the duplicate button in your layers panel. I usually duplicate until the halo is a bit darker than I want so I can tune it more precisely later. Then merge back down to one blurred black layer, by selecting the top blurred black layer (under your subject layer), and then selecting top menu>layer>merge down. Repeat this step until you are left with just one blurred black layer between your top subject layer, and your bottom background layer. Now adjust the intensity by using the blurred black layer's opacity slider in the layer panel.
  7. @LinkoVitch Thank for the troubleshooting options. I will try these before putting anyone through the brutal task of unsoldering and resoldering all of those pins.
  8. Boy do I feel stupid. The part number is on Best's website. It is SC414201FT. This thread can be deleted, or left as an eternal monument to my shame 😆 It looks like I will need to cannibalize another non-working jaguar or deal with the audio issues until the console finally dies. I guess while this is still up, does anyone happen to have a 6SC600HF106 DSP laying around that they would be willing to sell me?
  9. I am looking to replace what I believe is a failing DSP in my Jaguar. I have a few games where the audio has issues (Atari Karts & Some of Reboot's Games). Symptoms are audio doesn't play at all, games crash, or audio runs at a fraction of the speed it should. I have confirmed that these same games work just fine on two of my other Jags. A few people have suggested that the DSP is failing. I am open to other ideas other than replacing the DSP if there are other things that I should check/replace before one of the primary processors on the board. Best Electronics has replacements, but they can only replace Jags that have the "2nd Generation" DSP. Is there a sure way to identify whether or not the Jaguar has a 1st or 2nd generation DSP? After compiling the list below, it seems that there are only two part numbers for the DSP, SC414201FT and 6SC600HF106. I am assuming right now that SC414201FT is the 2nd generation DSP since it has a later range of manufacturing dates (9428 to 9506) when compared to 6SC600HF106 (earliest 9336 to 9405). Here is the sampling of Jaguar motherboards I used to make this assumption (sorry not very organized, I compiled this as I was writing this post): CPU V1.0 (SC414200AT, AAHCC9436), DSP V1.0 (SC414201FT, IHAC9441) <-- Link to Image CPU V1.0 (SC414200AT, AAHDN9441), DSP V1.0 (SC414201FT, IHAD9440) <-- Link to Image CPU V1.0 (SC414200AT, AAHBQ9428), DSP V1.0 (SC414201FT, IHAB9428) <-- Link to Image CPU V1.0 (SC414200AT, AAHFL9451), DSP V1.0 (SC414201FT, IHAH9506) <-- Link to Image CPU V1.0 (6SC880HF106, 9336YAI), DSP V1.0 (6SC600HF106, 9336EAI) <-- Link to Image CPU V1.0 (6SC880HF106, 9350YAI), DSP V1.0 (6SC600HF106, 9336EAI) <-- Link to Image CPU v1.0 (SC414200AT, AAHFJ9450), DSP V1.0 (SC414201FT, IHAF9449) <-- Link to Image - CoJag Arcade Board CPU V1.1 (6SC880HF106, 9417EAI), DSP V1.0 (6SC600HF106, 9405EAI) <-- Link to Image - My Jaguar that is having audio issues. CPU V1.1 (6SC880HF106, 9408YAI), DSP V1.0 (6SC600HF106, 9405EAI) <-- Link to Image CPU V1.1 (6SC880HF106, 9417EAI), DSP V1.0 (SC14201FT, IHAE9424) <-- Link to Image CPU V1.1 (6SC880HF106, 9417EAI), DSP V1.0 (6SC600HF106, 9345EAI) <-- Link to Image CPU V1.1 (6SC880HF106, 9417EAI), DSP V1.0 (SC414201FT, IHAD9433) <-- Link to Image More out there... I am looking for a second opinion before buying since the costs to get a replacement and then having someone replace it will be considerable (but still less then a new Jag). Thanks for the help!
  10. No time to build it for you, but I did setup a repository for a cygwin version of the setup script for my brother earlier this year to see if it could be done. We were able to get it working. Cygwin RMVLIB setup script - https://github.com/lachoneus/windows-cygwin-rmvlib-install-scripts Here is the bad news. I haven't been updating it along with my linux script. If you are adventurous though, and you have some experience with bash scripts, you can do a side by side with the linux script(latest version) and the cygwin script(older version) and update the cygwin script, along with the necessary files it may need from the linux script's repository, you should be able to get it working. I believe rmac has been updated since I put together this script, so some of the lines that manually change rmac source files aren't required anymore. There may be a few other small things as well. I may approach this again in the future, but my focus is making sure the linux scripts are up to date until I finish Crescent Memories (someday...).
  11. Spent a few minutes with the docker image. Followed instructions after getting familiar with the basics of docker. It seemed to setup the docker container flawlessly, and I had my generic example built in no time after modifying my Makefile's a bit. This is awesome, I need to try this in Windows now. I am not sure what feedback you are looking for, for the Jaguar Image Converter. Its great that it is just a python script now, and this will be great in case of future updates. Unfortunately I haven't worked on enough Jag stuff to justify using all the options that the image converter offers. I did do some quick conversions to make sure that the options I typically use still work. 4, 8, 16-bit image depths all converted just fine. I actually avoid the dithering options in the image converter, as I like my work to look the same before and after it is added to my programs. I am looking forward to using an up-to-date version of the image converter. Thanks for putting this together Seb!
  12. There is a possibility that our streaming time will change in the next couple to be a bit later on the same day. Hopefully it doesn't end up in the middle of your workday... 😋
  13. No worries. We appreciate you and the few other regulars that join us and chat when we are wasting time.
  14. We did a live stream of Wormhole 2000 yesterday, with an on the spot review. The three of us really found the game entertaining even though it is a bit rough around the corners. Only one of us actually owns a Jag, and I recommend this game for anyone who likes playing and collecting homebrew for the Jag, but you may want to hold off until it is being sold through AtariAge to get a complete package (game, box and manual). The actual gameplay starts around the 33 minute mark. We like giving the VLM some love before going to meat of the stream.
  • Create New...