Omnimaga
General Discussion => Other Discussions => Humour and Jokes => Topic started by: DJ Omnimaga on June 29, 2010, 08:51:53 pm
-
Once capture starts, wait at least 15 minutes before taking any action on the emulated calculator. People will be very happy to wait until the program you wanted to show is ran. Plus nobody cares about dial-up users anymore, anyway.
Also, people usually don't mind waiting an additional 5 minute if you mess up several times when trying to select commands in the CATALOG or programs in the PRGM menu, so don't worry about this too much either. People will be fine.
-
Shouldn't you also take the time to scroll through all of your code, in all of the programs for your project?
-
yes. every single byte must be shown. there are two approaches to this
1) pause at 7 lines. i'm sure the reader will be able to decipher your code that quickly.
2) scroll as quickly as possible, making it as non-readable as possible. if you choose this option, it's suggested you scroll through the program multiple times unnecessarily.
-
Remember to BREAK the program at inappropriate spots for your audience to get a burning curiosity of "what happens next" and cause them to download your project.
-
Also, randomly simulate pulling a battery just to prove that all programs get RAM Clears. :P
-
Anyway, here is a new screenshot of my game attached below!
-
That is great ;D Really makes me want to play that game!
EDIT: Shouldn't this be in Randomness? Somehow, I don't think the conversation here is exactly serious, if you know what I mean :D
Also, randomly simulate pulling a battery just to prove that all programs get RAM Clears. :P
Is there a way to do that? I've tried, but no emulator allows this :P Is there a program to simulate battery pulling?
yes. every single byte must be shown. there are two approaches to this
1) pause at 7 lines. i'm sure the reader will be able to decipher your code that quickly.
2) scroll as quickly as possible, making it as non-readable as possible. if you choose this option, it's suggested you scroll through the program multiple times unnecessarily.
Unless, of course, you don't want your source to be viewable. In that case (assuming you're screenshotting an ASM program) unlock the program and start showing all the garbage tokens :)
-
Also, randomly simulate pulling a battery just to prove that all programs get RAM Clears. :P
Is there a way to do that? I've tried, but no emulator allows this :P Is there a program to simulate battery pulling?
In the version of Wabbit that I use, I click Debug and then Reset to get a RAM Clear. :)
-
Yeah, that would work for most purposes, but I had a problem a few weeks ago where I tried to load a 3rd-party OS into, say, TI-Smartview (I know, it's definitely not the best emulator, but it's the only one I've found so far that allows loading .8xu files), but I couldn't find a way to do the battery trick to prevent the validation check.
-
I didn't put it in Randomness since I wanted guests to see it too :P
Btw, yes, my first post is full of sarcasm :P I just recently got through watching two unnecessary long screenshots for a project and gave up halfway through (before the program itself was even shown in action)
-
Link please? :D
-
I forgot, I know one was by Qazz42 on Cemetech but I forgot if it was on IRC or forums. The other was by JoeYoung, but did not even come close to top Qazz42 one. I think JoeYoung was just only one or two minutes wait before running the stuff he wanted to show :P
-
:D I actually nearly did that once. I left WabbitEmu in Record mode for a few minutes, then started to take the screenshot. But then I realized that it had already been recording for a while.
I like how the new WabbitEmu shows a dynamic blue border around the screen when it's recording. It becomes helpful in situations like this :)
-
Yeah true. It doesn't work in every skin, though.
-
Maybe we could make an entire list of "Screenshotting Guidelines" like "2^6 Ways to Get Your Files Accepted to ticalc.org"?
Unfortunately, 2^1 (or 2^1+1 or 2^2, I don't know how many we're at) doesn't make a good list.
More guidelines! :P
-
Make sure you demonstrate all your quadratic solvers and other effin 1337 math t00lz first, in order to warm up the audience. Then, get to business.
-
Post counts probably shouldn't increase in this topic, at least.
Anyway, another tip: Slow your emulator down, way down. You want your audience to notice every detail.
-
yeah I agree. It was more of a sarcastic rant to begin with but then it turned into a "1000 ways to annoy people with animated screenshots" thread, so I am gonna move it to Randomness :P
Also, when slowing the emu down, screenshooting will still be done at max speed, meaning your screenshot will revert emulation back to 100% speed once saved. You have to use CalcCapture or another third-party screenshotter to achieve such slow emu
-
Doesn't Wabbit now have an option to choose your export framerate?
-
It does, but the screenshot will always play at the 100% emulator emulation speed, regardless of the speed at which you were emulating. Meaning, if a game was played at 5%, the screenshot will be speed up to 100. Pretty handy to make tool-assisted runs.
That's of course unless you use Internets Exploder, which caps animated GIF playback at 10 FPS.
-
Internets Exploder
Haha nice, I'll have to remember that one ;D
-
Hi and welcome to part II of my screenshooting tutorial!
Today we are gonna cover comments on your game. When you create an animated screenshot, you must be as informative as possible. Before running your program, type what you are going to do inside the emulator while you are capturing. To leave at least 5 minutes for people to read the text, you must delete it using the DEL key afterward, not CLEAR. Before executing the program, remember that you must explain every single thing that happen inside the screenshot. It's also a good idea to quit the program while explaining. Afterward you just run it again all the way through until where you left off.
It's ok if you accidentally erase your entire text or correct mistakes during capture.
Good luck in full lenght movie creation!
-
Shouldn't you also take the time to scroll through all of your code, in all of the programs for your project?
A better method is to type all the code out while you're taking the screenshot. ASM programs are exempt, however, due to the tedium of typing hex.
-
ASM programs are exempt, however, due to the tedium of typing hex.
(http://www.omnimaga.org/index.php?action=dlattach;topic=4672.0;attach=3590;image)
;)
-
Even better ;D
-
ASM programs are exempt, however, due to the tedium of typing hex.
(http://www.omnimaga.org/index.php?action=dlattach;topic=4672.0;attach=3590;image)
;)
Too short. You need to write Wolfenstein into the program for kicks.
-
ASM programs are exempt, however, due to the tedium of typing hex.
(http://www.omnimaga.org/index.php?action=dlattach;topic=4672.0;attach=3590;image)
;)
O.O
Lol, now if only ASM was so easy we could type that fast when coding, E:SoR 2 and 3 would be out by now. ;D
It's insane all the code we need to do things like grayscale, though. X.x
-
ASM programs are exempt, however, due to the tedium of typing hex.
(http://www.omnimaga.org/index.php?action=dlattach;topic=4672.0;attach=3590;image)
;)
O.O
Lol, now if only ASM was so easy we could type that fast when coding, E:SoR 2 and 3 would be out by now. ;D
It's insane all the code we need to do things like grayscale, though. X.x
And then there's Axe ^-^
Was that TAS'd, or does someone really type that fast? Should be easier with Wabbit, I guess.
-
I'M pretty sure this was TAS'ed.
-
Bump:
-As tr1p1ea just mentionned now in #omnimaga, it's also a good idea to show off your title screen menu when making animated screenshots. Make sure to navigate in the game's main menu for at least 5 minutes before showing any gameplay. People won't mind waiting since they absolutely want to see how long your text is in the credits section.
-People also like to see proof that your program was made in Axe. So before starting the game, show off the entire compiling process, even if it takes minutes due to the incredibly slow compiling process of the last few Axe builds (the ones with a progress bar).
-When doing the above, people enjoy seeing your typing skills when you try to type in the PRGM name in order to run it. You win two cookies if you fail less than 3 times at typing it. :)