Urgent SCENE-REQUEST: Please get your releases Win7 (x64) compatible!!
category: general [glöplog]
Hey guys,
just wanted to place a kind request on here to ALL CODERS (mainly the 4k intro coders though ;-) ) !
PLEASE get your tools updated to be Win7 (x64) compatible !!
At the moment it's pretty sad to see many of all those amazing 4k intros not working with Win7 64bit anymore mainly cause of the usage of an old/outdated/incompatible CRINKLER still used all over the place.
Although there IS a way to get it compiled and working with win7 x64 without any problems (see 'elevated' as a positive example here! It got re-released and works perfectly now with Win7, too! :-) )
So PLEASE, everyone, try to keep this in mind for all your future releases or otherwise many sceners, fans and other people won't be able to watch all those great productions anymore in the near future!
Thanks a lot for reading and also _spreading_ this word throughout the _whole_ scene as well ! ;-)
Bye,
Weasel
just wanted to place a kind request on here to ALL CODERS (mainly the 4k intro coders though ;-) ) !
PLEASE get your tools updated to be Win7 (x64) compatible !!
At the moment it's pretty sad to see many of all those amazing 4k intros not working with Win7 64bit anymore mainly cause of the usage of an old/outdated/incompatible CRINKLER still used all over the place.
Although there IS a way to get it compiled and working with win7 x64 without any problems (see 'elevated' as a positive example here! It got re-released and works perfectly now with Win7, too! :-) )
So PLEASE, everyone, try to keep this in mind for all your future releases or otherwise many sceners, fans and other people won't be able to watch all those great productions anymore in the near future!
Thanks a lot for reading and also _spreading_ this word throughout the _whole_ scene as well ! ;-)
Bye,
Weasel
Please make them also Linux-compatible. Both 32 and 64-bit.
Weasel, have you tried crinkler's /RECOMPRESS? I thank that's exactly the solution to your problem.
It's more important to make F-secure stop thinking crinkler is a trojan :)
@zerkman: yeah, that should be easy... it's not like there were a lot of years of brainpower involved (not to mention certain preinstalled software libraries) to create those magical 4k intros we see today. let's just do the same on linux, where software variety and missing libraries are no problem at all...
Another problem is that most dx9 4ks refuse to run on my dual screen win7 setups with aero enabled.
When resolution is changed (by createdevice) Aero reinitializes on the 2nd desktop causing the intro to loose it's device. So a device.reset is needed a bit after the createdevice, not immediatly (and before you start using it ofcourse). We generate the music in between.
When resolution is changed (by createdevice) Aero reinitializes on the 2nd desktop causing the intro to loose it's device. So a device.reset is needed a bit after the createdevice, not immediatly (and before you start using it ofcourse). We generate the music in between.
RTFM.
Aske beatdown :o)
---> STAY THE FUCK!
---> STAY THE FUCK!
lol@urgent scene request
but yes 4ks...
they proof to be a problem in win7 x64, especially if they are older that win7 itself.
maybe a new approach is needed to "conserve" these great pieces of art for the future.
for the old releases maybe a kind of sandbox which emulates xp x86 or something would be the way to go, for newer prods id like a dialoged-version (which exceeds 4k then of course) which i believe is not liked much by many groups/coders since they are proud of their small size (imagine that! ;).
so maybe there should be some sort of 4k player app. so the intro itself is actually not an exe but a .4ki or something and the player is able to execute the code and set some parameters around it, include the decruncher or whatnot.
the player app would most likely have to be generic (hence not a new/custom version for every prod) so we can be sure theres actually no intro-code hidden in it.
og course the x64 problem exists with some other prods but 4ks too but those filesizes are usually big enough to be fixable (if the group/coder cares about it that is).
oh and im not talking crinkler here. a /recompress is easily done but sadly thats not always the solution...
well im not a coder so maybe my ideas are totally crap or involve way too much work but i find it increasingly sad that i can only watch about 50% of the 4ks released between 2k5 and now. video-captures dont really do it for them.
but yes 4ks...
they proof to be a problem in win7 x64, especially if they are older that win7 itself.
maybe a new approach is needed to "conserve" these great pieces of art for the future.
for the old releases maybe a kind of sandbox which emulates xp x86 or something would be the way to go, for newer prods id like a dialoged-version (which exceeds 4k then of course) which i believe is not liked much by many groups/coders since they are proud of their small size (imagine that! ;).
so maybe there should be some sort of 4k player app. so the intro itself is actually not an exe but a .4ki or something and the player is able to execute the code and set some parameters around it, include the decruncher or whatnot.
the player app would most likely have to be generic (hence not a new/custom version for every prod) so we can be sure theres actually no intro-code hidden in it.
og course the x64 problem exists with some other prods but 4ks too but those filesizes are usually big enough to be fixable (if the group/coder cares about it that is).
oh and im not talking crinkler here. a /recompress is easily done but sadly thats not always the solution...
well im not a coder so maybe my ideas are totally crap or involve way too much work but i find it increasingly sad that i can only watch about 50% of the 4ks released between 2k5 and now. video-captures dont really do it for them.
The problem touches other domains as well, not only 4ks.
My old (crappy I admit) pc intros were made using DirectDraw, and since Windows XP they stopped working. It's most probably some error in my code, some non checked value on the caps of the system, but still, it used to work on all machines, and now they fail everywhere (except "oh funny" on Wine on linux :p).
And I fear this kind of thing will happen more and more often for all kind of pc things, depending on how well old APi's are kept.
My old (crappy I admit) pc intros were made using DirectDraw, and since Windows XP they stopped working. It's most probably some error in my code, some non checked value on the caps of the system, but still, it used to work on all machines, and now they fail everywhere (except "oh funny" on Wine on linux :p).
And I fear this kind of thing will happen more and more often for all kind of pc things, depending on how well old APi's are kept.
Quote:
for the old releases maybe a kind of sandbox which emulates xp x86 or something would be the way to go
I thought the 64-bit Windowses came with this already?
Quote:
(except "oh funny" on Wine on linux :p)
Quoting myself but...
Quote:
Couldn't get it run in wine but the movie was in technical terms - shit hot.
@doom
yes but that solution is based on virtual-pc which is a VM that emulates the whole pc which is not only bad for performance but also for native hardware access (read: no satisfying 3d acceleration) so its not really usable for demos.
one would need some kind of wrapper that catches the calls x64 cant handle and translates them to something usable.
yes but that solution is based on virtual-pc which is a VM that emulates the whole pc which is not only bad for performance but also for native hardware access (read: no satisfying 3d acceleration) so its not really usable for demos.
one would need some kind of wrapper that catches the calls x64 cant handle and translates them to something usable.
wysiwtf: I was talking about WOW64, which only translates OS functions between 32-bit and 64-bit formats. As I understand it, code runs natively on x64 with no emulation and no overhead worth mentioning. What you can't do is run 32-bit drivers (or other kernel-level code), and there is no support for code injection between 32-bit and 64-bit processes. But that shouldn't matter to a demo.
Maybe you're thinking of IA64?
Maybe you're thinking of IA64?
ney i was talking about the xp-mode in windows 7. which i basically virtualPC with a windows-xp image included.
but that is not 64bit specific.
but that is not 64bit specific.
Phff screw win 7
I have eleven toes. Count them, eleven.
...oh yeah, and what Blueberry said. We have new intros to work on and shouldn't be expected to update our old pieces of crap when two seconds with your command prompt will suffice.
...oh yeah, and what Blueberry said. We have new intros to work on and shouldn't be expected to update our old pieces of crap when two seconds with your command prompt will suffice.
Sure,
I've found many problems running new demos/intros on Win7 (32), not only the ones of last year.
.. And the compo machine at Evoke is a XP. This is a signal.
I've found many problems running new demos/intros on Win7 (32), not only the ones of last year.
.. And the compo machine at Evoke is a XP. This is a signal.
May I ask what this is a signal for?
To be sure we should ask to the Evoke people, I think.
Can one of you give us the answer ?
Can one of you give us the answer ?
42
It all makes sense :O
Win7 64bit runs most demos I've tried just fine but some 4Ks need recrinkling. The biggest problem I have is ATI's strict GLSL compiler on demos coded against nVidia's more forgiving compiler, but there are ways around that.
... but I thought everyone watched the videos anyway ?
Please make all amiga demos compatible with c64!
