Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: Cosmos Amiga on May 08, 2016, 08:35:29 AM
-
A new version of Duke Nukem 3D v0.4 is available for 68060 on my forum (the GHOAC for Good Home Of Amiga Classic) : http://www.68kforever.com/forums/showthread.php?1-New-version-is-coming
Some improvements :
- all mul & div 64 bit removed, much better for 060
- the Duke3D: assign removed
- the Duke3D: assign for AmigaSetup removed too
- added a $VER Duke Nukem 3D 0.4 by Dante, Bifat and Cosmos in the main .exe
I'm looking for good coders to optimize the mul64 routines and later the div64 if Frank agree : you are welcome !
-
link broken !
The requested URL /forums/showthr...ming&p=1 was not found on this server.
-
Here is the correct link: http://www.68kforever.com/forums/showthread.php?1-New-version-is-coming&p=1
-
Thanks for the info! I will try it out.
-
Here is the correct link: http://www.68kforever.com/forums/showthread.php?1-New-version-is-coming&p=1
thx !
well apparently you have to register to be able to download and test it !
-
Cosmo, could you upload it to aminet?
Thanks, Amiga deserves decent version of Duke Nukem 3D
-
Ok, I'll put it on Aminet !
A little video : https://www.youtube.com/watch?v=q9CHMV4JIuw
:)
-
WOW! The difference! :)
-
Didn't I already port this years ago?
[youtube]Mef6qbN1B3Y[/youtube]
-
Unbelievable!, and all thanks replacing mul/div 64 bits instructions?
Good work indeed!
The video from NovaCoder seems a slower version; much different rig setup?
-
Unbelievable!, and all thanks replacing mul/div 64 bits instructions?
Good work indeed!
The video from NovaCoder seems a slower version; much different rig setup?
The Nova version is only AGA, that's why I updated the RTG Dante's version
My video show a 3dfx screen !
:)
-
WOW! The difference! :)
I guess a problem somewhere : why I got only 1 fps with the v0.4 ?
Last 68060.library 46.16 installed with Rom2Fast...
I saw another video with this time an Apollo 1260, and Duke run fine (https://www.youtube.com/watch?v=zRdgaRoKdJc)
The next v0.5 is coming soon with a faster Smul64 routine using now the Fpu
Thanks to Matthey for this help !
-
The next v0.5 is coming soon with a faster Smul64 routine using now the Fpu
Using FPU will ruin this version for Vampire owners or not? (Just curious)
-
Using FPU will ruin this version for Vampire owners or not? (Just curious)
Still use the v0.3 on this A600 accelerator...
Explanation : the instructions mul64 & div64 are NOT inside the 68060, so the 68060.library emulate them, and very slowly...
I replaced all of them with instructions who are really inside the 060, so no emulation anymore = big speedup... Oups, still one mul64 into the v0.4, sorry, was in the libnix... The v0.5 will fix that...
I have a new version of BlitzQuake who have the same problem but with sinus & cosinus : I get now 4 fps faster !!
:)
-
The Nova version is only AGA, that's why I updated the RTG Dante's version
I don't understand - aren't we talking C code here, or did Dante optimize the whole thing by porting parts of it to ASM? Libnix certainly is C.
Ok, I'll put it on Aminet !
That requires honoring Duke Nukem's license (GPL). I'm not sure how to do that, if you just patch other people's binaries. But at the very least, the license needs to be mentioned and you need to include an offer to provide interested parties with a way to easily duplicate what you did. I doubt that "I replaced all mul64/div64 instances with 68060 friendly opcodes" will suffice...
Edit: Your forum seems to have a minor SPAM problem: three postings from you, followed by eleven pages of spam postings...
-
I don't understand - aren't we talking C code here, or did Dante optimize the whole thing by porting parts of it to ASM? Libnix certainly is C.
That requires honoring Duke Nukem's license (GPL). I'm not sure how to do that, if you just patch other people's binaries. But at the very least, the license needs to be mentioned and you need to include an offer to provide interested parties with a way to easily duplicate what you did. I doubt that "I replaced all mul64/div64 instances with 68060 friendly opcodes" will suffice...
Edit: Your forum seems to have a minor SPAM problem: three postings from you, followed by eleven pages of spam postings...
Ok, no upload to Aminet...
There are some parts in asm into the Dante's source...
I'll see for the SPAM problem...
-
Explanation : the instructions mul64 & div64 are NOT inside the 68060, so the 68060.library emulate them, and very slowly...
The 64bit MUL and DIV are available in hardware in the apollo core so this optimisation is probably going to make the code run slower on the vampire. Same problem as with most optimisations, you can't optimise for all target hardwares at the same time...
-
Ok, no upload to Aminet...
There are some parts in asm into the Dante's source...
I'll see for the SPAM problem...
http://aminet.net/package/game/shoot/duke3d_amiga_v0.3
Cosmo just upload it to aminet. You can easily "honore duke nuken 3d GPL lisence" like Dante did. I don't want to register french language forum just to download one lha file. It is not anyone interest.
-
You can easily "honore duke nuken 3d GPL lisence" like Dante did.
Dante uploaded the sources along with his binary, which is how you properly honor the license.
I'm just not sure how one would do that if you don't modify the sources but simply patch the binary (assuming that's what Cosmos did). If anybody's got an idea, I'm all ears. Like I said, uploading the file with hint that he replaced this and that wouldn't cut it, IMNSHO.
-
Dante uploaded the sources along with his binary, which is how you properly honor the license.
I'm just not sure how one would do that if you don't modify the sources but simply patch the binary (assuming that's what Cosmos did). If anybody's got an idea, I'm all ears. Like I said, uploading the file with hint that he replaced this and that wouldn't cut it, IMNSHO.
The Dante's source were compiled again with gcc 2.95.3-4 and with updated asm parts...
-
Unbelievable!, and all thanks replacing mul/div 64 bits instructions?
Why simple if it can be done the complicated way... Actually, for those that do not know: There is a small tool on the Aminet ("MuRedox") that can perform such patches in real-time on running binaries. Any manual patching is quite superfluous. Yes, it *also* takes care of the 64-bit multiplication and division instructions.
-
Dante uploaded the sources along with his binary, which is how you properly honor the license.
I'm just not sure how one would do that if you don't modify the sources but simply patch the binary (assuming that's what Cosmos did). If anybody's got an idea, I'm all ears. Like I said, uploading the file with hint that he replaced this and that wouldn't cut it, IMNSHO.
OMG. Anyway Cosmos could release just patch, differences between two binary files, based on Dantes 0.3 version from Aminet, for spatch for example and we have nothing to talk about.
-
what concerns aminet, it looks like cosmos can simply include updated sources, along with asm inlines in his release, no problem. and cg is not nitpicking here on anyones work, he simply needs to ensure license conformity of material published on the repository he is in charge of maintenance.
then again, solution proposed by thor is another viable option, people might not initially think of, rather simply giving up on slow binaries.
-
Why simple if it can be done the complicated way...
Because mul&div64 routines are used a lot :
1/ with a direct replacement, it will be faster than using MuRedox, each cycle is important for this case
2/ Actual integer replacement mul&div64 is a bit slow, fpu version seems even faster
3/ Another secret goal for the moment, maybe for the v0.5
Again, it's not a patch/hack, but a complete compilation with gcc 2.95.3-4
-
Because mul&div64 routines are used a lot :
1/ with a direct replacement, it will be faster than using MuRedox, each cycle is important for this case
Have you measured this or are you guessing? The reason why the emulation is so slow is not because the actual replacement implementation is slow, but rather because the fpsp/isp has to go through a complete decoding cycle of the instruction, i.e. it has to figure out where the data is coming from, fetch it there, and where it is going to, all in supervisor mode with interrupts block. This overhead goes away.
In reality, "mulu" is part of a bigger program and typically not as critical as you may believe. Unless it is really called in a tight loop, more or less as the only instruction within such a loop. So for example, if you compute a Mandelbrot fractal in integer math, the difference between a 32 multiply natively executed by the 68060 or a 64 bit math patched over by MuRedox is measurable - more or less because it is the only instruction in the loop.
In real world, this rarely happens and the multiplication is just a minor part of a bigger algorithm.
-
The Dante's source were compiled again with gcc 2.95.3-4 and with updated asm parts...
Oh? Then I simply misunderstood what you did. In that case, there's no problem of course. Just upload the modified souces along with your binary (in a separate archive, preferably) and make sure you mention the license.
-
So here are some hard facts. FYI, this is measured with DMandel, a fractal generator, quite deeply zoomed in. This runs a couple of multiplications and additions (and nothing else) in a very tight loop, probably around 10000 iterations per pixel, for a 1024x768 XGA screen.
68000 integer (fixed point) math requires 1:33 for the full picture.
68020 integer (fixed point) math: This is based on 64 bit integer operations (add, addx, but also 64x64 multiplication) - 7:20.
68882 FPU: This is using FPU instructions in a tight loop, based on floating point. Note that this does not require explicit scaling (as in the fixed point case) and hence the loop is tighter - 1:08. Surprisingly, the FPU is here faster than the CPU, at least on the 68060. For the 030, this is not the case.
FPU, but via the mathieeedoubbas.library. Essentially, it is using the same instructions as in the 68882 case, but has to go through the ieeedoubbas library interface, hence some "register ping-pong". The loop is hence not very streamlined. - 3:35.
68020 math as above, 64 bit multiplications, but patched with MuRedox: 3:55. So a bit less than a factor of two as speedup, or approximately doubling the overhead for going through an instruction decoding phase.
Note again, this is for calling instructions in a tight loop (probably 20 instructions long), nothing you would typically find in most other applications.
I forgot to say: This is a 68060@50Mhz.
-
Oh? Then I simply misunderstood what you did. In that case, there's no problem of course. Just upload the modified souces along with your binary (in a separate archive, preferably) and make sure you mention the license.
Or an offer to provide the source to anyone who possesses the binary should do to comply with the GPL.
-
Have you measured this or are you guessing?
No precise measure, but it's used A LOT for sure !
The reason why the emulation is so slow is not because the actual replacement implementation is slow, but rather because the fpsp/isp has to go through a complete decoding cycle of the instruction, i.e. it has to figure out where the data is coming from, fetch it there, and where it is going to, all in supervisor mode with interrupts block
Of course, I know.
Inlining is always much better than your MuRedox in this case !
My routines included skip some of your code : no time lost...
Anyway, was very easy to do, maybe one hour of work...
-
Just a few quick notes here since I see a lot of misconceptions about the GPL license.
[ul]
[li]You don't honor the license simply by distributing the source. Binary distributions as well as the source distributions have to include the original license, unchanged, and be released under the terms of that license.[/li]
[li]If you distribute binaries on a network server, you have to distribute the source on a network server as well. That is, if you are offering binaries for download, you have to offer the source for download as well, not simply offer to send the source to someone requesting it.[/li]
[li]Source patches or binary patches are not permissible ways to distribute the source. You honor the license by distributing the full source or simple means to retrieve it(e.g. via a version control system)[/li]
[/ul]
-
Just a few quick notes here since I see a lot of misconceptions about the GPL license.
* You don't honor the license simply by distributing the source. Binary distributions as well as the source distributions have to include the original license, unchanged, and be released under the terms of that license.
* If you distribute binaries on a network server, you have to distribute the source on a network server as well. That is, if you are offering binaries for download, you have to offer the source for download as well, not simply offer to send the source to someone requesting it.
* Source patches or binary patches are not permissible ways to distribute the source. You honor the license by distributing the complete source or simple means to retrieve it (e.g. via a version control system)
-
No precise measure, but it's used A LOT for sure !
Of course, I know.
Inlining is always much better than your MuRedox in this case !
My routines included skip some of your code : no time lost...
Anyway, was very easy to do, maybe one hour of work...
you should update libnix or create a 68060-pure libnix instead of patching existing binaries. improving gcc to create more optimized 68060 code would be a good idea too.
@novacoder:
you should avoid getting rid of perfectly working rtg code. If it's an aga only game you could kill the os. If you don't kill the os there's no reason to strip rtg code. you don't need to release various versions for 030, 040, 060... You can compile each c2p and optimized part and choose it at run time. take a look at adoom, it's a good example
-
So, since you are sharing the binaries, will you share the source and the license terms as well? Otherwise I think that this thread should be deleted on the grounds that it is a blatant copyright infringement.
-
Otherwise I think that this thread should be deleted on the grounds that it is a blatant copyright infringement.
Ha. I was wondering how long it would take the bickering to start! :angry:
And we wonder why we have so few developers left! :lol:
-
And we wonder why we have so few developers left! :lol:
Yes, it's no wonder given how readily people will break licensing agreements and infringe on their intellectual property. But don't you dare linking to an ADF of some cracked 25 year old software!
-
If Cosmo uploads exe and sources to aminet, updates readme with original license terms. Then situation is better than Dante's release many yaers ago, as there wasn't license terms in readme or any other document in that lha archive.
-
Just tried it and got a problem, it asks this :
Using Setup file: 'DUKE3D.CFG'
STUB: CONTROL_ClearAssignments (CONTROL_ClearAssignments, Game/control.c:180)
Missing external con file(s).
COPY INTERNAL DEFAULTS TO DIRECTORY(Y/n)?
It locks duke, so I can't anser question.
What I did. I extracted lha archive to duke's game dir. It works (still do) with duke 0.3 version. Choosed "over write all", when asked. Started stteings seditor choosed correct audio / video modes,etc.
Tested with two 68k amigas wich are in my signature, bot have same problem.
-
Just tried it and got a problem, it asks this :
Using Setup file: 'DUKE3D.CFG'
STUB: CONTROL_ClearAssignments (CONTROL_ClearAssignments, Game/control.c:180)
Missing external con file(s).
COPY INTERNAL DEFAULTS TO DIRECTORY(Y/n)?
It locks duke, so I can't anser question.
What I did. I extracted lha archive to duke's game dir. It works (still do) with duke 0.3 version. Choosed "over write all", when asked. Started stteings seditor choosed correct audio / video modes,etc.
Tested with two 68k amigas wich are in my signature, bot have same problem.
Yes, I have this issue from time to time here...
The v0.5 is coming, theorically faster using an Fpu SMult64 routine...
I recompiled Duke without some gcc options, hope this bug is going away now...
-
@Cosmos:
The archive you uploaded to Aminet does not give any indication that Dante is not the guy releasing it. He's listed as author and uploader, his mail address is given as a target for bug reports... Actually, you're not mentioned anywhere in the archive.
Plus there is no source release, no offer to hand over sources, the GPL's not even mentioned (let alone quoted)...
Please upload a version of the release fixing these problems.
-
I'm actually testing this new 0.5 version :
- one mul64 removed into _rand
- few render routines optimization, nothing serious
- integer SMul64 replaced with Fpu SMul64, a bit faster
- removed some (buggy ?) gcc options
==> http://www.68kforever.com/forums/showthread.php?1-New-version-is-coming&p=202&viewfull=1#post202
or here : http://warpclassic68k.blogspot.fr/p/blog-page.html
:)
-
I'm actually testing this new 0.5 version
I see that there is still no source available, and no GPL license information included. It's simple. Include the original GNU.TXT distributed with the official Duke Nukem 3D source code release in the binary package, and make the source code that you are building from available. It could be on the same download page.
You have included a different license, which I guess is applicable to the original distribution of Duke Nukem 3D, but that license doesn't govern the source code or software based on it. If it was applicable to any of your work, your work would have breached the license since it maintains exclusive rights over the program.
I would love to try this if I had a faster Amiga btw. I don't say any of this to detract from the amazing work you are doing.
-
I see that there is still no source available, and no GPL license information included. It's simple. Include the original GNU.TXT distributed with the official Duke Nukem 3D source code release in the binary package, and make the source code that you are building from available. It could be on the same download page.
You have included a different license, which I guess is applicable to the original distribution of Duke Nukem 3D, but that license doesn't govern the source code or software based on it. If it was applicable to any of your work, your work would have breached the license since it maintains exclusive rights over the program.
I would love to try this if I had a faster Amiga btw. I don't say any of this to detract from the amazing work you are doing.
Why these posts ?
When NovaCoder released AmiQuake2 and AmiDuke, have you asked ?
Why me ?
Leave me alone, please...
-
Because you are breaking the law by disrespecting the license terms of the software yours is built on. If NovaCoder did the same, shame on him too, but I was not aware of that. It's not a very hard thing to comply with.
-
I am sure the original developers are awake last nights about this port, Cosmos, thank you and keep up the good work.
-
Where do these fake lawyers keep coming from ?
Good job Cosmos ! Keep it up, we appreciate your effort.
-
I am sure the original developers are awake last nights about this port, Cosmos, thank you and keep up the good work.
Well it's a matter of principle. We all know how GPL works, otherwise he wouldn't even had the opportunity to tweak with the code, we wouldn't have the games and that would be that. It's not that people doesn't appreciate Cosmo's work, far from it, it's that they also appreciate the original gift from the games owners to the community.
-
OK nice work. It works now bot of my A1200 amigas.
It is playable with 040/AGA 320x100. Very fast with 060/RTG 320x240
Some small problems.
Priorities needs to be adjusted, trying 320x240 with 040/AGA is virtually impossible, as it doesn't wait for keyboard. Same with 060/RTG 640x400.
With my AGA, it doesn't disable mouse pointer and thats why using mouse is impossible.
After some minits playing it hangs, happened two times. Same time there is a "sound effect".
-
OK nice work. It works now bot of my A1200 amigas.
It is playable with 040/AGA 320x100. Very fast with 060/RTG 320x240
Some small problems.
Priorities needs to be adjusted, trying 320x240 with 040/AGA is virtually impossible, as it doesn't wait for keyboard. Same with 060/RTG 640x400.
With my AGA, it doesn't disable mouse pointer and thats why using mouse is impossible.
After some minits playing it hangs, happened two times. Same time there is a "sound effect".
First : this new version is only for the 060 !
For the mouse pointer, I have no idea...
I never had your sound issues here. I use AHI version 6.7, and you ?
-
Why these posts ?
When NovaCoder released AmiQuake2 and AmiDuke, have you asked ?
Why me ?
Leave me alone, please...
I'm actually with Cosmos on this. Who gives a f**k if someone releases a FREE patch to a very old PC game without providing the patch source code, who is actually getting hurt by this action? The original game developers who have probably died of old age by now? The copyright holder? The Amiga community?
I really don't get what all the fuss is about?
Some people obviously prefer to complain than to step up and do something productive themselves.
-
I really don't get what all the fuss is about?
The law perhaps? That said, screw those GPL software Nazis.
-
I'm actually with Cosmos on this. Who gives a f**k if someone releases a FREE patch to a very old PC game without providing the patch source code, who is actually getting hurt by this action? The original game developers who have probably died of old age by now? The copyright holder? The Amiga community?
I really don't get what all the fuss is about?
Some people obviously prefer to complain than to step up and do something productive themselves.
No fight between us : that's our ennemis want...
To be clear : I have only added some asm 060 Mul64 parts into the source, nothing more since I'm a super beginner in C, I cannot do more, sorry...
I'm looking for some good C/C++ coders to finally fix the -mreg-parm gcc option : compiled sources will be faster with that for sure !
:)
-
No fight between us : that's our ennemis want...
I don't think anyone here wants the two of you to start fighting, Cosmos. People are just complaining about license issues, that's all. I don't care about GPL, but if the source code you used is licensed under GPL and you didn't make the source code available, then people will, of course, complain.
-
No fight between us : that's our ennemis want...
Your enemies? There's no need to try to make me look like an antagonist for pointing out these issues.
To be clear : I have only added some asm 060 Mul64 parts into the source, nothing more since I'm a super beginner in C, I cannot do more, sorry...
You were able to simply add those to the source because the source code of the port was made available to you by Dante. Dante was able to port it to the Amiga because the original source was made available to him by 3D Realms & Ken Silverman. The point of GPL is that if you'd actually comply with it, someone else could just as easily improve on your efforts.
If anyone else in this chain had the same attitude to the license as you do, you wouldn't have been able to modify and improve on the source code.
Who gives a f**k if someone releases a FREE patch to a very old PC game without providing the patch source code, who is actually getting hurt by this action?
If I walk into your house and just stand there without doing anything, who is actually getting hurt by it? Probably no one (maybe me, if you found out), but since I respect your property and I respect the law (besides having no personal interest in doing so) I won't do that anyway.
You can also look at it like this: Who would have been "hurt" if Dante hadn't released his source? Certainly, changing a few lines of code in his source to produce a faster Amiga port wouldn't have been possible. Who would have been hurt if 3D Realms didn't release the source in 2003? An Amiga port would have been a massive undertaking.
What GPL does is set up a definition of "FREE" that is more permissive than exclusive copyright but with the caveat that derivative works also need to be "free" under the same conditions. Apart from that it permits you to do basically anything. If you don't agree with that definition of "free", you don't have to use or derive your software from GPL software. It's simple to opt out, but it's also very simple to comply by including the license information and dumping the source you built your binaries from somewhere that people can reach it. I equally don't understand what the fuss is about.
Some people obviously prefer to complain than to step up and do something productive themselves.
Say whatever makes you feel better.
-
1) People are so bored of their life that they complain wherever they can.
2) They think that by giving their opinion they exist.
3) They like arguing for the sake of it.
4) They think that you're wrong and that they're right.
Kamelito
PS not sure where I'm with this post :)
-
Just another thread hacked by lawyers wannabees.
-
If I walk into your house and just stand there without doing anything, who is actually getting hurt by it? Probably no one (maybe me, if you found out)
You forgot the part about "the original authors are probably dead". So in this case, if you walk into a dead guy's house, you're not too likely to get hurt. :lol:
-
So in this case, if you walk into a dead guy's house, you're not too likely to get hurt. :lol:
What if you trip over the dead guy?
-
I'm actually with Cosmos on this. Who gives a f**k if someone releases a FREE patch to a very old PC game without providing the patch source code
The Aminet administration "gives a f**k". There are people out there who care about that sort of thing and don't hesitate to complain about it. The least Aminet can do to protect the individuals providing the mirrors from being harrased by copyright owners is to make sure uploaders respect other people's licenses.
I really don't get what all the fuss is about?
Cosmos is known for pissing on other people's licenses and for totally ignoring Aminet's upload rules - there's a history there, you know... What do you expect me to do?
who is actually getting hurt by this action?
Someone gave away the source code to his legendary game and lets you do whatever you want with it. That's kind of nice, isn't it? And all he asks in return is that you make your sources available along with it. I don't think that's asking too much.
-
That said, screw those GPL software Nazis.
How mature of you.
Think about it like that: Having more software released under the GPL (or any other free license) benefits users of niche computer systems - in other words: it's a good thing, especially for us. If we want more people to release their intellectual property under a free license, we need to make sure they feel like they can trust said license.
If more people behave like Cosmos, less people will release stuff under a free license.
-
Cosmos is known for pissing on other people's licenses and for totally ignoring Aminet's upload rules - there's a history there, you know... What do you expect me to do?
WTF ?
They block Classic with licenses since MANY YEARS (watch actually P96 for example...), so with my disassembling, I mock them...
You play with the opposite and return the situation, I don't like that, really...
The Classic are now near dead because of these big blockers (Kickstart, CyberGraphX, Workbench, hardware gerber files, .jed files...)
-
@cgutjahr
Godwin's law
-
so with my disassembling, I mock them...
I don't care what you do in private. if you upload to Aminet, you respect Aminet's upload rules - period.
You've been told that twice in the past - the second time in no uncertain terms. I asked politely a third time in this thread - and your entire upload is basically another big "f**k you". And as if that wasn't enough fun already, I now face people yelling "GPL nazi" and I'm getting recommendations to do something productive instead.
Do not bother uploading to Aminet again.
-
The Aminet administration "gives a f**k".
Cool. BTW how many complains are you getting from subjects outside Amiga so-called-community about copyright infringements?
-
How mature of you.
I admit that Nazis is harsh.
Think about it like that: Having more software released under the GPL (or any other free license) benefits users of niche computer systems - in other words: it's a good thing, especially for us. If we want more people to release their intellectual property under a free license, we need to make sure they feel like they can trust said license.
GPL sucks because it claims freedom while not giving true freedom. Some people may not want to make their software open source, even when it's based on open source software. GPL is restrictive.
If more people behave like Cosmos, less people will release stuff under a free license.
Well, yes. While GPL sucks, you should still comply with it.
-
I'm sure FSF France would not mind educating Cosmos on GPL, especially since he is now an online shop too.
-
I don't care what you do in private. if you upload to Aminet, you respect Aminet's upload rules - period.
You've been told that twice in the past - the second time in no uncertain terms. I asked politely a third time in this thread - and your entire upload is basically another big "f**k you". And as if that wasn't enough fun already, I now face people yelling "GPL nazi" and I'm getting recommendations to do something productive instead.
Do not bother uploading to Aminet again.
I uploaded on Aminet because two guys on amigaworld.net asked me...
You are on the big blockers side : it's your choice !
-
You are on the big blockers side : it's your choice !
Just comply with the stupid license. Is it such a big deal? Would opening up the source compromise expensive company secrets? Probably not, right?
-
The "enemy" is always "Big" something.
-
You are on the big blockers side : it's your choice !
christoph is maintaining the most complete software pool for amigas available online, which he has to ensure of its legality and legitimity not to be compromised and questioned, otherwise it could even be taken down as a whole. its his responsibility and he tries to do his job best, as service he is not rewarded for, for what i know. your package is one of many, even if it is particularly important, you need to accept and comply to the terms necessary.
-
Here a new version of this great game :
- four mul64 turned to mul32 into _slopevlin
- a lot of mouse & keyboard routines now in fast asm
- some unused code removed
- R_WritePixelArray8 call replaced by BWCP_WritePixelArray8 from BlazeWCP (Rick Pratt) for AGA screen
BWCP_WritePixelArray8 is theorically faster
Enjoy !
==> http://warpclassic68k.blogspot.fr/p/blog-page.html
:)