I have to apologize to everyone now. I'm sorry. I was releasing a debug build. I'm stupid.
I'll explain like this: it was all of this 'cause I was totally sure a debug build would always have the name under "GSDX-dbg.dll" instead of "GSDX.dll". Also, the plugin said "GSDX r535 (1.14, SSE2)" on the emu so, yeah, it was confusing and all.
Now this time the release weight 952 KB, so it should be fine now.
I will not bother you guys anymore. I'll be sure next time.
Maybe you compiled the debug build, and then build Release build, VS just check the file gsdx.dll, it's still there and most recent, so it just didn't compile the release build
.
Btw, I think when we choose Release SSE2, SSSE3 and SSE4, the dll file should be in different name ( like gsdx-SSE4.dll for ex )
I've got an i7 920, and a 3870X2. What would be the best combination of plugins and settings for me? I'm not quite sure what to use. These plugins in the OP run fine but give me a lot of graphics errors (RE-C:VX).
Air: It could be done in reverse, first let the linker output to the relative bin path and then make the script copy it to somewhere else like a "distro" folder, which could be zipped and released easily.
Funnnny: Yes, switching between builds does not automatically rebuild the dll when the output name is the same and both's files are already compiled. In my own projects I usually have $(SolutionDir)$(ConfigurationName) as the output and $(ConfigurationName) as the intermediate dir, so the different binaries of the configs are well separated but those that belong together still go to the same place, with pcsx2 it's not possible, mostly because there are many other static files it needs that are better not duplicated. This (rare) no rebuild problem is still better to me than having to switch configs all the time at two places, once in visual studio and then in pcsx2. In pcsx2 I also had to make sure the plugin settings were updated because the ini goes after the dll's name, each would have its own.
(02-21-2009, 09:58 AM)Gabest Wrote: [ -> ]This (rare) no rebuild problem is still better to me than having to switch configs all the time at two places, once in visual studio and then in pcsx2. In pcsx2 I also had to make sure the plugin settings were updated because the ini goes after the dll's name, each would have its own.
It may or may not be up your alley, but I did add to pcsx2 the option specify command-line overrides for some plugins. So in your debugger options you can add this as a command line:
-gs $(TargetPath)
That will always start Pcsx2 with the plugin matching the current build target, even if the plugin's target name is like gsdx-dbg-somehashnumber-guid.dll
(the console notifies in yellow when it's using a custom plugin override)
Made some tests of GoW2 again and i think the problem of green is fixed but something in HW render do not allow it to be fixed, you see on the second screen the wall of something else moving after Kratos i think the problem in projection or something else, please Gabest take a look we knew that you concentrated on SoftWare render but please don't forget of HardWare part of your great plugin
Heya Gabest,
We were wondering if you thought of adding a shader interface that can use the GPU to add some nice effects to the low res software output.
Pete had such an interface for his psx gpu plugins, and many users wrote nice shaders for it already.
If that ressource could be reused in gsdx, it'd be great.
Example:
http://www.razyboard.com/system/morethre...026-0.html
Look here, there are times in GOW2 that the green screen disappears while in hardware mode:
[
attachment=13293]
The speed is very very nice too in HW mode. It's going to be a remarkable day for Pcsx2, GSdx and emulation itself when this green screen bug gets fixed in HW.
Oh and the FFX bug didn't really disappear as much as it moved to effect different areas it seems.
Some updates for my last post about fps drop on some scene in ffx, finally i have a chance to try on Win7.
WinXP dx9:
- Summon Shiva fps drop till 13+fps
- Highroad south end, fps drop till 28+fps
Win7 dx9:
- Summon Shiva fps drop till 55+fps
- Highroad south end, fps drop till 55+fps
Win7 dx10:
- Summon Shiva fps ~59 fps
Seeing the different of performance on dx9, I wonder if this is due to the OS or ATI driver problem?