Hey everybody, Loki Entertainment will be showing off their port of the
new game “Civilization: Call To Power” at the LinuxWorld Expo in San Jose,
tomorrow and Wednesday. If you’re going to be there, look us up! 
(We’re using SDL for the Linux port of CivCTP)
See ya there!
-Sam Lantinga (slouken at devolution.com)
Hi everyone
Sam Lantinga wrote:
Hey everybody, Loki Entertainment will be showing off their port of the
new game “Civilization: Call To Power” at the LinuxWorld Expo in San Jose,
tomorrow and Wednesday. If you’re going to be there, look us up!(We’re using SDL for the Linux port of CivCTP)
Cool they are porting CivCTP ! I'll bought that one for sure :)
By the way could you tell me why the test program ( SDL/test/testvidinfo)
tell me this :
A window manager is available
Current display: 16 bits-per-pixel
Red Mask = 0x0000f800
Green Mask = 0x000007e0
Blue Mask = 0x0000001f
Video hardware has 4095K of video memory
video memory protecting
that’s the video memory protecting that interest me since it look like even
with the SDL_HWSURFACE flag I can’t used my Hardware memory …
I got an ATI 3d Rage 2 card with 4 mb
Thanks and cya
ClusterCool they are porting CivCTP ! I'll bought that one for sure :)
By the way could you tell me why the test program ( SDL/test/testvidinfo)tell me this :
A window manager is available Current display: 16 bits-per-pixel Red Mask = 0x0000f800 Green Mask = 0x000007e0 Blue Mask = 0x0000001f Video hardware has 4095K of video memory video memory protecting
that’s the video memory protecting that interest me since it look like even
with the SDL_HWSURFACE flag I can’t used my Hardware memory …
That message comes directly from the XFree86 libraries. It’s just
chatter that probably shouldn’t be there.
-Sam Lantinga (slouken at devolution.com)
A window manager is available Current display: 16 bits-per-pixel Red Mask = 0x0000f800 Green Mask = 0x000007e0 Blue Mask = 0x0000001f Video hardware has 4095K of video memory video memory protectingthat’s the video memory protecting that interest me since it look like even
with the SDL_HWSURFACE flag I can’t used my Hardware memory …That message comes directly from the XFree86 libraries. It’s just
chatter that probably shouldn’t be there.
if ( (screen_->flags & SDL_HWSURFACE) == SDL_HWSURFACE) {
cerr << "\tScreen is in video memory" << endl;
} else {
cerr << "\tScreen is in system memory" << endl;
}
And I get the "Screen is in system memory" message so I'm not quite sure that
I’m using Hardware memory now Any idea ?
ClusterAnd I get the "Screen is in system memory" message so I'm not quite sure thatI’m using Hardware memory now
You aren’t using hardware memory. That’s just the X11 libraries being cute.
You can ignore the message.
-Sam Lantinga (slouken at devolution.com)
Hi there…
Jeremie Plante wrote:
Hi everyone
Sam Lantinga wrote:
Hey everybody, Loki Entertainment will be showing off their port of the
new game “Civilization: Call To Power” at the LinuxWorld Expo in San Jose,
tomorrow and Wednesday. If you’re going to be there, look us up!(We’re using SDL for the Linux port of CivCTP)
Cool they are porting CivCTP ! I'll bought that one for sure :) By the way could you tell me why the test program ( SDL/test/testvidinfo)tell me this :
A window manager is available Current display: 16 bits-per-pixel Red Mask = 0x0000f800 Green Mask = 0x000007e0 Blue Mask = 0x0000001f Video hardware has 4095K of video memory video memory protectingthat’s the video memory protecting that interest me since it look like even
with the SDL_HWSURFACE flag I can’t used my Hardware memory …
No no no no.
The ‘video memory protecting’ is actually the X server saying that. It says that
every time you enter DGA mode. There’s no way to turn it off or shut it up (bar
commenting it out in the X server source). So you see it. It’s not the test
program saying that. And don’t worry, it’s basically meaningless…
Peter>
I got an ATI 3d Rage 2 card with 4 mb Thanks and cya Cluster
By the way could you tell me why the test program ( SDL/test/testvidinfo)tell me this :
A window manager is available Current display: 16 bits-per-pixel Red Mask = 0x0000f800 Green Mask = 0x000007e0 Blue Mask = 0x0000001f Video hardware has 4095K of video memory video memory protectingthat’s the video memory protecting that interest me since it look like even
with the SDL_HWSURFACE flag I can’t used my Hardware memory …No no no no.
The ‘video memory protecting’ is actually the X server saying that. It says that
every time you enter DGA mode. There’s no way to turn it off or shut it up (bar
commenting it out in the X server source). So you see it. It’s not the test
program saying that. And don’t worry, it’s basically meaningless…
Peter
Ok thanks for the explanation :) But I think I haven't explain myself pretty
well (bad english sorry) …
My real question is about SDL_HWSURFACE .. I've just runned some more test and
it seam that I’m really not able to Set any Surface in Hardware memory !
Since I had a new graphic card Ati 3d rage pro 2 I'm really confuse ... Could
it be the hardware that doesn’t let me access Hardware mem ?
Cause I know the speed diffrence between Hw and Sw mem and it seam that I'm
also ain’t able to do Double Buffering .
Could my ATI card be the problem ?
Thanks
ClusterMy real question is about SDL_HWSURFACE .. I've just runned some more test andit seam that I’m really not able to Set any Surface in Hardware memory !
Since I had a new graphic card Ati 3d rage pro 2 I'm really confuse ... Couldit be the hardware that doesn’t let me access Hardware mem ?
Cause I know the speed diffrence between Hw and Sw mem and it seam that I'malso ain’t able to do Double Buffering .
Could my ATI card be the problem ?
No, it’s that you are running under X11. If you really want to access the
hardware memory (and I don’t recommend it) then you can run the program as
root, and set the (SDL_FULLSCREEN|SDL_HWSURFACE) flags in SDL_SetVideoMode()
Generally the speed will be faster when you don’t write directly to the
video memory, but you can do your own tests.
-Sam Lantinga (slouken at devolution.com)
Could my ATI card be the problem ?No, it’s that you are running under X11. If you really want to access the
hardware memory (and I don’t recommend it) then you can run the program as
root, and set the (SDL_FULLSCREEN|SDL_HWSURFACE) flags in SDL_SetVideoMode()Generally the speed will be faster when you don’t write directly to the
video memory, but you can do your own tests.-Sam Lantinga (slouken at devolution.com)
I'm confuse ... You mean that Software mem is faster than hardware ???
I'm sorry to ask all these question it's just that it's my second try to accelerate
my Client and I do know that speedy refresh is hard to achieve in linux so I want to be
sure
Thanks
ClusterI'm confuse ... You mean that Software mem is faster than hardware ???
I'm sorry to ask all these question it's just that it's my second try to acceleratemy Client and I do know that speedy refresh is hard to achieve in linux so I want to be
sure
Yes, you can touch software mem faster than you can touch hardware mem.
The memory bus is much faster than the system bus.
The time hardware memory is really useful is when you have an image that
you don’t want to change often, and you want to blit it repeatedly to the
screen. In that case, it’s very helpful to have the image in hardware and
then blitting it often becomes a fast command to the video hardware.
However, if you are assembling dynamic screen contents yourself, you are
much better off doing it in RAM and then doing a fast copy to the video
display.
-Sam Lantinga (slouken at devolution.com)
I have a program that uses a rendered scrolling background with sprites
blitted onto it. Does this seem like the fastest system:
1. Render background in software memory;
(This involves blitting the background from the last frame onto
itself with an offset for scrolling)
2. Blit to video surface.
3. Blit sprites also stored in video memory.
4. Flip buffer.
emblem
I have a program that uses a rendered scrolling background with sprites
blitted onto it. Does this seem like the fastest system:
1. Render background in software memory; (This involves blitting the background from the last frame ontoitself with an offset for scrolling)
2. Blit to video surface.
3. Blit sprites also stored in video memory.
4. Flip buffer.
It does to me. Anyone else?
-Sam Lantinga (slouken at devolution.com)
I’ll be working at the Loki booth at the LinuxWorld Expo in San Jose
next week: http://www.linuxworldexpo.com/
I hope I’ll see some of you there.
See ya,
-Sam Lantinga, Lead Programmer, Loki Entertainment Software