GSdx9

[next gen gamer]

Ok. . .
I will waiting for the official release from gabest. .
Gabest go for it!!You're the best!!

[rainbow]

Guys, before u start yelling at everyone u should ask gabest and mods first for a permission to post compiled svn ver of GSDX.

[serag4000]

I Guess it's Like, The Coder might know there is an Issue in His Code that needs to be fixed, He Waits till things are "Good Enough", then, "Try out people, Does it do the Trick ?"

But if u Can Compile it, You might as well se an Issue to point out for the Coder to take care of....

That's what I Think is behind the SVN Rule

That's Flawless in Gsdx, But is TOO BAD for Pcsx2, Coz the Updates are too far, meaning that a New Build is Something Big, then just some private testers try it, & then redo....
I Think it should be ok to test the SVNs, Say What's wrong Without asking for Fixes or Help....
Just Stating Using v.123, I Got Issue X,Y & X in Game (G)

Then Again, I'm Sure convincing people to do Just That may prove to be Hard

[J0hnny]

Only one question, where declaration or description of these functions?

unresolved external symbol "public: virtual void __thiscall GSState::Flush(void)" (?Flush@GSState@@UAEXXZ)
unresolved external symbol "public: bool __thiscall GSLocalMemory::FillRect(class CRect const &,unsigned long,unsigned long,unsigned long,unsigned long)
.................................................. .................................................. ....

[S23]

I understand godwin´s point. Here is a new discussion every second/third page how you compile it or any bugs in compiling (I only mean missusage of users). The reason is obvious. people with no or only very less knowledges stupidly downloading a free compiler only to get a build to work a few days before a stable release.
Something like this should only be made people that know what they do. If gabest allow it (write it down here) or tolerate it. I will compile an unoffical build here and there. maybe also without sse2. But I don´t know if this really would be good.

[KOC2000]

WOW! I didn't think posting svn versions would make such problems... I understood by SVN versions NOT supported that people DO NOT complain about them, I didn't know it's forbidden to be even shared compiled.

[Agetian]

Well, the position of the developers that SVNs are unsupported is very understandable - those are *intermediate* builds, completely untested and breaking some of the features from time to time. Certain things can be fixed but certain other things can get broken. I think it's very kind of the developers to provide access to the SVN for whoever wants it, and now the PCSX2 team even provides compiled SVN builds from time to time so that everyone can check them out, and Gabest is simply awesome making all those releases incredibly fast (awesome job, man! Make sure you give yourself a great Christmas and New Year's rest!) -- I don't think we're really in position to ask for more, let alone demand more.

As for SVNs -- if you'd like to test them, well - you can uncheck them yourself from the SVN and compile them yourself, it's not hard. You can think of it as a challenge that might be somewhat hard at first (if you never did it before) but that is rewarding when you succeed: you learn something new and you get a new build you desire so much at the same time. Personally I compiled the latest SVNs of both PCSX2 and GSdx myself and I can say it was quite easy to do it, probably much easier than it is to beg perpetually for someone to post a compiled vesion, which, as I understand, is not acceptable on this board.

- Agetian

[maxx77]

Please everyone, we do better stop criticizing the new SVN system and asking for compiled unrelased SVN betas, or the PCSX2 team might stop releasing public betas.

We must be grateful the PCSX2 team decided to share the once private builds to everyone of us; and the latest public SVN version released in the PCSX2 webpage was ONLY 10 days ago.

It seems some people don't remember or don't know that before the public SVN's, official PCSX2 builds were released 1 time a year, and now with the SVN system, we have already tested 3 or more beta versions.

Please, try to have patience, because even 1 public SVN version of PCSX2 a month is better than 1 official PCSX2 version a YEAR.

Thanks for your understanding,
Maxx77.

[fried_egg]

agree with the guy above me

[Agetian]

Seconded.

- Agetian

[Godwin]

Guys...this isn't a tea party. So stop gabbing about SVN stuff (spamming) and make with the detailed bug reports and such. I will let you know that I asked what to do before taking action. But I just want you guys to fill this thread full of feedback that will hopefully help Gabest somehow, since he doesn't have time to test every game nor has every game made.
Now on to our regularly scheduled program I hope.

[Kizage]

having problems with breath of fire 5.
1)When Capcom is shown in screen the screen shakes
2)The intro movie goes slow around 15 fps (30% or so)
3)The selection screen for new game and load game shakes
4)Name Selection screen shakes
5)Menu is not shown in game
5)Graphics is pretty messed up in game :/

Was wondering if anyone else had the same problem...:S

[Human]

mgs3 with svn 705:
snake got black face and blond hair. with 0.11.4 and 704 its was ok black hair and yellow face.
or maybe he is now afro-american:P

