home *** CD-ROM | disk | FTP | other *** search
- Path: nntp.teleport.com!sschaem
- From: sschaem@teleport.com (Stephan Schaem)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Amiga programmers in deep shit...
- Date: 10 Jan 1996 13:02:09 GMT
- Organization: Teleport - Portland's Public Access (503) 220-1016
- Message-ID: <4d0dch$cup@maureen.teleport.com>
- References: <4bsgo0$3sg@bagan.srce.hr> <4c76qg$l7b@maureen.teleport.com> <4c8pb6$91p@serpens.rhein.de> <4c9qu8$v0@maureen.teleport.com> <4carpi$7c2@serpens.rhein.de> <4ccpsd$d8f@maureen.teleport.com> <Kevin_Phair.040b@bgi.internet-eireann.ie> <4cjimb$4im@maureen.teleport.com> <Kevin_Phair.040n@bgi.internet-eireann.ie> <4cto7l$t4s@maureen.teleport.com> <4ctuqh$1gj@serpens.rhein.de>
- NNTP-Posting-Host: julie.teleport.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Michael van Elst (mlelstv@serpens.rhein.de) wrote:
- : sschaem@teleport.com (Stephan Schaem) writes:
-
- : > CBM never saw that it was something to worry about for games, they
- : > basicly said it was all ok to write HW level game from day one.
-
- : They basically acknowledged the fact that game producers do not use
- : the system. However, they tried to enforce use of the system for
- : AGA. They failed.
-
- CBM never wrote a library that was designed with game or multimedia
- in mind (Not anything close to the HW capability). and the system
- library where simply not flexible enought.
-
- CBM gave up to easely... if they knew better then the game developer,
- they should have put they knowledge in writting: Basicly go in detail
- on each point why using the HW directly dont give you an edge vs their
- OS solution.
- Personaly I dont think game developer where happy with 3.x to write
- games... But 3.x is not bad for some type of games.
-
- : > then 10% per frame? The amiga multitask, but it doesnt offer time
- : > slicing or guaranty a task will get a certain % of the CPU.
-
- : It offers time slicing and it guarantees that a task gets the CPU
- : when it has the highest priority and is runnable.
-
- Task 1: PRI 127 waitof: render frame
- Task 2: PRI 0 alway: read() data
-
- Task1 alway leave 10-20% of the frame free... I dont want task2 under
- any circonstances to use task 1 'reserved' cpu time.
-
- Would doing the above just work on any HD system?
-
- : > There is no point in talking to you about it, since all you care and want
- : > to hear about is multitasking HD only games.
-
- : Well.. That's 99% of all games... potentially.
-
- The new AT machine will most probably have that ratio... mainly
- because it would be stupid to use floppy when all machine come with
- HD. I cant say about multitasking, but at least it will load from HD
- and return to the system.
-
- AT better set the rules strait from the start this time.. if they want
- software for their machine done right, they better create a quality label
- with good info and guidline.
-
- Stephan
-