02-05-2007, 09:15 PM
I think that there should be an upgrade for the DirectX because I herd that if you get a better 1 then you can have way better graphics which would be cool. So just wandering also if anyone has DX8+ or sometin

DX8+
|
02-05-2007, 09:15 PM
I think that there should be an upgrade for the DirectX because I herd that if you get a better 1 then you can have way better graphics which would be cool. So just wandering also if anyone has DX8+ or sometin
![]()
02-05-2007, 10:16 PM
Why was my post deleted? All I said was if he wanted to do it for his game, he could. But it's not easy to do.
02-05-2007, 10:45 PM
Erm, yes is it
![]() Quote:Robin:
03-05-2007, 12:33 AM
It actually isn't though. There is alot of changes.
And VB is only supported until DX8, 9+ aren't compatible, or at least said not to be.
03-05-2007, 12:38 AM
Has anyone ever tried to get it working? And if so, what happened?
03-05-2007, 03:27 AM
Yes I did, and it worked fine
just takes some fiddling around
03-05-2007, 12:10 PM
Sorry, I meant DX9. Lol. Forgot to specify. Although I was pretty sure I did. I think I'm going senile at a young age.
03-05-2007, 03:12 PM
I thought you couldn't use dx9 in vb6...
03-05-2007, 03:23 PM
I don't think you can...
But, DX8, if programmed properly can be even more convenient than Direct Draw. After looking around, I was linked to Lucky's VB Game Tutorials, and using the tutorial to init DX8 (Part 1 Part 2), a small piece of code from the tutorial on 2D Game Design in DX8 (Here) and for menu backgrounds (my entire engine is DX8) I used the tutorial on loading large textures onto a surface (Here) and then made a few functions and subroutines, added a few scripted files so you could easily change textures, sizes, sprites etc. without having to edit the game engine (all textures need to be in multiples of 2 (32x32, 64x64, 96x96, 256x256 etc. etc.) so it is hard to hard code (*hint @ pun*) the entire graphics engine) and then a few automated services and it works even better than Direct Draw (Faster (if you have a 3D graphics support ![]() Wow. I do believe I used little to no punctuation there. Ah, shoot me. Quote:Robin:
03-05-2007, 03:55 PM
*Shoots Robin*
You make it sound easy. Lol. Oh well. One of these days I may look into what you just posted, who knows?
03-05-2007, 04:36 PM
Well I found it as easy as what Robin says, I also used Luckys vb Game tutorials
![]()
03-05-2007, 06:19 PM
I personally find Direct3D faster than DirectDraw, too. It may just be since I was more noob using DirectDraw, but you can take the 3d optimizations to a ridiculous level of obfuscation for power. Cards these days just support 3d better than native 2d (the straight copy of one surface to another). Strange how it works that way, though, since you would think copying from one surface to another would be the easiest thing you could possibly do.
03-05-2007, 08:25 PM
Well it be cool if we can get some tuts
![]()
03-05-2007, 09:08 PM
04-05-2007, 05:13 AM
Actually i think you can use DX9 with VB6... i think there was an SDK developed to allow it to be used... but i have been wrong before. I think shan was actually working on a VB6 project using DX9 at one point...
04-05-2007, 10:47 AM
To my knowledge, and a quick internet search, DX9 has no way to be interfaced with VB6, just because Microsoft said so, and I couldn't find it, doesn't mean its not possible in some shape or form, since DX9 also contains DX8 and DX7.
04-05-2007, 11:31 AM
I'm pretty sure Unformed uses DX9, but it's also not VB. Shan doesn't use VB anymore, he uses PB (Pure Basic). That could be what you were thinking of Obsi.
04-05-2007, 02:47 PM
Well you can probably create a DLL to wrap the DirectX calls in another language, then call that from VB, but I see absolutely no point in doing that. It'd just be a waste of time. If you want to use a tool that doesn't work with your language, learn a new one. :wink:
04-05-2007, 07:50 PM
Spodi Wrote:Well you can probably create a DLL to wrap the DirectX calls in another language, then call that from VB, but I see absolutely no point in doing that. It'd just be a waste of time. If you want to use a tool that doesn't work with your language, learn a new one. :wink: exactly. and besides if you know enough to make a porting wrapper for VB in another language, why not use that language ![]()
04-05-2007, 08:54 PM
xD, well anything thats better then the DX7 right now thats compaitble would be good in tut :o
04-05-2007, 09:32 PM
Writing a tut is pointless because by simply following a tutorial on putting it into Mirage, you shoot yourself in the foot.
You won't be able to manage to code, debug the code, edit the code, create add-ons for the code, etc. etc. Quote:Robin:
06-05-2007, 10:43 PM
You both are right. Creating a DLL wrapper for DX9, to be called from VB, was what I was working on at one point using PB. But yeah, it's better to just learn another language.
But what's the point? To have the benefits of DX9, and soon 10, in VB6.
07-05-2007, 01:28 PM
But have we got to the point where using DX9 and DX10 is a serious advantage for the games we are creating?
Quote:Robin:
07-05-2007, 03:26 PM
Unless the game your creating is in 3D, or you want/need the extra speed ... nope.
07-05-2007, 03:43 PM
So we shouldn't really be worrying about the need to render more than 1000 sprites (which I can do in DX8 without my fps dropping below my monitor refresh rate). So is the extra work and language knowledge needed to use DX9 and DX10 really worth it, even in a 3D game? Because I don't think anyone programming in VisualBasic will need anywhere near that amount of Sprites on screen at the same time, even in tandem with 3D models.
Quote:Robin: |
« Next Oldest | Next Newest »
|