[Firnis]

Originally Posted by Kizage

... screen shakes

Try different interlacing modes (F5), it must solve your problem.

[orusskich]

Originally Posted by Kizage

having problems with breath of fire 5.
1)When Capcom is shown in screen the screen shakes
2)The intro movie goes slow around 15 fps (30% or so)
3)The selection screen for new game and load game shakes
4)Name Selection screen shakes
5)Menu is not shown in game
5)Graphics is pretty messed up in game :/

Was wondering if anyone else had the same problem...:S

The menu works ingame and the graphics work normal for me, and turn on interlacing.

[AndreaB]

i compiled SVN and i obtained 1,5Megabyte DLL... versus the standard 600Hbyte Dll...

What's happend? my mistake?

[Kizage]

Originally Posted by Firnis

Try different interlacing modes (F5), it must solve your problem.

well the interlacing mode helped the screen shaking but i have a few other problems
1)When you try to load your game at the bottom it asks if you want to load that save file the "yes or no" doesnt appear it goes the same for when you open up the menu and try to select items to drop/use/etc
2)The graphics are a bit crappy :/
3)The speed is like 17 FPS probably the slowest game i have so far if i have compared it to FF12 or FFX series which run perfectly fine and smoothly..

[Agetian]

OK, here are some testing results:

Test Subject: Final Fantasy X (original) SLUS-20312
System: Intel Core2 Duo E4500 @2,2Ghz, 2048MB RAM, GeForce 8600GT 512MB

PCSX2: Official v0.9.4, all optimizations on (EErec, VU0rec, VU1rec, MTGS, DC), Limit FPS mode (auto)
GSDX: GSdx9 v0.11.4 (official) and GSdx9 v0.11.4 build 704 (svn)
GSDX Settings: Interlacing off, 4:3 mode, windowed/full screen (1024x768 when full screen), NLOOP Hack on, Logarithmic Z on/off, Alpha Correction (FBA) on/off, all other options off, Pixel Shader 3.0, Direct3D9 renderer, Native D3D internal res.

The game runs very well and stable, when using build 704 the game runs @5-15fps faster in different areas than the official v0.11.4.

Both versions (official v0.11.4 and svn build704) cause a visual error in the form of intermittent stripes, usually white, gray, or black. The common cause of this (and a way to reproduce it) is entering the character menu and then leaving it. You can see the effect on the screenshots: before entering the menu (SLUS20312-before.jpg) there are no artifacts, but after entering and exiting the menu (SLUS20312-after.jpg), there are gray-ish stripes present on the terrain.

Another time I saw this was during the very first battle - the stripes were black and were seen far in the background. Unfortunately, I didn't take a screenshot of this (will do so when I retest). I'm not sure what caused the appearance of the stripes here.
EDIT: Uploaded a screenshot of this happening during the first battle (firstbattle-glitch.jpg), black stripes can be seen in the background.

Reloading the game from a memory card causes the artifacts to go away (until you, for instance, re-enter the menu next time).

Didn't try reloading from a saved state (not a big savestate fan, will try it out later if I have some time).

Turning Logarithmic Z and Alpha Correction on or off doesn't seem to affect this artifact.

Another bug I've seen when testing the same game was the appearance of thin white lines on the Sphere Grid after viewing the Sphere Grid isometrically. Unfortunately, I failed to take a screenshot there as well (the screengrabber program glitched), as soon as I reproduce this bug again I'll make a screenshot and post it here.

Hope this helps.

- Agetian

[Shadow Lady]

Originally Posted by Agetian

Another bug I've seen when testing the same game was the appearance of thin white lines on the Sphere Grid after viewing the Sphere Grid isometrically. Unfortunately, I failed to take a screenshot there as well (the screengrabber program glitched), as soon as I reproduce this bug again I'll make a screenshot and post it here.

Hope this helps.

know issue, basically nobody has any idea what's causing it :P

the black stripes ingame are normal so far ofc it's a bug but it's not a big issue if u change areas u barely notice the problem much, savestates would not take care of it

Originally Posted by Kizage

well the interlacing mode helped the screen shaking but i have a few other problems
3)The speed is like 17 FPS probably the slowest game i have so far if i have compared it to FF12 or FFX series which run perfectly fine and smoothly..

Final Fantasy series is of the very few games that can actually be played full speed, that's PCSX2 fault thou not GSdx :P

[gabest]

Originally Posted by Human

mgs3 with svn 705:
snake got black face and blond hair. with 0.11.4 and 704 its was ok black hair and yellow face.
or maybe he is now afro-american:P

Could you test it again with the latest from svn?