GSdx

[Necron]

Greetings ,

I'm not sure if that bug was already reported but just in case.
There is one graphical glitch in Front Mission 5 you get blinking shadows and some background garbage. Basically this game has 1 step left for perfect emulation.
Attached are the SW and HW screens.

[Innuendo]

If people are dying to use bleeding-edge SVN builds, just compile them yourself we already have a very detailed guide on it. If you can't follow that, I don't think you should be using SVN builds in the first place.

I understand.
And where is that detailed guide, if I may ask ? I've been looking around, but still couldn't get vs2010 to compile gsdx...

[Bositman]

http://forums.pcsx2.net/thread-2373.html
No need to compile it under VS2010 either, no advantage yet. VS2008 works fine

[Shadow Lady]

Also take in count vs2010 is still in beta stages (well at least as far as I know )

[rama]

Yeah, very beta.
The gui crashes by just looking at it for too long.
The compiler and linker randomly can't find their files, and so on.

[Linear]

Hello Gabest ! Can you, please, add checkbox which will activate or deactivate postprocess skipping by games CRC's in GSDX config window ?
Your awesome plugin can allready render some FX without skipping (like SotC)

[BasilAbdef]

bug report. Tales of the Abyss [NTSC]. On those cutscenes where you press select and they start talking, background seems to be completely broken...check first image. This seems to happen since the rev. 1300+ (or near it)

EDIT: since it is a rather annoying bug i decided to go back on the GSdx rev. to a point where the bug no longer existed. On 1357 the bug is gone (see image number 2). So it was between 1357 and 1476. Sorry for not trying all of the GSdx, but there are just too much of them =P

I have this issue also (using the latest version 1650), and it is very irritating. The problem is that the newer GSdx versions produce a significantly higher FPS for me than the older ones in which this issue doesn't exist (1354 or so for me), but if I use the newer versions, all the text in these skits becomes completely unreadable.

[taltamir]

We removed it. Compile it on your own or wait for the beta releases

Jeez. Just what was the point of that.

People reporting crap 'bug reports' like omgz not working need dlls and such, clueless people making threads all the time about how the new beta breaks x-y-z games and expecting to get support etc.

The point of betas is for people to give us bug reports. Having a tested beta released as we have been doing so every so often, which does not suffer from random bugs helps a lot. People can get that and give us much more useful bug reports than what we are getting now.
It also cuts back on people using 10000000000 different builds, which we can't keep track of what was fixed/broken in each specific one making it that much harder to track bugs or help anyone.

If people are dying to use bleeding-edge SVN builds, just compile them yourself we already have a very detailed guide on it. If you can't follow that, I don't think you should be using SVN builds in the first place.

I just assumed it would be more useful to see bug reports with the absolute latest svn, since already for it to not be deleted outright it HAS to have been tested under multiple different plugin configuartions, no speed hacks, etc...

Fools posting useless reports and demanding support for a beta program as if they are paying customers for a final product will always exist. If they are such a problem, why not get a few volunteers here to police the forums better by removing such posts and sending those people PMs explaining what they need to do?

However if you say that it will be more beneficial for the project to look for bugs using a specific version rather than latest svn, than that is what I shall do. running any pre 1.0 version should be done for bug finding purposes anyways. So, just to be clear. Which exact version should I be running when hunting for bugs?

PS. VS2008 is a proprietary program by microsoft that costs money, so that also limits who can compile their own copy of latest SVN. I typically use netbeans

[Bositman]

I just assumed it would be more useful to see bug reports with the absolute latest svn, since already for it to not be deleted outright it HAS to have been tested under multiple different plugin configuartions, no speed hacks, etc...

Nope, that's the whole point, SVN builds are NOT tested AT ALL and bugs will lurk in many of them, even very serious ones.

However if you say that it will be more beneficial for the project to look for bugs using a specific version rather than latest svn, than that is what I shall do. running any pre 1.0 version should be done for bug finding purposes anyways. So, just to be clear. Which exact version should I be running when hunting for bugs?

Latest stable released beta would be best. We can always test ourselves if the issue was fixed in the latest SVN (you doing it for us would be even better)

PS. VS2008 is a proprietary program by microsoft that costs money, so that also limits who can compile their own copy of latest SVN. I typically use netbeans

You can compile with VS2008 express, which is totally free afaik.

[DKTronics]

There is already a Bug Reporting forum to post for bugs, no need to clutter up this thread.