Windows/DirectX versions
VBBRI would like to know (for no apparent reason) which versions of DirectX come with each version of Windows. That's what I think... - Win95: DirectX 5 - Win98: DirectX 7 - Win2K: DirectX 8 - WinXP: DirectX 9 Is this right? Another thing: I suppose all (or 99.9%) of the PCs nowadays have DX7 installed?
Scorpion_Bloodif ur DX is 8 or 9 then it have DX7 :) but yes most of the computer nowdays have DX7, i didnt know that DX9 was in XP :p vc é de brasil? legal :p
Lachlan87I believe my version of XP only had DX 8 to start with, but I can't remember for sure.
VBBRI also don't know for sure if it's really 9.0 or 8.1 that comes with XP.
quote:
vc é de brasil? legal :p
e so agora vc viu isso? :p ja tinha posto faz algum tempo... (now you US'rs must think... what does all that $#%$& mean? heh)
Eric ColemanWindows 95 - none Windows 98 - possibly 3 Windows 98 SE - possibly 5 Windows 2000 - 7 Windows XP - 8 Windows ME - don't know. DirectX 3 was the first version, and there was no DirectX 4.
CrysstaafurI think if I remember right, Win95revB(2nd major patch) came with DX3 and USB support. Original 98, not sure, probably DX5. 98SE, is either DX5 or DX6. ME also defaults to DX6 I believe. Win2k(Pro)(at least the version I have) defaults with DX6. WinXP(Pro) I can verify that it starts with DX8.1 I don't know about other XP revisions..
Sr. GuapoXP SP1 came with DX 8.1, and I assume that SP2 probaly has DX9 on it, though I have no idea which revision.
ZarnethXP SP2 comes with DX9.0c I know this 'cause the latest DX9 SDK for VB I could find was 9.0b, so I had to find a directX uninstaller. Why .net can't be as simple as vb6 and not even need the sdk I don't know. But I'm using Revolution3d now anyway so it doesnt' matter. ;)
Scorpion_Bloodnone OS came with DX7?
Eric ColemanMy version of windows 2000 (pro) shipped with Directx 7. Also, Windows 2000 Adv Server has dx7 as well.
VBBRI think that's already good. If I was worried with compatibility with crappy PCs, should I go with DX7 then? (I think the really paranoid thing would be to use GDI, but would that do any good compared to DX7, regarding speed and compatibility?) (Note: No, this is not 3D, not even a game. I'm going to create a 2D app. Anyway I think DX7(DD, Hybrid or whatever) would be great for fancy effects and also for DShow integration?)
ZarnethWell if anyone doesn't have a copy of DirectX7 you can pretty much rely on the fact that they'll have a game lying round with at least DX7 on it. Though if it's for use in a business environment that may not apply.
Eric ColemanIf it's not a game, and you don't need to update the entire screen 60 times per second, then I would use GDI. You won't be able to use DirectShow with VB and Directx7, MS left that out of the dx7 type library. You can use DirectShow in dx 8 if you need it. And if you're going to use a "hybrid" engine, then that will require a 3D card, so you might as well use Directx 8.
VBBRI guess I'm going for DX8 then... What are the minimum requirements for D3D8?
ZarnethI don't know what OS it requires. But for hardware, as long as you dont' force and fancy pixel shaders and bump mapping I"m pretty sure any ancient crappy old 3d card that has relativly up to date drivers will work.
Eric ColemanDX 8 works on windows 95 and up, DX 8.1 works on windows 98 and up, it won't work on 95.
PeterIf you need the graphics fidelity I'd go with DirectX 8 or so. It probably depends on the audience, a lot of business type apps use 3D graphics via DirectX or OpenGL. Like CAD/CAM applications, 3d modelling packages etc (I guess thats not really business software but I couldnt find a better word).