The game plan, at the moment:

* Wrap DirectDraw 2,3,4 and 7 to Direct3D9. Games that use these renderers have the most issues under Windows 7 and Vista.

This will involve rendering to textures or surfaces. Ultimately, at this stage, I just want to compile a wrapper DLL that wraps *right* before we replace the rendering functionality using D3D9. Saves a lot of hassle, since there is a *HUGE* amount of DirectDraw functions that need to be replicated properly. Fortunately, we don't need to reinvent the wheel too much since Wine luckily has most of the research done.

From there, I can imagine a lot of nice things. Shaders in ZSNES, Kega Fusion, Regen & SNESGT are already some of my ideas.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

who the fuck is that?

oops.

hah, dunno .

But yeh, I came up with some more ideas.

Would be nice to wrap D3D8 to D3D9, in the same DLL. Entry points won't be a issue, due to the different functions for creating a DirectDraw/Direct3D context.

Least it will also allow shaders in Jabo's plugin, too.

I have an idea:
You should look at the Wine source code. They probably already have some kind of DirectDraw code you could modify or backport to Windows.

http://www.winehq.org/

**** wine.

we want a wrapper, not an emulator.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

It isn't an emulator.

@Spacy: Already done so. Its a goldmine. Saves my skin, so I know exactly how much to wrap and the arguments some DirectDraw functions expect. And the API interface.

Which means only Ddraw 2/3/4/7 need to be wrapped. DirectDraw 7 only adds Clipper* functionality, everything else can be reused, including pallete usage.

Only issue is: how exactly to define DirectDrawCreate(). From there, I need to spawn the renderer and the different DirectDraw interfaces depending on the GUID used when creating the instance.

---

(11-05-2009 10:18 AM)I.S.T. Wrote:  It isn't an emulator.

But it emulates too much. It wraps DirectDraw -> Direct3D -> OpenGL.

That is pointless to port.

WINE is an emulator, written by faggots who want to be sophisticated and claim it isn't.

Read the definition of emulation in the dictionary. IT IS an emulator.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

@Squall: I did not mean to use Wine 1:1 but to use it as a code base. It's open source, after all.
You should also restrict your offending use of language. It creates a bad athmosphere.

I'm adopting the snes/zsnes mentality.

IE, i don't give a shit.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

(11-05-2009 06:38 PM)Squall Leonhart Wrote:  faggots

Go cry to the PC pussies.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

Not only is your taste in gaming poor(given your name and avatar), but apparently your deductive and language faculties are severely lacking as well. Why don't you wipe the Vegemite and Kangaroo shit off your eyes and try looking at this thread again. You'll clearly see that you shouldn't argue with your superiors.

Irony intended.

Squall, Spacy is right. Please don't wreck a nice thread.

Spacy is awesome suggesting the Wine code as a base, for adding shaders/2xSai/HQ2X/bloom to nuclear blasts to Starcraft as well as fixing some major game bugs with pallete usage. It saves a immense amount of work working out DDRAW.DLL.

And also, why reinvent the wheel?

(11-07-2009 10:06 AM)I.S.T. Wrote:  Not only is your taste in gaming poor(given your name and avatar), but apparently your deductive and language faculties are severely lacking as well. Why don't you wipe the Vegemite and Kangaroo shit off your eyes and try looking at this thread again. You'll clearly see that you shouldn't argue with your superiors.

Irony intended.

I R board creator, now bow down to me biatch

anyhoo....

What did you learn by RE' starcraft mudlord?

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

(10-24-2009 09:39 AM)mudlord Wrote:  The game plan, at the moment:

* Wrap DirectDraw 2,3,4 and 7 to Direct3D9. Games that use these renderers have the most issues under Windows 7 and Vista.

This will involve rendering to textures or surfaces. Ultimately, at this stage, I just want to compile a wrapper DLL that wraps *right* before we replace the rendering functionality using D3D9. Saves a lot of hassle, since there is a *HUGE* amount of DirectDraw functions that need to be replicated properly. Fortunately, we don't need to reinvent the wheel too much since Wine luckily has most of the research done.

From there, I can imagine a lot of nice things. Shaders in ZSNES, Kega Fusion, Regen & SNESGT are already some of my ideas.

Awesome idea! Though why settle on D3D9? It sounds a bit counterproductive to me when we have D3D11. I don't know too much about the technical differences between the versions however, so it may be better, but I would think D3D11 is more fitting since it's a newer version..

Direct3D 11 without tessellation is pretty much D3D9/10 with additional multithreading.

Besides, D3D10 and 11 are just supersets, as in they make use of the functions of D3D9 and just add their own additional features...

so even if we used D3D11 on paper, in code it'd just be D3D9 features used. (atleast thats the basic gist of it)

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

[/quote]

I R board creator, now bow down to me biatch

anyhoo....

What did you learn by RE' starcraft mudlord?
[/quote]


Blizzard abuses DirectDraw 2.x like crazy :S. Why can't they do things cleanly? It makes things much harder than they already are.

sounds painful lol.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7