Main > Software Forum

MAME Movie Maker released

<< < (32/153) > >>

Buddabing:
I've created a -moviesquare flag which will resize the movies to 256x256. Someone familiar with 3darcade or Dragon King should try this and make sure this is what they want.

I fixed a small bug where if a black screen went on forever then the movie would never end. This typically is a problem only with non-working games.

I've uploaded new binaries and source to both version 0.89 and version 0.90.


Buddabing:

--- Quote from: Minwah on January 14, 2005, 10:43:40 am ---
--- Quote from: Buddabing on January 13, 2005, 12:38:31 pm ---I have a new version of ListGen available, too. No major changes, I made it so that the batch file created to make movies doesn't have the copy and delete steps at the beginning and end.

--- End quote ---

Sorry for being dumb but where can I get this?

--- End quote ---

The latest ListGen is here. I made the MAME version detection match what is projected to be the future naming convention of MAME. They are planning to have MAME go to 0.100 instead of 1.0 after 0.99. This would have broken the previous version of ListGen. There probably should be smarter detection code for very early versions of MAME.

Howard_Casto:

--- Quote from: Buddabing on January 14, 2005, 08:55:29 am ---I'm confused about this a bit. Won't the videos look funny if they are resized to exactly 256x256 or 255x255? Shouldn't we make the -longest- dimension 256 or 255?

mk 400x254 -> resize to 256x162
tron 480x512 -> resize to 240x256

And which is it, 255 or 256? Can someone tell that by experimentation?

Another thing, aren't 256x256 sized textures a features on mostly high-end video cards? I thought that a good chunk of mid-sized cards had a 128x128 texture limit.

--- End quote ---

This is very true.... however, both dx and opengl automatically break the texture up into blocks and re-assemble them.  In all honesty 128 would be the most compatable size, however, chances are if you have a video card that old (256 has been the standard for about 3 years now)  you won't be running 3darcade or dk anyway.  Also one break isn't so bad, assuming it's a power of 16 break. Several odd-sized breaks are what kill more modest systems.

It's convoluted and compliacted, but it all draws down to the fact that normal pc games pre-cache all textures, but because all of our textures are external (artwork, frames grabbed off the video)  we have to load a ton, constantly, on the fly.  This makes front ends very video card intensive, even the gdi based ones. 


Out of curiosity, what settings are you guys running mame on when you capture?  I tried it for the heck of it last night and I was getting a puny 3 fps.  Also mame kept complaining about "e:\test" or something to that degree. 

Buddabing:

--- Quote ---
Out of curiosity, what settings are you guys running mame on when you capture?
--- End quote ---

2600:
Movies are being created fine, but the loop detection seems to be a problem for me on some games.

Aquajack is one.  It cuts out way too soon.

Others, I'm not sure why the BIOS type screens are there.   MK series or radikalb.


Any ideas, I tried changing the movieloops flag, but that wasn't it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version