Post by: OUberLord on June 09, 2003, 04:50:00 PM
Post by: jsm on June 09, 2003, 06:55:00 PM
Post by: cantloseu on June 09, 2003, 06:55:00 PM
Post by: cantloseu on June 09, 2003, 07:32:00 PM
Post by: jsm on June 09, 2003, 07:42:00 PM
Post by: UberJim on June 10, 2003, 08:42:00 AM
Post by: gainpresence on June 10, 2003, 10:20:00 AM
I may go pick up VS.net (or order the 60day trial) and try to get the control config working from an INI file
Post by: phantazma1 on June 10, 2003, 10:23:00 AM
Post by: UberJim on June 10, 2003, 10:49:00 AM
| QUOTE (phantazma1 @ Jun 10 2003, 06:23 PM) |
| i have .NET at home. i can compile it for you guys later (i'm at work) and give you a link to my ftp address (is that legal?) |
Well if you compile what I did, I would like to hear if it works or not, that isn't illegal.
Post by: MillerTyme on June 10, 2003, 05:57:00 PM
Post by: UberJim on June 10, 2003, 06:17:00 PM
Post by: MillerTyme on June 11, 2003, 01:39:00 PM
Post by: phantazma1 on June 11, 2003, 01:56:00 PM
i tried to execute the .xbe file but it would freeze on the evox loading screen.
maybe i'm doing something wrong.
Post by: UberJim on June 11, 2003, 05:10:00 PM
Post by: Iriez on June 11, 2003, 06:06:00 PM
| QUOTE (UberJim @ Jun 11 2003, 07:10 PM) |
| Well no dice on this one for now at least. We hit a road block in compiling the other parts, and through a "he said, she said" kind of thing I got wind that the original author doesn't want this to continue. The original author intends on releasing an update soon. |
The author hasnt been contacted about it. Someone asked me if they could host it on xbins and i said no. The author will release a new version soon enough, and i dont need anymore bandwith hammering for just a small fix every day.
Post by: MillerTyme on June 11, 2003, 08:17:00 PM
Post by: Vegita on June 11, 2003, 08:34:00 PM
| QUOTE (jsm @ Jun 10 2003, 04:42 AM) |
| All i need is vc++.net damn This woulda've been fixed already if i had vc++.net damn. redamn |
Or the full version could force its way onto ur hard drive from the usual places on the internet.
Post by: UberJim on June 11, 2003, 08:34:00 PM
Post by: mace on June 11, 2003, 09:29:00 PM
The default.xbe passes a command line to those .xbe's.
If you wanted to compile the PJ64-rice32.xbe you would have to move some files around.
Notes on the Source
===================
To compile an xbe with Rice's plugin make sure you enable all the files
in /OldVideo and disable all the files in /OldVideo. Compile away.
To compile an xbe with daedalus plugin make sure you enable all the files
in /Video and disable all the files in /Video. Compile away.
No other support for the source will be provided by Xbins.
Post by: UberJim on June 12, 2003, 08:46:00 AM
| QUOTE (mace @ Jun 12 2003, 05:29 AM) |
| The default.xbe is just a so called dashboard for the emulator, all it does is list roms and lets you pick which compile version you want to launch, PJ64-daed.xbe, PJ64-rice.xbe, PJ64-daed32M.xbe, or PJ64-rice32M.xbe. The default.xbe passes a command line to those .xbe's. If you wanted to compile the PJ64-rice32.xbe you would have to move some files around. Notes on the Source =================== To compile an xbe with Rice's plugin make sure you enable all the files in /OldVideo and disable all the files in /OldVideo. Compile away. To compile an xbe with daedalus plugin make sure you enable all the files in /Video and disable all the files in /Video. Compile away. No other support for the source will be provided by Xbins. |
You see, that is part of the problem, the release notes don't make sense. Enable all of the things in this folder and disable all of the things in the same folder. It also doesn't explain how to do the 32meg optimized counterparts.