Ultimate Amiga
Network Boards => AMOS Factory => Extensions Forum => Topic started by: KevG on November 15, 2009, 05:58:42 PM
-
Hello folks.
Has anyone managed to get the AMCAF extension to work in AMOS 1.3? I have tried but it failed. I think its for AMOS Pro only.
Thanks, Kev G
-
AMCAF is for AmosPro only.
-
Thought so :-[
Thanks anyway.
-
Is there a reason you don't want to use AmosPro? I realize that the downloads area here glitches with 0k downloads sometimes but we do have AmosPro and the compiler downloadable here.
-
I use AMOS1.3 because you can disable multitasking properly which gives you a speed boost.
-
It is probably far to late for you to change, but I am sure there was an extension or something that made AP multi-task properly. I have a feeling it was on aminet.
[EDIT] I found it, http://aminet.net/package/dev/amos/AMOS_Patch
-
I think the Turbo Plus extension also has a few commands that turn off multitasking in AMOS Pro.
-
It is probably far to late for you to change, but I am sure there was an extension or something that made AP multi-task properly. I have a feeling it was on aminet.
[EDIT] I found it, http://aminet.net/package/dev/amos/AMOS_Patch
That enables multitasking. He wants to disable it, Skate.
-
It is probably far to late for you to change, but I am sure there was an extension or something that made AP multi-task properly. I have a feeling it was on aminet.
[EDIT] I found it, http://aminet.net/package/dev/amos/AMOS_Patch
That enables multitasking. He wants to disable it, Skate.
Whoops, once again I fail... ;D
-
Hi folks.
The Turbo Extension command doesn't really turn multi-tasking off in AMOS Pro. I think all it does is change its task priority. It does do it in AMOS1.3 though which is kind of strange but I think this is due to the way that AMOS1.3 was designed.
Thanks for your help chaps but I think I am going to have to figure a way around it.
Kev G.
-
If you're going to disable multitasking, you're also going to slow down the system. Normally the blitter runs asynchronously while the CPU is doing other stuff. Unless you do all of the blitting at the beginning of the game loop you're going to spend a lot of time waiting for the blitter to finish its previous operation.
-
Thats a new one on me ??? I have done lots of demos/games and I have found that you get far better speed results when you disable multi-tasking. The sonic demo that I did was only possible because I disabled multi-tasking and I used a lot of screen copying to create the parallax effects. With multi-tasking enabled it is jerko-vision!
However, I take on board what you have said regarding the blitter and will look into it.
On another note, I am seriously thinking of migrating to AMOS Pro simply because of the extra features and the ability to use the AMCAF extension. Maybe I will gain more speed using the AMCAF extension in AMOS Pro than I would by disabling multi-tasking in AMOS1.3.
Cheers, Kev G.
-
Hello folks.
Has anyone managed to get the AMCAF extension to work in AMOS 1.3? I have tried but it failed. I think its for AMOS Pro only.
Thanks, Kev G
It isn't possible to get AMCAF working with AMOS 1.3 without the aid of Chris Hodges (the author). Even then it requires taking the original source code, turning it upsidedown and removing the extra code which AMOS Pro requires (and makes things alot easier).
Even then the code may require recoding in places and I can't see anyone taking on that mammoth project or Chris giving up the source code (if he even has it still).
Regards,
Lonewolf10
PS. Sorry I have been absent lately. Didn't have the new URL for the forum and only found it by searching for the site on Google. I have changed my bookmark now :)
-
I use AMOS1.3 because you can disable multitasking properly which gives you a speed boost.
Which command do you use to disable multitasking in AMOS-TC 1.3?
-
Hello KevG,
Still on AMOS1.3 or AMOSPro ?
I found this post because I wanted to found a way to disable completely the multitasking too... Maybe for coding arcade games and demos, it's better to use Amos 1.3...
-
I think the real answer to this these is, how to disable multi tasking on Amos pro, or otherwise significantly improve it's speed.
For me, this is the most exciting possibility of the new Amos Pro updates
-
For me too :)
Or a patch to disable multitasking on AmosPro.
BruceUncle, maybe you are reading this ?
-
The only way I know to disable multi-tasking in AMOS Pro is to use Forbid from Exec library(?), and re-enable multi-tasking by using Permit (also from Exec library).
They have improved the speed of some of my AMOS stuff in the past, but there's a chance that AMOS may crash.
AMOS (and AMOS Pro) generate the copper in realtime, which is used for thing like the Rainbow commands, setting up screens, sprites etc.
This all makes it very slow and as AMOS hits the hardware directly (from what I remember) it is not OS friendly, therefore not very multi-tasking off friendly either.
Hopefully bruceuncle is reading this and will confirm what I said.... and correct the bits I may have got wrong ???
-
In ASM it is:
MultiTaskOFF:
Move.l $4,a6
Jsr _LVOForbid(a6)
Rts
;
MultiTaskON:
Move.l $4,a6
Jsr _LVOPermit(a6)
Rts
In AMOS:
MultiTaskOFF:
E=Execall(-132)
MultiTaskON:
E=Execall(-138)
In AmosPro I don't think that it is as efficient that it is in AMOS The Creator, I think it's is disabled at 80%... You can correct me.
In AMOS if you code:
E=Execall(-132)
Repeat
Until Mouse Key=1
There it no way to click the mouse, while it is possible in AmosPro.
If you are coding a Trackmo of something like that, it is useful that multitasking is totally disabled.
-
Two more useful commands also help when placed before hand....
Break Off
Amos Lock
E=Execall(-132)
You also may find that the keyboard is locked out as well and make sure that any disk activity has finished first before using these commands.
Its a small price to pay for the extra speed that you gain.
-
Two more useful commands also help when placed before hand....
Break Off
Amos Lock
Be careful when using these, particularly the first one. All it takes is to forget what you are doing and hit F1 (run program) and you won't be able to save the new bit of code you have written, as you have just disabled the Control+C (or whatever you have set it as) to break out of the program to get back to the editor! I learnt my lesson (several times) the hard way :(