Posts for BadPotato


1 2
17 18 19
22 23
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
here's the lastest wip that I downloaded(I made a savestate if you don't want want to playback the whole movie), but for the 15 sec at the end this is me trying my own failling test :p
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
For now the easier way would be to use reset while saving and corrupt data enought accurate to be able to do some crazy stuff... But I'm not very interested to explore this farther. So, I keep TASing this and I even start a SVN depot :) (just like some other.. but I like the idea) a next decent wip should come out soon
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
Warp wrote:
Bisqwit wrote:
This example code is designed to maximize the density of pointer use
I think it's also a good example of how obfuscated and hard to follow C quickly becomes with complex data containers.
since the bisqwit algorithm use some recursion function..(ouch my head!!) I doubt there language that would be easier either for the current problem.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
this is going to remplace one of the logo in the top-left corner like this one and this one or we are just talking about the logo for submission "without screenshot" ?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
eternaljwh wrote:
BadPotato wrote:
no one interested by lunar silver star/Eternal blue?
Possibly...
I've just test eternal blue on the actual pcsx-rr and it crash when zophar appear for the first time.. maybe pcsx-reload would be able to run, when it come out. For now I'm replaying Lunar II on sega-CD(gens) and trying to hunt for some glitch(I'm already into the write dragon cave and din't saw anything interesting), but I seriously think that this run should be done with the remake(PSX), since must enemy can be avoided easily(no RNG.. yeah!!), and we can skip the cinematic. ...Anyway, there also command & conquer on PSX that cool be nice even if this isn't pc version. I remember how hard it was to control the stick on the commando mission to sneak into the enemy base.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
ok, Bon j'espère que tu te laissera pas décourager par mon message, mais j'imagine que ta déjà compris que la plupart des gens n'aiment pas tes speedruns. Mais si c'est ton premier speedrun et bien dis toi qu'il a des gens qui ont déjà fait bien pire :) Le gros problème dans ce cas-ci c'est que ta mal configurer ton film pour qu'il puisse commencer au démarrage(le moment où on appuie sur le bouton power de la 64) et du coup personne peut voir ce que t'a fait!!! Ensuite, faut vraiment que tu comprenne que ceux qui poste leur run ici peuvent passer facilement des dizaine(voir centaines) d'heures juste pour que chaque fraction de seconde soit parfait. C'est comme ça que fonctionne et c'est pas toujours amusant. Si t'es vraiment motiver a faire un speedrun qui va surpasser celui-là, d'abord le mieux serait que t'essaye de maîtriser un peu l'anglais et te trouver quelques tutoriels sur comment faire des BLJ(backward long jump), muppen, etc... En tout cas, continue à t'améliorer, y'a personne sur cette planète qui est capable de faire ce genre d'exploit du premier coup(sauf peut etre Chuck Norris). Puis si tu te réessaye... prend la version US et poste ton fichier dans un des topic du forum(déjà existant) avant de le poster ici. :) ---- Quick traduction: Hope that you'll be enought motivate to keep tasing after my message and the other post from the angry member. If this your first run.. keep in mind that some people already did something worse than your. The most important problem in your submission file is because you doesn't start the movie at the boot and then nobody can saw your work!! Also, there a lot of freak people on this website. Actually a common submission should be about 10-20-30 or even more than 100 hours to be sure that each twentieth of second is perfect, etc. This how the whole thing work and trust me that this isn't alway fun. Thought, if your going to beat the actual run, the best way should be to learn some english basic... then seek for some muppen tutorial, BLJ tutorial, etc Anyway, keep praticing, nobody on earth should be able doing such run at the first time, but next time take the US rom and post your wip in the active mario64 topic. :) cheer
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
I've just try to run the gpu plugin and I got an error about the file "cygwin1.dll is missing". Then if I put this dll in my output folder, pcsx ask me to configure the plugin and when I choose my gpu plugin build, the program freeze before that the main windows pop up. :/ Thought if I choose your plugin pcsx run fine Also, look like that my build is a bit bigger that yours: mine: pcsx.exe 360ko gpuPeopsSoft.dll 666Ko (I should probably rename it as gpuTASsoft.dll) your: pcsx.exe 146Ko gpuTASsoft.dll 122Ko Any idea? maybe I should compile the gpu plugin without cygwin... I'll give it a shoot.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
I just trying to do an .exe from the pcsx source but I'm very confuse about what going on, since I have very basic knowledge in C and general programation.... anyway, now I feel more comfortable with cygwin and I manage to gather all the other missing lib to compile the gpu plugin:
badpotato@rorqual:~/trunk/pcsxrr/plugins/gpuTASsoft $ make
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows gpu.c -o ./release/gpu.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows cfg.c -o ./release/cfg.o
cfg.c: In function `DirectDrawEnumCallbackEx':
cfg.c:1286: warning: dereferencing type-punned pointer will break strict-aliasing rules
cfg.c:1295: warning: dereferencing type-punned pointer will break strict-aliasing rules
cfg.c: In function `bTestModes':
cfg.c:1508: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows draw.c -o ./release/draw.o
draw.c: In function `DXSetGamma':
draw.c:4723: warning: dereferencing type-punned pointer will break strict-aliasing rules
draw.c: In function `DXinitialize':
draw.c:4887: warning: dereferencing type-punned pointer will break strict-aliasing rules
draw.c: In function `ShowTextGpuPic':
draw.c:5485: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows fps.c -o ./release/fps.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows key.c -o ./release/key.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows menu.c -o ./release/menu.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows prim.c -o ./release/prim.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows soft.c -o ./release/soft.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows zn.c -o ./release/zn.o
nasmw -O1 -f win32 -D__WIN32__ -D__i386__ hq3x32.asm -o ./release/hq3x32.o
nasmw -O1 -f win32 -D__WIN32__ -D__i386__ hq2x32.asm -o ./release/hq2x32.o
nasmw -O1 -f win32 -D__WIN32__ -D__i386__ hq3x16.asm -o ./release/hq3x16.o
nasmw -O1 -f win32 -D__WIN32__ -D__i386__ hq2x16.asm -o ./release/hq2x16.o
nasmw -O1 -f win32 -D__WIN32__ -D__i386__ i386.asm -o ./release/i386.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows gpupeopssoft.c -o ./release/gpupeopssoft.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows record.c -o ./release/record.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows fpsewp.c -o ./release/fpsewp.o
windres gpuPeopsSoft.rc ./release/res.res -D__MINGW32__ -DNDEBUG
windres  -o ./release/res.o -i ./release/res.res
cd ./release/ ; \
        dllwrap -dllname gpuPeopsSoft.dll -def ../gpupeopssoft.def gpu.o cfg.o draw.o fps.o key.o menu.o prim.o soft.o zn.o hq3x32.o hq2x32.o hq3x16.o hq2x16.o i386.o gpupeopssoft.o record.o fpsewp.o res.o -mwindows -Wl,--enable-stdcall-fixup  -lddraw -lwinmm -ld3dim -ldxguid -ladvapi32 -lmsacm32 -lvfw_cap32 -lvfw_ms32 -lvfw_avi32
cd ./release/ ; \
        strip gpuPeopsSoft.dll
maybe this isn't the best place for reporting these compile log... hmm bah anyway. ok, now I would like to know where I can find the segu controller plugin source.. I din't find anywathing... does his controller plugin is open-source?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
my best advice would be that you keep working to (re)familiarize with the game and just trying to make up a decent route I just test by myself and I feel like your only way to manipulate the radom battle would be to manipulate before going into a "monter aera"... but this is definitly very hard to do it manually. So I think you can go ahead to TAS the game without any pressure, since the game is very long(I even stop playing the game near the beginning of CD2) and the attempt from SeedDemoArchive was unfinished. Honnestly, I think this is very meaningless to trying to make a perfect run of this game at the first try and just waiting for some "brute force" addons stuff, just like the FF7 speedrun, because there no developpement. If you have some problem with kkapture, explain us and we might been able to help you.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
mz wrote:
Maybe you don't have the DirectX SDK? Try installing this and see if that helps: dx80_mgw.zip.
I'm very confuse how I should this in cygwin... so I just dump everything in /usr/local/include and /usr/local/lib after, the make utility told me that "direct.h" wasn't here (even if I could find it in /usr/include/mingw/direct.h). Again, I just copy this in /usr/local/include Finaly, I ended up with this:
badpotato@rorqual:~/trunk/pcsxrr/plugins/gpuTASsoft $ make
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows gpu.c -o ./release/gpu.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows cfg.c -o ./release/cfg.o
cfg.c: In function `DirectDrawEnumCallbackEx':
cfg.c:1286: warning: dereferencing type-punned pointer will break strict-aliasing rules
cfg.c:1295: warning: dereferencing type-punned pointer will break strict-aliasing rules
cfg.c: In function `bTestModes':
cfg.c:1508: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows draw.c -o ./release/draw.o
draw.c: In function `DXSetGamma':
draw.c:4723: warning: dereferencing type-punned pointer will break strict-aliasing rules
draw.c: In function `DXinitialize':
draw.c:4887: warning: dereferencing type-punned pointer will break strict-aliasing rules
draw.c: In function `ShowTextGpuPic':
draw.c:5485: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows fps.c -o ./release/fps.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows key.c -o ./release/key.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows menu.c -o ./release/menu.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows prim.c -o ./release/prim.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows soft.c -o ./release/soft.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows zn.c -o ./release/zn.o
nasmw -O1 -f win32 -D__WIN32__ -D__i386__ hq3x32.asm -o ./release/hq3x32.o
make: nasmw: Command not found
make: *** [hq3x32.o] Error 127
this seem to be a problem with the assembler file
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
mz wrote:
windres Win32/pcsx.rc Win32/pcsxres.res
windres: Win32/pcsx.rc:278: syntax error
make: *** [Win32/pcsxres.o] Error 1
Well, there's a syntax error in line 278 of Win32/pcsx.rc, you may want to see what's there and fix it or just comment it out, as I always do when I find about an error. :P
ok, I commented this line and the rest compiled perfectly :D Then, I was interested to your gpuTASsoft plugin and try to compile it... but I have again some problem: first I had these missing file(for some raeson cygwin seem to doesn't have them) with lot of error
stdafx.h:36:19: TCHAR.H: No such file or directory
stdafx.h:44:19: ddraw.h: No such file or directory
stdafx.h:45:17: d3d.h: No such file or directory
(actually from my cygwin package manager I only add the devel, editor, gnome, libs, X11 category with the default package... I doubt that I have to install everything) So, I manage to google these missing file and add them Thought for d3d.h, I found on the cygwin drive d3d9.h that looked pretty similar... so I simply add this one too. Anyway after solve this problem gpu.c was ok but now I got stuck at cfg.c ... and he doesn't want to cooperate at all:
badpotato@rorqual:~/trunk/pcsxrr/plugins/gpuTASsoft $ make
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows gpu.c -o ./release/gpu.o
gcc -g -Wall -O4 -march=i686 -fomit-frame-pointer -ffast-math  -c -D__i386__ -D_WINDOWS -DNDEBUG -DWIN32 -D__MINGW32__ -mwindows cfg.c -o ./release/cfg.o
cfg.c:1248: error: parse error before "LPD3DDEVICEDESC"
cfg.c: In function `Enum3DDevicesCallback':
cfg.c:1254: error: `pGUID' undeclared (first use in this function)
cfg.c:1254: error: (Each undeclared identifier is reported only once
cfg.c:1254: error: for each function it appears in.)
cfg.c:1254: error: `pHALDesc' undeclared (first use in this function)
cfg.c:1254: error: `pHELDesc' undeclared (first use in this function)
cfg.c:1255: error: `D3DENUMRET_CANCEL' undeclared (first use in this function)
cfg.c:1258: error: `IID_IDirect3DNullDevice' undeclared (first use in this function)
cfg.c:1259: error: `D3DENUMRET_OK' undeclared (first use in this function)
cfg.c: In function `DirectDrawEnumCallbackEx':
cfg.c:1277: error: `LPDIRECTDRAW4' undeclared (first use in this function)
cfg.c:1277: error: parse error before "g_pDD"
cfg.c:1278: error: `LPDIRECT3D3' undeclared (first use in this function)
cfg.c:1282: error: `D3DENUMRET_OK' undeclared (first use in this function)
cfg.c:1286: error: `IID_IDirectDraw4' undeclared (first use in this function)
cfg.c:1286: error: `g_pDD' undeclared (first use in this function)
cfg.c:1295: warning: implicit declaration of function `IDirectDraw4_QueryInterface'
cfg.c:1295: error: `IID_IDirect3D3' undeclared (first use in this function)
cfg.c:1295: error: `pD3D' undeclared (first use in this function)
cfg.c:1297: warning: implicit declaration of function `IDirectDraw4_Release'
cfg.c:1304: warning: implicit declaration of function `IDirect3D3_EnumDevices'
cfg.c:1316: warning: implicit declaration of function `IDirect3D3_Release'
cfg.c: In function `DoDevEnum':
cfg.c:1333: error: `LPDIRECTDRAWENUMERATEEX' undeclared (first use in this function)
cfg.c:1333: error: parse error before "pDDrawEnumFn"
cfg.c:1340: error: `pDDrawEnumFn' undeclared (first use in this function)
cfg.c:1341: error: parse error before "GetProcAddress"
cfg.c:1344: warning: implicit declaration of function `pDDrawEnumFn'
cfg.c:1345: error: `DDENUM_ATTACHEDSECONDARYDEVICES' undeclared (first use in this function)
cfg.c:1346: error: `DDENUM_DETACHEDSECONDARYDEVICES' undeclared (first use in this function)
cfg.c:1347: error: `DDENUM_NONDISPLAYDEVICES' undeclared (first use in this function)
cfg.c: At top level:
cfg.c:1468: error: parse error before '*' token
cfg.c: In function `EnumDisplayModesCallback':
cfg.c:1471: error: `pddsd' undeclared (first use in this function)
cfg.c: In function `bTestModes':
cfg.c:1489: error: `LPDIRECTDRAW4' undeclared (first use in this function)
cfg.c:1489: error: parse error before "g_pDD"
cfg.c:1508: error: `IID_IDirectDraw4' undeclared (first use in this function)
cfg.c:1508: error: `g_pDD' undeclared (first use in this function)
cfg.c:1515: warning: implicit declaration of function `IDirectDraw4_EnumDisplayModes'
make: *** [cfg.o] Error 1
maybe I just do everything wrong about these missing header, I feel like adding an "include folder" might help to solve the previous problem... but for the other error this seem much more complicated.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
mz wrote:
I think for v0.1.0, I (or anyone else) should use PCSX-R, since that version already has built-in ISO loading and disc switching. We should call it PCSX-RRR v0.1.
Do you have to restart from the beggining if your going to use pcsx-reload as new base? Actually, I've try to do my own (unmodified) pcsxrr build with cygwin and I get:
badpotato@rorqual:~/pcsxrr-src$ make
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxBios.o PsxBios.c
PsxBios.c: In function `psxBios_strcat':
PsxBios.c:358: warning: null argument where non-null required (arg 1)
PsxBios.c:358: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strncat':
PsxBios.c:362: warning: null argument where non-null required (arg 1)
PsxBios.c:362: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strcmp':
PsxBios.c:369: warning: null argument where non-null required (arg 1)
PsxBios.c:369: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strncmp':
PsxBios.c:378: warning: null argument where non-null required (arg 1)
PsxBios.c:378: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strcpy':
PsxBios.c:382: warning: null argument where non-null required (arg 1)
PsxBios.c:382: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strncpy':
PsxBios.c:383: warning: null argument where non-null required (arg 1)
PsxBios.c:383: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strlen':
PsxBios.c:384: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_strpbrk':
PsxBios.c:428: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strspn':
PsxBios.c:436: warning: null argument where non-null required (arg 1)
PsxBios.c:436: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strcspn':
PsxBios.c:437: warning: null argument where non-null required (arg 1)
PsxBios.c:437: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_strstr':
PsxBios.c:451: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_bcopy':
PsxBios.c:461: warning: null argument where non-null required (arg 1)
PsxBios.c:461: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_bzero':
PsxBios.c:462: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_bcmp':
PsxBios.c:463: warning: null argument where non-null required (arg 1)
PsxBios.c:463: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_memcpy':
PsxBios.c:464: warning: null argument where non-null required (arg 1)
PsxBios.c:464: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_memset':
PsxBios.c:465: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_memmove':
PsxBios.c:466: warning: null argument where non-null required (arg 1)
PsxBios.c:466: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_memcmp':
PsxBios.c:467: warning: null argument where non-null required (arg 1)
PsxBios.c:467: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_printf':
PsxBios.c:546: warning: null argument where non-null required (arg 2)
PsxBios.c:600: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_Load':
PsxBios.c:619: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_open':
PsxBios.c:1250: warning: null argument where non-null required (arg 1)
PsxBios.c:1254: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_read':
PsxBios.c:1311: warning: null argument where non-null required (arg 1)
PsxBios.c:1312: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_write':
PsxBios.c:1352: warning: null argument where non-null required (arg 2)
PsxBios.c:1353: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios_firstfile':
PsxBios.c:1431: warning: null argument where non-null required (arg 2)
PsxBios.c:1434: warning: null argument where non-null required (arg 1)
PsxBios.c:1439: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios_delete':
PsxBios.c:1500: warning: null argument where non-null required (arg 1)
PsxBios.c:1504: warning: null argument where non-null required (arg 1)
PsxBios.c: In function `psxBios__card_write':
PsxBios.c:1551: warning: null argument where non-null required (arg 2)
PsxBios.c:1554: warning: null argument where non-null required (arg 2)
PsxBios.c: In function `psxBios__card_read':
PsxBios.c:1574: warning: null argument where non-null required (arg 1)
PsxBios.c:1576: warning: null argument where non-null required (arg 1)
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Gte.o Gte.c
Gte.c: In function `FNC_OVERFLOW1':
Gte.c:448: warning: integer constant is too large for "long" type
Gte.c: In function `FNC_OVERFLOW2':
Gte.c:455: warning: integer constant is too large for "long" type
Gte.c: In function `FNC_OVERFLOW3':
Gte.c:462: warning: integer constant is too large for "long" type
Gte.c: In function `FNC_OVERFLOW4':
Gte.c:469: warning: integer constant is too large for "long" type
Gte.c: In function `FlimG1':
Gte.c:534: warning: integer constant is too large for "long" type
Gte.c: In function `FlimG2':
Gte.c:542: warning: integer constant is too large for "long" type
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o CdRom.o CdRom.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxCounters.o PsxCounters.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxDma.o PsxDma.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o DisR3000A.o DisR3000A.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Spu.o Spu.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Sio.o Sio.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxHw.o PsxHw.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Mdec.o Mdec.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxMem.o PsxMem.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Misc.o Misc.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o plugins.o plugins.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Decode_XA.o Decode_XA.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o R3000A.o R3000A.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxInterpreter.o PsxInterpreter.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o PsxHLE.o PsxHLE.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o movie.o movie.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o cheat.o cheat.c
cheat.c: In function `PCSXRemoveCheat':
cheat.c:12: warning: unused variable `address'
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/WndMain.o Win32/WndMain.c
Win32/WndMain.c: In function `DlgMemPoke':
Win32/WndMain.c:1839: warning: control reaches end of non-void function
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/Plugin.o Win32/Plugin.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/ConfigurePlugins.o Win32/ConfigurePlugins.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/AboutDlg.o Win32/AboutDlg.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/memwatch.o Win32/memwatch.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/memsearch.o Win32/memsearch.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/memcheat.o Win32/memcheat.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/maphkeys.o Win32/maphkeys.c
gcc -Wall -O4 -fomit-frame-pointer -finline-functions -ffast-math -fno-exceptions -march=i686 -IWin32 -I. -D__WIN32__ -D__MINGW32__ -DPCSX_VERSION=\"1.5\" -D__i386__ -mwindows -mno-cygwin -c -o Win32/movie.o Win32/movie.c
Win32/movie.c:534:2: warning: no newline at end of file
windres Win32/pcsx.rc Win32/pcsxres.res
windres: Win32/pcsx.rc:278: syntax error
make: *** [Win32/pcsxres.o] Error 1
some clue to fix this?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
...yeah lurker can't even vote and the "view counter" of this thread is actually about ~13371. Thought I think that you should tell us a real raeson if your going to quit. Else, how about you apologize for this embarassing mistake and ask an (comprehensive) admin to delete these previous unnecessary post, uncancel and continue just like nothing happened?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
After some level I had to fastfoward... mainly because the level repetition getting boring. Thought I liked your run and I think you made a good job.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
abusing reset button... awesome :) also, are you going to collect all the music disc?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
no all letter? :( Thought this was nice run, yup.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
Congrualation!!! These rocket in wolf face was a good idea :) Now, look like that your stuck here, I even try myself to change disc with the designed hotkey, but it seem to crash everything. @DDRKhat : I had similar issue on some other playback... are you using deamon tool lite?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
Dooty wrote:
I was trying to TAS this one too, but due to desyncs I gave up, you did a great job Yes vote for you.
you should at least watching the entire movie before voting... this is simply a question to be fair toward other submission. Anyway, actually I manage to make it synch(was blocked at the wall too) by unchecking right/left|up/down... closing snes, then start it again and checking right/left|up/down, if that may help. The run was good, well performed.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
very cool TAS, the next level will probably getting harder and harder... I'm curious how far you'll be able to go with one player.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
It remember me an another html game in french. I don't know how hard you set up the game, but I love this kind of game. EDITH:
The mop is the key wrote:
YOU WON.
This wasn't bad, thought I was on page 3265, does there are different "winning" ending?
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
I would like to know how your going to fix the sound, I'm actually working on a psx game and this issue may been a big problem for me...
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
The end was definitly... ... ... yeah this was the best :) The lag counter about the "special effect" was quite impressive too, I think you have about 3000-4000 single frame input. I've never see such TAS like this.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
Progress... and tubed part16, part17, part18. Also, I here is some ram watch:
General:

!2567A X-Coordinate
!2567C Y-Coordinate
!2566E step counter
!6A4F8 potch


Inventory:

x6A4EA Slot1-Special
x6A4EB Slot2-Special
x6A4EC Slot3-Special
x6A4ED Slot4-Special
x6A4EE Slot5-Special

...

x6A4AE P1-S1-ItemDigit
x6A4AF P1-S1-QuantityMod
x6A4B0 P1-S2-ItemDigit
x6A4B1 P1-S2-QuantityMod
x6A4B2 P1-S3-ItemDigit
x6A4B3 P1-S3-QuantityMod
x6A4B4 P1-S4-ItemDigit
x6A4B5 P1-S4-QuantityMod
x6A4B6 P1-S5-ItemDigit
x6A4B7 P1-S5-QuantityMod
x6A4B8 P1-S6-ItemDigit
x6A4B9 P1-S6-QuantityMod

...

StoreHouse:
x6A97D P1-S1-ItemDigit
x6A97E P1-S1-QuantityMod
x6A97F P1-S2-ItemDigit
x6A980 P1-S2-QuantityMod


Dual

!12E198 HP-Riou
!12E2B8 HP-Flick


Aera A (Tenzan_Pass_1 - Mercenry_Forteress_Aera_1 - Sparrow_Pass_1)
!145BB6 Slot1-HP
!145C32 Slot2-HP
!145CAE Slot3-HP
!145D2A Slot4-HP
!145DA6 Slot5-HP
!145E22 Slot6-HP
!145E9E Slot7-HP
!145F1A Slot8-HP
!145F96 Slot9-HP
!146012 Slot10-HP
!14608E Slot11-HP
!14610A Slot12-HP
x17C44 EnemyItemDrop
x17C45 QuantityModDrop

Aera B (Kyaro_Highlander - Sparrow_Pass2(return) - Mercenry_Forteress_Aera_2 - Ryube_Forest)
!195BB6 Slot1-HP
!195C32 Slot2-HP
!195CAE Slot3-HP
!195D2A Slot4-HP
!195DA6 Slot5-HP
!195E22 Slot6-HP
!195E9E Slot7-HP
!195F1A Slot8-HP
!195F96 Slot9-HP
!196012 Slot10-HP
!19608E Slot11-HP
!19610A Slot12-HP
x2AD64 EnemyItemDrop
x2AD65 QuantityModDrop

Aera C (Kyaro_Aera - Muse_Aera_1)
145BB6 Slot1-HP
145C32 Slot2-HP
145CAE Slot3-HP
145D2A Slot4-HP
145DA6 Slot5-HP
145E22 Slot6-HP
145E9E Slot7-HP
145F1A Slot8-HP
145F96 Slot9-HP
146012 Slot10-HP
14608E Slot11-HP
14610A Slot12-HP
x2AD64 EnemyItemDrop
x2AD65 QuantityModDrop
Pay attention that these address will move if your party size is smaller than 6. Also, the enemy formation can be really confusing... but here is some example that should help: Sample1 & Sample2. Also, while loading new map/aera... lot of address about the battle sequence are moving to another one. This is very annoying to search for them... I'll probably complete the whole list about this later.... Anyone have an idea how the "storyline" event is stored in memory? If I can do my own path by using memory corruption to break some sequence... I'm sure that this could make the game a bit interresting.
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
Cool all those platform on the same emulator :) what is the command line to start a game?
mednafen.exe KrazyAceMiniatureGolf.lnx
I've many other command... but nothing seem launched :/
Experienced Forum User
Joined: 1/26/2009
Posts: 558
Location: Canada - Québec
pretty decent game, yes vote
1 2
17 18 19
22 23