I think svn is just broken right now, but i'm not sure. Just switch back to pcsx2 0. I thought it was with svn Comment Russell Harmon UTC I've added a pcsx2-playground to allow you to build one of the unofficial builds of pcsx2. That one works, use it. As for pcsx2 itself, I hadn't changed anything in the ebuilds recently, so my best guess as to why the release build is broken is that they changed something in svn and backported it to the release and replaced the tarball that is on sourceforge.
I may be wrong, but I really think it's pcsx2's fault and I don't know how to fix it or I would make a patch to. If someone else can fix it, post a patch and i'll include it in the repo. It looks more likely that binutils 2.
This version only hit the tree a few days okay. If you haven't upgraded yet, try it now, then upgrade and try again, ensuring that a new tarball isn't fetched for pcsx2. I tried downgrading my binutils I had already upgraded and that didn't fix the compile errors.
Tpo -c -oConfigDlg. What does it mean? I'm using 1. It's not that it doesn't recognize the option man page includes it as well , it tells that overlay doesn't exists happens with wgetted local file too.
Fortunately, the other way mentioned above seems to work for the people who are experiencing this problem. Now the bigger problem is figuring out why pcsx2 doesn't compile any more Unfortunately, I have the same merging problem as Paul : Comment Russell Harmon UTC I just tried compiling pcsx and it compiles for me now.
I masked pcsx It was being caused by gcc 4. I figured it out by looking at the commit messages in svn for pcsx2 so shouldn't actually get the credit for solving the problem. I also fixed the pcsx2-playground ebuild so that compiles for me now. One thing I noted was that there seemed to be a custom-inis patch merged into the pcsx2-playground svn repo. Is one of the pcsx2-playground devs a gentoo user? It will then show pcsx2-overlay. It's old and I don't think it even builds anymore.
Anyone tried bumping one of the older ebuilds? Comment Russell Harmon UTC I had been really busy with my school, but I should have time to try to make it work this weekend. Comment Russell Harmon UTC I should also add the fact that I was not aware that a new version had been released I thought I was just procrastinating fixing the svn ebuilds.
My apologies to the gentoo-pcsx2 community. I will fix it today. I dropped pcsx since it doesn't work i'll re-add it when I fix it. Note that pcsx I've emailed one of the developers who I have a correspondence with asking him to release source tarballs on their googlecode page.
There is no obvious mistake as an -m32 in there. Portage 2. S: Maybe I should add that there is no 32bit libgio Comment Russell Harmon UTC In that case, i'm missing one of the emul libraries from the ebuilds dependencies I have class, but I should be able to figure out which one has libgio after class. Yes, I have the same failure as Dennis on amd Could you please post your emerge--info, so we can compare?
I can't even find references to gio in the source code! I pushed a patch which bumps the compile-time version number. Comment Russell Harmon UTC I should also point out that pcsx2 on amd64 won't work until I port the plugin ebuilds to build bit plugins.
Did PCSX2 drop amd64 support? Oh well, it never really worked anyway. The library would be removed again by --as-needed, but before ld can decide that it is needed.
Feel free to start telling me about issues. And of course still the incompatible libgio How did you fix that? Comment Russell Harmon UTC As a general call out: I'm looking for another developer to help maintain the pcsx2 ebuilds.
This is not to say that i'd stop working on it, but someone who could devote their time to working on svn ebuilds or something along those lines would be ideal. So anyone who is familiar with writing ebuilds and the pcsx2 build system, please send me an email russ eatnumber1.
Argh I'd love to help Every time I want to sit down and write an ebuild it becomes much more complicated than I originally thought. In any case, the pkg-config files would be the same between the two archs It would be helpful, because the pkg-config files would not be the same. Thus a package using pkg-config --libs would only try to link against the libraries which are actually present for the given arch. I created bug for the pkg-config issue.
To aid user you should bump the revisions of those in your overlay and then depend on the bumped revisions. I propose adding a shell-script wrapper. The issue magically vanishes when using the one from the pcsx2 overlay. I assume the internal copy pcsx2 uses to link against in the absence of a 32bit system GLEW is outdated or otherwise broken.
For some reason, this was the version that was installed, and something decided to downgrade it automatically to 2. Graphics seem quite choppy and games are basically unplayable due to so many artifacts and glitches, but this is possibly due to fglrx. Is there a reason that the nvidia-cg-toolkit version in the overlay is 2 versions old, and could this be causing issues?
Even going in the BIOS is slow and drops framerate. I haven't done much testing with PCSX2, I need to compile my own version I think, but I think you're going to be limited by your graphics card. From what I can see, doing a quick Google search, the is a pretty basic graphics card. Your dual core CPU should handle it nicely but the bottleneck is the graphics card. I wouldn't really call a Go a pretty basic graphics card : I use this machine to play all manner of games, and it has absolutely no trouble pushing out the power necessary to run any game I've thrown at it so far.
That hut my feelings :cry:. He is correct though. Any game that is cpu dependent should run great for you. GPU dependent will die. Make sure your laptop does not overheat, at least. Is there any particular reason that even going into the BIOS is slow?
You know, the 3d cubes and all that. That's the same fps I receive when loading up the game. Any possibility of using a different display plugin that might help any? Have you enabled all of the recompilers and the dual core stuff?
I have. There was a minuscule difference :. With a pentium 4 3. There is definitely a problem with your setup. You are using ZeroGS, right? SPU2 1. I've noticed that the BIOS loading screen with the cubes is about After I get to the menus everything is fine.
Nothing's changed since yesterday, so I have no idea. Sorry I'm late with this, I don't check these boards much anymore. The emulator does NOT place nicely with sync to vblank. Seems to work fine now, haven't tested it with any roms yet though. I checked my nvidia-settings and my xorg. Where might I find this option hiding?
OK I receive this error how can I correct it? And at the risk of sounding really dumb how do you install the Nvidia Cg-Toolkit? DEB file, then install. Playable framerate requires an overclocked core 2 duo. Some graphics-intensive games like resident evil are going to also require a decent video card read: gt or better.
People will sugarcoat this but that's the reality. Nvidia-settings, under opengl settings. Uncheck sync to vblank. If you're running a desktop compositer, kill it before running the emulator.
Some graphics-intensive games like resident evil are going to also require a decent read: gt or better. How exactly do you use this? I put the game in and nothing happens. You also have to run the program. Give details. Your question tells us nothing. Bitterness: I have a gt and can barely run most games on my 2. You'll have to scroll down a bit to find it, as the blog posts cannot be linked directly.
Anyway, yes, your GS will most likely be fine for most games. It should be noted that zerofrog is planning a large update to the opengl rendering engine for the next version, and all of this may change. If you have followed the instructions in the first post in order to compile it from SVN, the program can be run by going to the directory you installed it into, choosing the bin folder, and then running pcsx2.
You will want to change some of the settings under Config, such as enabling all of the recompilers in the ZeroGS plugin, and multicore support if you have it. Also, you should select a dvdrom plugin so that you can run your games from the discs themselves, which your first post implies you have. This can be dumped from your PS2 using instructions found elsewhere.
You can also er After that, clicking Run CD from the file menu in pcsx2 will run your game. This emulator rocks! Too bad it needs a beefed-up PC to run a game properly. Always seem to come to a halt here..
I have an ATI card as well and it worked for me. Now when I load my GT4 iso, it goes to the screen that you usually get on a PS2 when there's no disk inserted. Where you choose from memory card or browser etc. Thanks, the graphics plugin compiled. But it seems now I got another problem oh vey..
Sorry for the noob question, but where is the actuall program? Sorry im pretty new to this. You run the pcsx2 file in the bin directory, E. Oh, I compiled it. Or you could force the i one.
Unfortunatly I am still learning and dont know the commands to do things like this. Okay all good then. When i run pcsx2 happens this : ZeroGS window is black but fps continue counting Any solution? Sorry for my bad english ; I've the same problem, ZeroGS window is black and then crash the sound is good P. This is the bash output:. With the pre-compiled linux binaries it's the same problem. Any suggestions? Same Problem here: I have re-installed cg-toolkit but the error still occurs.
I haven't seen that one before, unfortunately. I suggest filing a bug report on their official forums. I compiled version 0.
Even though I now hear robotic sounds, the sound plugin configuration still fails to load. The ZeroPAD plugin does not react to the input I presume the other is for windows since the GUI is distorted and not reacting to input from the controller either. You can play Playstation 2 games in it, although you'll need a fairly high end machine. Okay, so I compiled it and everything, but stupid question here, how do I run it?
Now I'm getting permission problems. Is there any way to reverse the process. BTW, I am a Linux n00b but I think it's about time to learn Go back to the root user account and change the permissions by hand to your other user. I tried to compile, but i got the following error s : Building SPU2 plugins The guide actually recommends that you PS2 isnt chipped, you need either a flash drive to dump the file.
I'll burn it and test it later, i havent used this particular one yet myself. Following as much information as I could find thus far, I am still unable to compile this either from tarball release or from SVN, the binary doesnt work either.
I am using an amd64 setup, I have tried on both feisty and gutsy, both svn and stable release, and am still unable to compile. Would anyone please take the time to make a Deb file? Buttons I need you! I have a problem playing any and all games with PCSX2, even the bios loader crashes after just a couple of seconds.
My card supports 3 and 4, but not 2. Therefore I needed to switch to a different plugin. After downloading GSSoft 0. I then proceeded to download the source for the plugin it was actually still in my SVN download directory and compile it, but when I run build. Any suggestions would be great! Tpo"; exit 1; fi zerogs. Any ideas? I'm having the same problem as antman. Anyone know of a fix? EDIT: The only info that I've found is that it has to do with mesa and a "renderbuffer that is attached more than once.
I seem to have unfortunately lost the link, but i have read in some forum that its a bug in the new version of mesa-common-dev version 7. One possible solution is to downgrade to the old version 6. However I'm not sure about dependencies and I was unable to get it from repositories guess its not there anymore.
I didn't have time to look for more solutions so far, maybe it would be best to wait for a fix? Thank you, buttons, for the guide. I thought I had all of the required stuff installed but the graphics plugin wasn't working. It will be a horrible approach like daemonps2 does, but at least its open source haha. I mean, double emulation its the horrible approach. Box86 may have a. Whatever, hope we can launch some games. Play emulator sucks.
I can't make any promises, but I'm going to look into porting to x64 because I need to get back into practice with dynamic recompilation for a different project of mine and this seems like a good way to do that. I can tell you that in the x86 folder, iCore. Otherwise, a lot of files in there are obviously instructions for certain chips. That lone assembly file is just for supervu, and some things in there are complicated by having both supervu and microvu coexisting, honestly What would be a good place for general discussion towards this?
Is the IRC channel active? Should I open an issue for discussion? Generally speaking, I think the pcsx2 discord group is where a fair amount of discussion happens, and the dobiestation one may be worth going in as well, since that's where the most active discussion of developing a ps2 jit tends to happen, even if it's not for pcsx2.
I'm honestly looking forward to proper 64bit recompilers, it would be neat if this would make a speed difference, especially for low power mobile CPUs like Core-M. Could you just answer that guy instead of just sending emoji reactions? We know you don't have the devs..
Core M is x86, and as stated countless of times a 64 bit recompiler or vulkan, or whatever wouldn't bring any particular advantage. And all of this is just useless clutter in the already thin-of-information thread.
A bit recompiler will not improve performance on low-power machines. It is entirely possible and indeed quite likely it will be slower initially though eventually it should be able to at least match the x86 recompilers.
That's it. Nothing more. There's no magic speed improvements, and it'll likely be slower initially and take a while to catch up. Yeah, I thought that was the main interest.
Especially than on the not that far future x86 will completely dropped, and we will had to use VMs to run that programs.. That's the big reason why we need 64 bits. Linux distributions really want to drop 32 bits. If they hadn't backed down, the 32 bit libraries would have been gone from new versions of Ubuntu not that long ago. I expect that'll still happen eventually, and I could see less and less Linux compatibility if things don't get ported to 64 bits.
Installation and development on Linux would be a lot easier if you didn't need to install a bunch of 32 bit libraries as well Then it was only ubuntu going bonkers imo. No way in hell that for a general purpose enviroment you can drop multilib in this decade.
If they drop it they drop it. Doesn't matter why or if you can comprehend it. We have to adjust accordingly. When I was trying to develop for pcsx2 on Mint, which is Ubuntu based, I remember I was having enough trouble cross-compiling that I had to set up a 32 bit chroot to compile in.
Then I started running into trouble because the chroot was Ubuntu and couldn't be upgraded past a certain point because Ubuntu no longer had a 32 bit version. Anything using apt-get and multilib is a pain, too. I don't know how many times I was told I couldn't install something 32 bit because the dependencies weren't installed instead of installing them, or asked if I wanted to uninstall 64 bit packages I needed when trying to get the 32 bit ones installed.
What's new New posts New resources Latest activity. Resources Latest reviews Search resources. Members Current visitors. Everywhere Threads This forum This thread. Filters Search. New posts. Search forums. Forums Website Corner EmuTalk. JavaScript is disabled.
0コメント