12-15-2010, 07:19 PM
12-16-2010, 11:43 AM
What will it take to implant this into the regular builds updated daily?
12-17-2010, 12:18 AM
They could make game hacks like in PCSX2 but it looks like developers avoid to add more options, and I read that this patch breaks another games.
12-23-2010, 11:20 PM
They have support for it now! Rev 6650 and such have it well, without the bloom. Though they fixed it back in 6634. But I got another problem. The game crashes when I go into the break mode or whatever its caused. I'ma check now but if its not a known problem, let it be known now
12-24-2010, 01:20 AM
Yes, it works without errors and it hasn't the bloom effect in the menu, but it's VERY slow and the bloom effect returns in the single player game. So I had an idea: changing the DX11 plugin of the r6632 (64x) with the r6650 one and IT WORKS! No bloom effect in game and the emulator runs with 60/70 FPS *. There is only one problem... There is an error during the fights, here a screen
http://img841.imageshack.us/f/error1t.png/
I hope someone knows how to fix it...
* I have a PC with Windows 7 (64x), i5 760 @ 2.80 GHz, 6 GB RAM, Sapphire ATI Radeon HD 5670 with 1 GB, monitor with 1280 x 1024 resolution
http://img841.imageshack.us/f/error1t.png/
I hope someone knows how to fix it...
* I have a PC with Windows 7 (64x), i5 760 @ 2.80 GHz, 6 GB RAM, Sapphire ATI Radeon HD 5670 with 1 GB, monitor with 1280 x 1024 resolution
12-24-2010, 02:36 PM
(12-24-2010, 01:20 AM)Sakretsu Wrote: [ -> ]Yes, it works without errors and it hasn't the bloom effect in the menu, but it's VERY slow and the bloom effect returns in the single player game. So I had an idea: changing the DX11 plugin of the r6632 (64x) with the r6650 one and IT WORKS! No bloom effect in game and the emulator runs with 60/70 FPS *. There is only one problem... There is an error during the fights, here a screen
http://img841.imageshack.us/f/error1t.png/
I hope someone knows how to fix it...
* I have a PC with Windows 7 (64x), i5 760 @ 2.80 GHz, 6 GB RAM, Sapphire ATI Radeon HD 5670 with 1 GB, monitor with 1280 x 1024 resolution
Yea thats the error i was talkin about. thanks for taking a picture. it happens in unlimited adventure too.
12-24-2010, 06:29 PM
I know... It happens during fights with Break mode in Unlimited Adventure / Cruise 1 and during first video in Unlimited Cruise 2, but the DX11 is really perfect for all the three games with 100% speed and without bloom effect..
Folks07
12-29-2010, 11:21 PM
(12-24-2010, 06:29 PM)Sakretsu Wrote: [ -> ]I know... It happens during fights with Break mode in Unlimited Adventure / Cruise 1 and during first video in Unlimited Cruise 2, but the DX11 is really perfect for all the three games with 100% speed and without bloom effect..
happens to me too...is there a way to fix it?
12-30-2010, 07:33 AM
It's a plugin error.. We must wait a fix made by the developers. Anyway I sent a mail to the staff to report the bug.
12-30-2010, 11:02 AM
Seems that these games are finally in a playable state... Well, kind of.
For the break thingies, you don't have to use them. Just switch characters right before they activate, or don't use all of the attacks specified on the side.
Now, the same crash happens after you Activate one of those... Portals, or whatever. Make a state, switch plugin to DX9, ACTIVATED, switch back to DX11. It works fine this way.
Then you get to the boss fights, and the same crash happens. Now, THIS is a problem, since you can't save in between the intro of the boss fight and the actual fight, forcing you to stick with the lame DX9 plugin.
For the break thingies, you don't have to use them. Just switch characters right before they activate, or don't use all of the attacks specified on the side.
Now, the same crash happens after you Activate one of those... Portals, or whatever. Make a state, switch plugin to DX9, ACTIVATED, switch back to DX11. It works fine this way.
Then you get to the boss fights, and the same crash happens. Now, THIS is a problem, since you can't save in between the intro of the boss fight and the actual fight, forcing you to stick with the lame DX9 plugin.