knight0fdragon wrote:It seems ImgBurn and create symbolic link files with an optimize option when creating ISOs, I do not know how you create the ISO, but maybe you can use that to your advantage
I did not find the necessary option for this in Imgburn settings. But something like that I think I've seen in UltraISO.
---------------------------
I think I solved the strange problem with the emulator SSF. At least now the game does not crash after the first match. And now there is no need for a separate patch for SSF.
Do you use ultra ISO to make your images? If not what are you using? Right now we have an issue with how ISO's are built in the newest version of windows 10 and the little front end I made to make the translation discs. I currently use mkisofs to make the ISOs because we need a free distributed solution for people to use to make ISOs, if you have an alternative that is free and distributable that I can use, I may make a new program for them to use.
knight0fdragon wrote:Do you use ultra ISO to make your images? If not what are you using? Right now we have an issue with how ISO's are built in the newest version of windows 10 and the little front end I made to make the translation discs. I currently use mkisofs to make the ISOs because we need a free distributed solution for people to use to make ISOs, if you have an alternative that is free and distributable that I can use, I may make a new program for them to use.
I am using mkisofs library too, but with my custom GUI called SIR (Saturn Image Rebuilder). UltraISO has been used after the image was created.
-Mod Edit 2021-
Large image attachment removed due to low storage space.
-- Swalchy
well I did not build the library into my app, I am just going off the executable, but for some reason, it seems to just crash. If you look here http://forums.shiningforcecentral.com/v ... 34&t=26590" onclick="window.open(this.href);return false;, you can see what the users are posting
knight0fdragon wrote:well I did not build the library into my app, I am just going off the executable, but for some reason, it seems to just crash. If you look here http://forums.shiningforcecentral.com/v ... 34&t=26590" onclick="window.open(this.href);return false;, you can see what the users are posting
Paul met, I am a little confused here, how is the resolution 352x240, with the black bars removed? I thought you were adding to the vertical, but it seems you are only making it wide screen at a weird aspect ratio (22x15)
Hmm, I think I see what is happening, the old resolution is probably something like 320x216 after the black bars, and you are giving the video and extra 32x24 pixel (to meet the 4:3 requirements.) and that makes it 352x240.
The only thing I would be worried about is the overscan. I like playing my classics on a CRT, so I wonder how this will work with my TV's overscan
knight0fdragon wrote:
Hmm, I think I see what is happening, the old resolution is probably something like 320x216 after the black bars, and you are giving the video and extra 32x24 pixel (to meet the 4:3 requirements.) and that makes it 352x240.
The native resolution of SFIII is 320x240. But with the black bars viewing area is 320x224 (in battle mode even less).
I not only removed the black bars. I increased horizontal resolution, which in VDP specifications can be up to 352 pixels horizontally.
knight0fdragon wrote:
The only thing I would be worried about is the overscan. I like playing my classics on a CRT, so I wonder how this will work with my TV's overscan
It will works as the rest of the games for Saturn with 352 pixel by horizontal (for example, almost all the games from Capcom).
I am just more curious if the text will get cut off from the top and bottom of the scene, I know with XMen CotA the life meter is almost right up against the edges of my TV, so I can see the same thing happening to this. After I finish up the new tools I will try out this and let you know if overscan is a problem. This way if anybody asks on your post, you will have an answer for them,
Successfully tested S2 in SSF and this can indeed be included with the SF3 translation patch.
I'm wondering if there is any reason this shouldn't be the default. If it works on SSF, Yabause and the real hardware, I don't see why not. Are there any drawbacks or tradeoffs?
Well either way it should't be included by default because of overscan on TVs vary greatly. My 50" LCD uses overscan and has a bug that does not allow for it to be turned off, but perhaps paul_met will be kind enough to make a new version of ISO maker for us, or provide the source to his builder, and we can make it an option to the end user to decide
knight0fdragon wrote:Well either way it should't be included by default because of overscan on TVs vary greatly. My 50" LCD uses overscan and has a bug that does not allow for it to be turned off, but perhaps paul_met will be kind enough to make a new version of ISO maker for us, or provide the source to his builder, and we can make it an option to the end user to decide
It could be as simple as just providing the files outside of the s1, s2, etc. directories and a couple of lines of instructions for the end user to put them in the related folders to be included in the patching process.
But yes, a new patcher could provide a check box to include or not. That would be sweet
Quick question regarding the progress percent of each patch you released. The Shining Force III scenarios are at 90% does the patch have bugs or is there something still left to do?
knight0fdragon wrote:paul_met, I am just writing a new front end since I am now motivated, with your permission, I would like to add the option for your patches when done.
Ok. It will be nice.
Special T wrote:Quick question regarding the progress percent of each patch you released. The Shining Force III scenarios are at 90% does the patch have bugs or is there something still left to do?
I can not test my hack by 100%. To do this, I need to fully complete the game. I have no time for this. For this reason, I write the approximate percentages, because somewhere may appear bugs.
