GSdx
(05-26-2011, 07:18 PM)taltamir Wrote: >the problem is fixed by switching to software mode (F9)
Software mode is completely unplayable and will not be playable for at least a decade. It is used entirely for testing purposes. It is not a fix for anything.

I wouldn't say it's unplayable; I can get a *relatively* decent speed in Software with a GTX 260M and a 2.53 GHz Core 2 Duo. On a good day. In less-detailed areas. With every speedhack in the book turned on.

Regardless, I am really tired of hearing snooty "Use Software mode. Bug fixed." replies. If we're all expected to have supercomputers that can run Software mode smoothly and we're supposed to just "deal with" the tiny resolution, why does Hardware Mode exist? I mean, I understand it's a project that's done completely for free by people working in their spare time, but it's not usually them that are quick to suggest Software Mode.
Reply

Sponsored links

(05-26-2011, 06:50 PM)PSDude45 Wrote: Will the developers of PCSX2 ever consider fixing the 'eyes' problem in the Jak and Daxter games, and do they know about it?

The devs consider fixing every problem... I don't see why you would ask such a thing Tongue2

The trouble is actually how difficult or how possible or how much amount of work is required to make it happen with the current state of emulation and the dev tools at their disposal or if they even know the cause of a problem to begin with (some remain a mistery Tongue2) or if it can even be fixed without breaking every other game. Just remember, devs do work in the emulator on their own free time.

And yes, most devs probably know about that particular problem.


(05-26-2011, 10:40 PM)Jaitsu Wrote: If we're all expected to have supercomputers that can run Software mode smoothly

I don't think you're expected to have/do anything really, if people is really interested in emulating their games in their PCs then suggestions and solutions are given, software mode is a known solution for that problem but if you can't deal with the "tiny resolution" or low speeds you can always play the games in a PS2 as they were meant to be or probably also playable in a PS3. PCSX2 is just another alternative.
Core i5 3570k -- Geforce GTX 670  --  Windows 7 x64
Reply
actually, gsdx is independant from pcsx2 core. When we say "use software mode" it means : "make sure the bug doesn't from from pcsx2, but from the gfx plugin you're using."

Gabest made and makes a fantastic work with gsdx, but the hardware part of it has to take care of the different gfx drivers and hardware. Since there are many, and they are under a constant evolution, try to imagine how hard it can be to support and develope...
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
Reply
Here's Super Monkey Ball Adventure (SLUS-21272 - status = Nothing).

Here's six different dumps during different points of the game. The game generally runs at about ~35-60 FPS on my 5770.

There is a filter which is used for fog (and darkness, in some). There is a filter similar to this in all worlds, although it might be used for colour instead of fog. What's interesting is that the filter is not over the screen, but instead a certain distance from the character (I guess that's how it was done for the fog, and not changed for the colour). The game varies on FPS, but I can't really determine how. Against a certain wall I get 60 FPS, but against others I don't. It might be because of how much of the filter appears on screen, but also just the general amount of polygons. Even with the filter, I get ~53 FPS in the puzzle levels, which are very simple. I'm sure you guys will know, as you've been doing this for a while.

My specifications: 3326MB RAM (4GB), Sapphire ATI Radeon HD 5770, Intel Pentium XII Xeon Processor (4 cores - each clocked at 2.33Ghz), Microsoft Windows XP Professional (32-bit)

Using r4671.

GSDX.ini:

Code:
[Settings]
Renderer=0
Interlace=0
AspectRatio=0
upscale_multiplier=1
windowed=0
filter=1
paltex=1
vsync=0
logz=1
fba=0
aa1=0
nativeres=1
resx=320
resy=256
swthreads=6
msaa=0
UserHacks_AlphaHack=0
UserHacks_HalfPixelOffset=0
UserHacks_SkipDraw=0
allowHacks=1
gamefix_skipdraw = 1
CaptureWidth=320
CaptureHeight=240
CaptureFileName=C:\Documents and Settings\kody\Desktop\PTR2.avi
CaptureVideoCodecDisplayName=

I don't expect any "magic bullet" to this, just like Raw Danger!, but I'll just upload this so hopefully the vertical stripes bug that comes with some filters can be fixed sooner and those types of games can run more efficiently.

Sorry about the huge number of parts for some of the .rars. Sometimes WinRAR will compress a 35MB .gs & a 1MB .bmp into 2-3MB somehow. Sometimes not.


Attached Files Thumbnail(s)
   

