|
Mousecursors in 4k Intros |
| category: code |
|
|
Quote:And while we are at topic of sync, care to share ideas of what do you use to prevent this 3 frame bufering?
add dword [esp+1*4], 2048*4
:-/ |
|
|
|
care to elaborate blueberry? perhaps in c? |
|
|
|
well, looks like a fixed sample/time delta to me :) |
|
|
in 4ks i dont care!
in 64k i would care!
but not in 4096 lousy bytes!
fuck the mousecursor (everyone is able to move it offscreen still!)
fuck timing-issues (just try avoiding them atleast! 4klang does that for you.)
even with crinkler removing most of the PE-Header and smallest setup, we still waste way too many bytes on setting up a stupid window to render on already, so i dont waste any additional byte on unneeded features! you always can have a final-version with Resolution-Dialogue etc, which also has those additional features! (as long as you have a working <4096b-version of the same intro next to it!) |
|
|
Well hardy - those things are "nice to have features" - and they are pretty low cost, sizewise. If I can have those - I would favor all those features over some lame default font crap rendering "TRSI" "hardy" etc..
Btw. I "measured" the "cost" it was around ~4 compressed bytes... And I might have found another thing that gave me 1-9 compressed bytes (depending on the context, we're still checking compatibility - but it seems to be nice.).
In case anyone is not able to hide the mouse cursor with the provided code in 4096 bytes and your intro is <= 4096 bytes without that one PeekMessageA call, I'll help you doing it (In case you trust me enough to give me the source/toolchain + the deadline is not in 60 minutes - having >=1 day is cool). |
|
|
|
In case of doubt I'd vote for the 4k that is able to hide the mouse cursor. |
|
|
Code:we still waste way too many bytes on setting up a stupid window to render on already, so i dont waste any additional byte on unneeded features! you always can have a final-version with Resolution-Dialogue etc, which also has those additional features! (as long as you have a working <4096b-version of the same intro next to it!)
i strongly disagree. a 4k intro ahs to be a robust 4k intro, not a zip with crappy 4k coding exercise plus a 20 kilobyte demo. if yo cannot make 4k intros, then don't make them, just go for 64k. if you think you can do 4k intros, then make them proper, robust and good looking. in fact, i think hiding the mouse cursor should be mandatory, just like the ESC key ("hey dude, anybody can open the task manager and kill the intro anyway"), and and having a good timing is crucial. i don't see how sparing some extra 20 bytes is a problem. if you need those 20 bytes, well, optimize your code (or remove that last greet. done) |
|
|
Quote:even with crinkler removing most of the PE-Header and smallest setup, we still waste way too many bytes on setting up a stupid window to render on already, so i dont waste any additional byte on unneeded features!
Yeah, we waste more than half a kilobyte on stupid Windows boilerplate, and we only get a lousy handful of graphics and sound APIs in return. It's not fair! |
|
|
1. Write a virus, with the typical 4k's boilerplate code as its payload. Throw-in a few things like ray-marching primitives and a synth
2. Infect 99.9% of the potential audience
3. Call the virus payload from your demo
4. TEH ULTIMATE 1337^2 4K |
|
|
|
5. never visit a demoparty again. |
|
|
|
:D |
|
|
|
;) |
|
|
|
|
