I am new to the mailing list, so if this topic was discussed already I’m
sorry.
I’ve just installed windows XP. Previously I used win2k, where SDL run
smoothly. Now, with XP, programs that use SDL hardly function (very very
slow). I’ve made sure my gfx card is recognized by windows, and even tried
some non-sdl direcx games (they all run perfectly). So it seems there is some
problem with the SDL library on windows XP…
Any more information or solution ideas are welcome.
Does it happen with “pure” 2D games as well as OpenGL based games? If
not, your OpenGL driver might be broken on nonexistent, so that you end
up falling back on some software implementation…
//David Olofson — Programmer, Reologica Instruments AB
.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |-------------------------------------> http://olofson.net -'On Thursday 27 September 2001 17:50, Elik Eizenberg wrote:
I am new to the mailing list, so if this topic was discussed already
I’m sorry.I’ve just installed windows XP. Previously I used win2k, where SDL run
smoothly. Now, with XP, programs that use SDL hardly function (very
very slow). I’ve made sure my gfx card is recognized by windows, and
even tried some non-sdl direcx games (they all run perfectly). So it
seems there is some problem with the SDL library on windows XP…
Hi Elik,
I also had a friend who was testing my MD2 Model Viewer under XP and
he complained that it ran extremely slowly as well.
Could it be that Microsoft have made their OpenGL implementation run
slower under XP to encourage people to use DirectX and Direct3D? I may
be grasping at straws here but they’ve done this sort of thing before.
Just a thought.
Dominique Louis
http://www.DelphiGamer.com := for all your Delphi/Kylix game development
needs;
Elik Eizenberg wrote:> I am new to the mailing list, so if this topic was discussed already I’m
sorry.
I’ve just installed windows XP. Previously I used win2k, where SDL run
smoothly. Now, with XP, programs that use SDL hardly function (very very
slow). I’ve made sure my gfx card is recognized by windows, and even tried
some non-sdl direcx games (they all run perfectly). So it seems there is some
problem with the SDL library on windows XP…Any more information or solution ideas are welcome.
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
Hi,
Thanks for your replies.
It is possible that microsoft did such a thing. I will now check if glut
applications (no SDL) work slowly too… it that’s the case, then it must be
something in the openGL implementation for windows XP.
Hi Elik,
I also had a friend who was testing my MD2 Model Viewer under XP and
he complained that it ran extremely slowly as well.Could it be that Microsoft have made their OpenGL implementation run
slower under XP to encourage people to use DirectX and Direct3D? I may
be grasping at straws here but they’ve done this sort of thing before.Just a thought.
Dominique Louis
http://www.DelphiGamer.com := for all your Delphi/Kylix game development
needs;Elik Eizenberg wrote:
I am new to the mailing list, so if this topic was discussed already I’m
sorry.I’ve just installed windows XP. Previously I used win2k, where SDL run
smoothly. Now, with XP, programs that use SDL hardly function (very very
slow). I’ve made sure my gfx card is recognized by windows, and even tried
some non-sdl direcx games (they all run perfectly). So it seems there is
someproblem with the SDL library on windows XP…
Any more information or solution ideas are welcome.
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
I’m almost forgetting how evil they can be… 
OTOH, if it’s that slow, I’m afraid it’s more likely to scare users
away from XP than it is to force Direct3D upon game developers. Some very
Big Names in the industry refuse to use Direct3D, and won’t drop OpenGL
without a fight. (Then again, Microsoft is incredibly powerful when it
comes to countering valid technical and political arguments with FUD…)
//David Olofson — Programmer, Reologica Instruments AB
.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |-------------------------------------> http://olofson.net -'On Thursday 27 September 2001 19:07, Dominique Louis wrote:
Hi Elik,
I also had a friend who was testing my MD2 Model Viewer under XP and
he complained that it ran extremely slowly as well.Could it be that Microsoft have made their OpenGL implementation run
slower under XP to encourage people to use DirectX and Direct3D? I may
be grasping at straws here but they’ve done this sort of thing before.
Could it be that Microsoft have made their OpenGL implementation run
slower under XP to encourage people to use DirectX and Direct3D? I may
be grasping at straws here but they’ve done this sort of thing before.
Oh no. Alert Slashdot immediately.
Perhaps we should try debugging/profiling SDL and verifying that other
OpenGL programs are slower and that these XP OpenGL drivers aren’t just
buggy. I know, I know, Microsoft’s the devil and everything.
–ryan.
Could it be that Microsoft have made their OpenGL implementation run
slower under XP to encourage people to use DirectX and Direct3D? I may
be grasping at straws here but they’ve done this sort of thing before.Oh no. Alert Slashdot immediately.
Perhaps we should try debugging/profiling SDL and verifying that other
OpenGL programs are slower and that these XP OpenGL drivers aren’t just
buggy. I know, I know, Microsoft’s the devil and everything.
I had some game-related difficulties with XP too, namely a) lag, b) lag
and c) more lag. The game in question was a DirectX game, which ran
smoothly in 98. Solution: Set the application to compatibility mode
for Windows 98/ME. This resulted in the same smooth gameplay. I have
currently no OpenGL applications to test this setting with, so someone
else has to do it. Technically, I don’t know what that compatibility
setting does but if it helps, well, I don’t know what that means either.
Also, WinXP is still like a little baby that must be taught and raised
carefully. You can’t exactly say that the current state of the OS will be
the final state, can you? New drivers will emerge and the support for
OpenGL will improve, if it really is buggy. Time will heal. That’s my
opinion. We just have to wait until WinXP gets officially released + some
more time before we can say anything ^.^
Petri LatvalaOn Thu, 27 Sep 2001, Ryan C. Gordon wrote:
Could it be that Microsoft have made their OpenGL implementation run
slower under XP to encourage people to use DirectX and Direct3D? I may
be grasping at straws here but they’ve done this sort of thing before.
I don’t think so, I can run serious sam (opengl based game) under xp
without any preformence issues.
//TimOn Thu, 27 Sep 2001, Dominique Louis wrote:
You HAVE TO update your video drivers immediately after installing XP.
Windows XP, even 2000 ships with video drivers that are “basic only” no
OpenGL, crippled if non-existant Direct3D support. The same goes for Audio
drivers, no DS3D or,OpenAL. Simply put, if you never updated your video
drivers, you are running in super-crippled mode.
The obvious reason is that MS doesn’t want people to use OpenGL, thus the
drivers that come with Win2K/XP do not come with OpenGL. However if you
think about it, Detonator and ATI driver “packs” are in the excess of 10MB
range typically, now at 10MB per family of video card, you easily run out of
disc space on the CD-ROM for other drivers.
This is similar to buying a new computer, by the time the new computer is
built, tested, shipped and bought the drivers are out of date. The first
thing you should do when you install a new OS or buy a new computer is
update/replace ALL the drivers.
I usually go in this order:
Ethernet Card (1st if internet isn’t working)
Motherboard/AGP/IDE
Video Card
Sound Card
Video Capture Card
SCSI Card
DVD-ROM/CD-ROM/CD-Burner/HardDrive
Scanner/Printer/Anything else USB
Of which the two priorities are getting the video working(max out refresh
rate/color depth/resolution) and getting the internet to work to download
the drivers. Usually Windows comes with a sufficient network card driver, so
I do video first, however it usually requires the AGP/Motherboard/IDE driver
first.
The worst graphics systems (Intel Onboard, Some Laptop chipsets) usually
fare no different when the newer drivers are installed. The Intel onboard
graphics is really nasty for this, the performance doesn’t increase, only
adds OpenGL and supports the latest version of DirectX. ATI and nVidia 's
performance increase quite a bit when they use proper drivers.
Anyways, OpenGL support is only provided by the graphics card vendor, not
Microsoft.> ----- Original Message -----
From: sdl-admin@libsdl.org [mailto:sdl-admin at libsdl.org]On Behalf Of
Elik Eizenberg
Sent: September 27, 2001 8:50 AM
To: sdl at libsdl.org
Subject: [SDL] SDL under WinXPI am new to the mailing list, so if this topic was discussed already I’m
sorry.I’ve just installed windows XP. Previously I used win2k, where SDL run
smoothly. Now, with XP, programs that use SDL hardly function (very very
slow). I’ve made sure my gfx card is recognized by windows, and even tried
some non-sdl direcx games (they all run perfectly). So it seems there is
some
problem with the SDL library on windows XP…Any more information or solution ideas are welcome.
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
You HAVE TO update your video drivers immediately after installing XP.
Windows XP, even 2000 ships with video drivers that are “basic only” no
OpenGL, crippled if non-existant Direct3D support. The same goes for AudioHm, I’m sure the win2k installer installs drivers for my card (geforce 1).
In fact, with OpenGL support. I remember this because the detanator
drivers used to freeze my system, so I had to fall back to the default
driver for stability.The obvious reason is that MS doesn’t want people to use OpenGL, thus the
drivers that come with Win2K/XP do not come with OpenGL. However if youAgain, not true (see above). Although, of course, newer cards (that didn’t
exist yet when the win2k installation was built) can’t have more than basic
support. But then, the windows update service gives you the choice to
install newer drivers, including openGL support.I’m not sure about XP, but since XP has a consumer oriented version (win2k
didn’t), I suspect it to be ‘end user’ friendly. (In fact, doesn’t the XBox
run a version of XP?), and again, if a full driver isn’t included in the
installer, the windows update service can check for newer drivers. (and
those drivers definitly include OpenGL support)It is true of course that Microsoft wants us to use DirectX instead of
OpenGL, but you have to admit that they try that by making DirectX a
feature-rich, mature API, and not by making it difficult to use OpenGL.
(B.T.W. in case you might wonder, I use OpenGL, because I don’t want to tie
myself to one platform)----- Original Message -----
From: Kisai [mailto:kisai_z@yahoo.com]
I’m not sure about XP, but since XP has a consumer oriented version (win2k
didn’t), I suspect it to be ‘end user’ friendly. (In fact, doesn’t the XBox
run a version of XP?), and again, if a full driver isn’t included in the
installer, the windows update service can check for newer drivers. (and
those drivers definitly include OpenGL support)
Please take this discussion offline - it’s going off-topic.
Thanks.
-Sam Lantinga, Software Engineer, Blizzard Entertainment