.rar   HWAgainstwallSMBA.rar (Size: 2,93 MB / Downloads: 128)
.rar   HWmonsterSMBA.part2.rar (Size: 6,68 MB / Downloads: 126)
.rar   HWmonsterSMBA.part1.rar (Size: 6,68 MB / Downloads: 122)
.rar   HWmonsterSMBA.part4.rar (Size: 283,44 KB / Downloads: 114)
.rar   HWpuzzlelevelSMBA.rar (Size: 4,34 MB / Downloads: 117)
.rar   HWmonsterSMBA.part3.rar (Size: 6,68 MB / Downloads: 120)
.rar   HWNormal(fog)SMBA.part1.rar (Size: 6,68 MB / Downloads: 117)
.rar   HWNormal(fog)SMBA.part2.rar (Size: 5,37 MB / Downloads: 126)
.rar   HWskipdraw=3;.part1.rar (Size: 6,68 MB / Downloads: 115)
.rar   HWskipdraw=3;.part2.rar (Size: 6,68 MB / Downloads: 122)
.rar   HWskipdraw=3;.part3.rar (Size: 3,29 MB / Downloads: 123)
Want to contribute? Don't know how? Check out the PCSX2 Wiki page!



Keep safe with MyWOT.

I have everything...
Reply
Hmmm... that Raw Danger game is developed by same company that did Steambot Chronicles, looks like the same bad postprocessing is what's causing the huge VRam usage in both. I have a half working hackfix for steambot chronicles, should be able to work for raw danger too, really gotta finish that Tongue2

BTW, you don't need to make a dump for each different setting you try, a single dump that shows the problem clearly is enough.
Core i5 3570k -- Geforce GTX 670  --  Windows 7 x64
Reply
(05-26-2011, 07:18 PM)taltamir Wrote: >the problem is fixed by switching to software mode (F9)
Software mode is completely unplayable and will not be playable for at least a decade. It is used entirely for testing purposes. It is not a fix for anything.

That's very relative. Most modern i5/i7 CPUs can play a vast number of games using software mode at full speed (or more). Your decade assumption is extremely far off from reality. Yes it does fix the problem, yes it does increase the raw cpu power requirements exponentially. So yeah it IS a fix to the problem. Speed is another issue.
Of course if you're up to you can always try fixing hardware mode or speeding up software mode (or just get a faster CPU) but you'll soon find it's so hard you should stop whining and just be glad for what you already have.
[Image: newsig.jpg]
Reply
I have an odd problem with Persona 4. Whenever using gsdx10 graphical bugs pop up on screen whenever text pops up. I have only been in the velvet room at the beginning but I assume its going to atleast happen everytime I go in there. I tried a version on gsdx9 and it didn't have that problem but graphics weren't as crisp. Anyone know what might be causing this? I have tried as many tweaks as I can think of and analyzed what is different about the 2 versions and nothing is coming up. My computer meets the specs to run it no problem. Its just this graphic bug.

EDIT: I also noticed that it says in the log that its not saving my configs because I don't have rights in the folder it selected to put the files, and I don't see a way to remap where it saves them to. I would like to set it to a different drive all together instead of my "my documents folder" Also this is in windows 7 x64
Reply
To fix your later problem, right click and run as administrator. If you want to avoid doing that every time, move your PCSX2 out of my documents or program files folders.

As for your P4 problem... Graphics bugs? Can you be a bit more specific? I haven't run into any and I was just playing it a few days ago. If you mean small lines it may be a texture filtering issue, change it in GSDXs options from a check mark to either off, or shaded.
Reply
(05-29-2011, 08:17 PM)Koji Wrote: To fix your later problem, right click and run as administrator. If you want to avoid doing that every time, move your PCSX2 out of my documents or program files folders.

As for your P4 problem... Graphics bugs? Can you be a bit more specific? I haven't run into any and I was just playing it a few days ago. If you mean small lines it may be a texture filtering issue, change it in GSDXs options from a check mark to either off, or shaded.

The bugs were certain textures flickering in the velvet room, like the chandelier, liquor bar on the left side of the screen and igor's mouth were pretty prominent. Like I said though they only started flickering when speech text would pop up. Otherwise, it was fine as far as I could tell.
Reply
(05-29-2011, 09:18 PM)lol817 Wrote: The bugs were certain textures flickering in the velvet room, like the chandelier, liquor bar on the left side of the screen and igor's mouth were pretty prominent. Like I said though they only started flickering when speech text would pop up. Otherwise, it was fine as far as I could tell.

Dx9 version of the latest Gsdx works fine for me with everything on (minus the allow 8-bit textures (seems to slow the games I have, go figure) and the hacks. Resolution is native. Using Blend bff and custom 1280x800 resolution.
Maybe the problem is misconfigured speedhacks. My config is 3 for the EE cyclerate, 2 for the VU stealing, all options enabled minus the fast cdvd. The round and clamp modes for the EE and VUs are the default ones (Chop/Zero and Normal, respectively for the round and clamp).
Did it help (the textures are broken in dx9 in certain walls, but that's an old Z problem, I think, fixed by Dx10, afaik)?
Reply




Users browsing this thread: 9 Guest(s)