Topic: dink's FBN Development & Fixes thread

[dink]

Actually, the reason I?ve always used the 32-bit version is because the 64-bit version doesn?t fully support all the filter systems available in 32-bit. I think a lot of us are in the same boat ^^

Best regards

I think you're talking about the Direct3d7 blitter?  Unfortunately this doesn't exist on 64bit Windows (at all), but, the DirectX9 blitters are really nice now, and dx9 also uses about 1/10th the cpu usage as D3D7 to blit to screen - which makes stuff like cv1k and snes a bit faster.  Dx9 also has the nice hardfx filters

best regards,
- dink

[TNTRafael]

I think you're talking about the Direct3d7 blitter?  Unfortunately this doesn't exist on 64bit Windows (at all), but, the DirectX9 blitters are really nice now, and dx9 also uses about 1/10th the cpu usage as D3D7 to blit to screen - which makes stuff like cv1k and snes a bit faster.  Dx9 also has the nice hardfx filters

best regards,
- dink

We trust in you, no doubt about it

I'm using the 64 bit too in the main PC, but the 32 bit build still useful on old machines to help keeping them alive a little longer

The Direct3d7 blitter looks way nicer than the basic directdraw 7 if you have an old graphics card/system for whatever reason

anyway thank you and the rest of the team for your hard work to keep everything running flawlessly, you all are the best!

[barbudreadmon]

The Direct3d7 blitter looks way nicer than the basic directdraw 7 if you have an old graphics card/system for whatever reason

Dink was talking about directx9 though, not directdraw 7.

While i can somehow understand windows xp users still using 32-bits builds (windows xp 64-bits exists, but very few people used it), dx9 is the recommended blitter and is available to old machine users.

[barbudreadmon]

Turns out the limitation is 2GB for a 32-bits process, so yeah that's definitely the problem.

I think there are ways around it at compilation level, i'll look into it.

So, about that workaround, there seems to be some linker flag named "--large-address-aware", which supposedly allows 32-bits apps to use up to 3GB ram, however testing this as a linux user has been troublesome.

On a sidenote, it seems someone is making progress on RE'ing paprium's music, so using samples might become unnecessary soon ?

[7zxkv]

I?m wondering if there might be a missing feature in the 64-bit build that I really enjoyed using in the 32-bit version?specifically Direct3D7 / Enhanced and 3D projection. I haven?t found them in the 64-bit build so far. Furthermore, in the 32-bit version, I was able to combine scanlines, 3D projection, and 2xBr (or similar) for a more refined visual experience?something that doesn?t seem possible with the 64-bit build. That said, I find it a bit surprising that DirectDraw7 is supported in 64-bit, but not Direct3D7. I imagine there must be some technical reason behind that which I don?t fully understand yet ^^

[barbudreadmon]

I?m wondering if there might be a missing feature in the 64-bit build that I really enjoyed using in the 32-bit version?specifically Direct3D7 / Enhanced and 3D projection. I haven?t found them in the 64-bit build so far. Furthermore, in the 32-bit version, I was able to combine scanlines, 3D projection, and 2xBr (or similar) for a more refined visual experience?something that doesn?t seem possible with the 64-bit build. That said, I find it a bit surprising that DirectDraw7 is supported in 64-bit, but not Direct3D7. I imagine there must be some technical reason behind that which I don?t fully understand yet ^^

I'm not a windows user so i am by no mean an expert of standalone FBNeo. If something useful is missing from the recommended dx9 blitter then it should definitely be reported instead of using 32-bits builds for the sake of using the old d3d7 blitter.

What's "3D projection" ?

[7zxkv]

This is the so-called fish-eye effect, which is absent in the 64-bit version (by the way, several things are missing when comparing the two builds). The only thing I don?t understand technically is why fbn64 offers DD7 but not D3D7, even though it?s from the same generation? It?s the only thing I?ve never understood?there must surely be a specific reason, but for our information, do you know what it might be?

[barbudreadmon]

IIRC the functions to create a d3d7 context just fail on 64-bits, unlike dd7's, i'm not entirely sure anyone knows the exact reason (maybe dink looked into this ?).

[dink]

d3d7 doesn't exist on 64bit, its impossible.  ddraw7 (2d, basic video stuff) does