Moderators: lp, moondog/.tSCc., Moderator Team
Great fun stuff 
To really harvest the speed of the SuperVidel (or the CTPCI, probably), you should allocate your render buffer in VRAM instead of RAM, because blits between RAM<>VRAM aren't nearly as fast as VRAM<>VRAM. Use ct60_vmalloc()Rajah Lone wrote:Daroou is studying the offscreen part of the VDI and the best way to use RAM and VDI. We have results for TT+NOVA, Falcon+CT6x+CTPCI+Radeon, FireBee, Ararnym. We would be interested on stats for Hades and Falcon+CT6x+SuperVidel. Thanks in advance.
No existing NVDI driver allocates offscreen bitmaps in VRAM, unfortunately. I've disassembled them all. This could potentially change in the future though..Rajah Lone wrote:@shoggoth : Daroou has no CT6x, just a Milan machine and an Aranym setup. vmalloc() is in project, but screen -> screen simulates Offscreen VRAM test. In Offscreen VRAM test, blit is made in screen to screen, therefore in supposed VRAM zone (present or not, depends on the display drivers).
Is vmalloc supported by the SuperVidel driver? I thought it was only for the Radeon, since Didier Méquignon's work is based on this card.
I generally avoided the other CTPCI-stuff, because it doesn't apply very well to the SuperVidel (or Videl for that matter). 
try with NVDI... with SuperVidel without NVDI it get confusedOrion_ wrote:the program doesn't tell me anything, NVDI is not loaded, but it should not be mandatory to have NVDI
Check if the cookie EdDI is present or not (one CPX can list them using XCONTROL.ACC or COPS.ACC).Orion_ wrote:This is what I get on my Firebee (FireTos or mint) running the program from A: (sdcard)
it starts with a little black screen in the upper left corner (during "chargement image...")
you repeatedly told me to make the most compatible VDI program for My games, now you tell me I need to install this and that so Your program can work ?Rajah Lone wrote:Check if the cookie EdDI is present or not (one CPX can list them using XCONTROL.ACC or COPS.ACC).Orion_ wrote:This is what I get on my Firebee (FireTos or mint) running the program from A: (sdcard)
it starts with a little black screen in the upper left corner (during "chargement image...")
If not present, and using none standard Atari screenmode, then you run any program at your own risk. Here it seems screen address could not be inquired or bitplane structure determined.
If I remember correctly, ENHANCER.PRG should install the EdDI cookie.
You should not be stubborn about not installing NVDI. It's a must have for anyone who use GEM every day.
I advised you to make some efforts on AES support (windows managment). There are some missing GEM-AES events that ought to be handled, if not, some users may encounter redraw problems.Orion_ wrote:you repeatedly told me to make the most compatible VDI program for My games,
For the record, not my program, but Daroou's. I post here in his name because English language is not his forte.Orion_ wrote:now you tell me I need to install this and that so Your program can work ?
Atari standard screenmode = take all Atari machines, basic and out of the box, without any upgrade. So on Falcon, from 320*200 duochrome to TrueColor 15/16 bits. Size does not matter, but Falcon TC modes are not large.Orion_ wrote:What do you mean by "non standard atari screenmode" ?
ENHANCER.PRG only knows about Atari-compatible screen resolutions, and IIRC it only works on the standard TOS VDI (it's a hack).Rajah Lone wrote:Check if the cookie EdDI is present or not (one CPX can list them using XCONTROL.ACC or COPS.ACC).Orion_ wrote:This is what I get on my Firebee (FireTos or mint) running the program from A: (sdcard)
it starts with a little black screen in the upper left corner (during "chargement image...")
If not present, and using none standard Atari screenmode, then you run any program at your own risk. Here it seems screen address could not be inquired or bitplane structure determined.
If I remember correctly, ENHANCER.PRG should install the EdDI cookie.
You should not be stubborn about not installing NVDI. It's a must have for anyone who use GEM every day.
I must ask what is ENHANCER.PRG ?shoggoth wrote:ENHANCER.PRG only knows about Atari-compatible screen resolutions, and IIRC it only works on the standard TOS VDI (it's a hack).
ENHANCER.PRG implements offscreen bitmaps on the standard VDI. It also provides information about the current pixel format (i.e. it implements vq_scrninfo()).calimero wrote:I must ask what is ENHANCER.PRG ?shoggoth wrote:ENHANCER.PRG only knows about Atari-compatible screen resolutions, and IIRC it only works on the standard TOS VDI (it's a hack).
..."worshiper of the void"...
I'm not sure what that means but it certainly sounds greatRajah Lone wrote:I'm a FireBee user, not a worshiper of the void.
