EmuNewz Network

Full Version: Star Ocean : The Last Hope - International
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Tested using latest commit on 18 February 2014 : 22558df68e0fc2648c53c60ffde8858ed086922e

The emulator doesn't crash, and displays the following error (seems looping forever) :
Code:
PPU[1] Thread (CPUThread)[0x00d9f034]]: sys_fs error: "/aska0000.bin" not found! flags: 0x00000000

A particular note, this aska0000.bin file is a 23.3 Gb file inside PS3_GAME/USRDIR.
Log file is attached.
[attachment=15730]
Sometimes you have to force the emu/game to find certain files. Go to config -> virtual file system manager and add "PS3_GAME/USRDIR" to the root "/" (will break other games though), or just copy the file there, symlink it, or whatever. It should be found then. Some other games also require you to do this, Disagea 4 for instance (I think)
(02-18-2014, 05:01 PM)ssshadow Wrote: [ -> ]Sometimes you have to force the emu/game to find certain files. Go to config -> virtual file system manager and add "PS3_GAME/USRDIR" to the root "/" (will break other games though), or just copy the file there, symlink it, or whatever. It should be found then. Some other games also require you to do this, Disagea 4 for instance (I think)

Oh I see.. but if the emulator is already mature enough, this kind of workaround won't be needed anymore, will it ?
Or perhaps this workaround will always be needed ?
It is probably an emulator bug. It should be fixed eventually, but there are more important things for now I guess.
An update for this game using rev : 4770e5af084b8e9d3d2a0b8bdc99984e8beac8e8
The emulator doesn't crash, and stopped at this instruction right after opening the 23.3Gb file.
We still need to add PS3Game/USRDIR manually to root folder using VFS to load this file though ..

Code:
[W : PPU[1] Thread (CPUThread)[0x00d9f034]]: *** cellFsOpen(path="/aska0000.bin"): fd = 56
[E : PPU[1] Thread (CPUThread)[0x00d9f004]]: TODO: cellFsReadWithOffset
Update for this game using latest revision : fb1b57720c124f22d3d8148df61e6df5a64aba04
After Alex implemented cellFsReadWithOffset, this game now shows Debug Console related to Atrac.
Code:
Multistream: atrac failed to load -2147418106

Btw, we still need to map PS3GAME/USRDIR manually in Virtual File Manager ..
Log is attached here while waiting for Dante to merge the update.
[attachment=15916]
Latest revision(0e437312adb1b02c9e04292c1ba51f5d58acceed) caused this error even though I've mapped the USRDIR in virtual file manager.
Code:
[E : PPU[1] Thread (CPUThread)[0x00d9f034]]: sys_fs error: "/dev_hdd0/game/MRTC00001/USRDIR/aska0000.bin" not found! flags: 0x00000000
Previously, if we map the folder USRDIR under "/" path, this issue will be solved. But the latest revision requires us to map the USRDIR folder into /dev_hdd0/game/MRTC00001/USRDIR.

And then, we also need the file flashATRAC.pic in dev_flash folder.
Here is the few lines after loading the flashATRAC file.
Code:
[W : PPU[1] Thread (CPUThread)[0x00d9f034]]: *** cellFsOpen(path="/dev_flash/sys/external/flashATRAC.pic"): fd = 81
[W : PPU[1] Thread (CPUThread)[0x00d9f01c]]: sys_fs warning: cellFsClose(fd=81)
[E : PPU[1] Thread (CPUThread)[0x00ff3250]]: TODO: _cellSpursSendSignal
[E : PPU[1] Thread (CPUThread)[0x00ff3094]]: TODO: cellSpursEventFlagWait
[E : PPU[1] Thread (CPUThread)[0x00ff3250]]: TODO: _cellSpursSendSignal
[E : PPU[1] Thread (CPUThread)[0x00ff3094]]: TODO: cellSpursEventFlagWait
[W : PPU[1] Thread (CPUThread)[0x0003c300]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x311912d0, attr_addr=0xd0020900, initial_count=0, max_count=2147483647)
[W : PPU[1] Thread (CPUThread)[0x0003c300]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x3119134c, attr_addr=0xd0020900, initial_count=0, max_count=2147483647)
[W : PPU[1] Thread (CPUThread)[0x0003c300]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x311913c8, attr_addr=0xd0020900, initial_count=0, max_count=2147483647)
[W : PPU[1] Thread (CPUThread)[0x0003c300]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x31191444, attr_addr=0xd0020900, initial_count=0, max_count=2147483647)
[W : PPU[1] Thread (CPUThread)[0x0003c300]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x311914c0, attr_addr=0xd0020900, initial_count=0, max_count=2147483647)
[W : PPU[1] Thread (CPUThread)[0x0003c300]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x3122aac0, attr_addr=0xd0020910, initial_count=0, max_count=2147483647)
[W : PPU[1] Thread (CPUThread)[0x00ff7004]]: cellAudio warning: cellAudioInit()
[! : Audio Thread]: Audio started
[W : PPU[1] Thread (CPUThread)[0x00ff7034]]: cellAudio warning: cellAudioPortOpen(audioParam_addr=0xd0020970, portNum_addr=0x3122aad0)
[W : PPU[1] Thread (CPUThread)[0x00ff7034]]: cellAudio warning: *** audio port opened(nChannel=8, nBlock=8, attr=0x0, level=0.000000): port = 0
[W : PPU[1] Thread (CPUThread)[0x00ff7010]]: cellAudio warning: cellAudioGetPortConfig(portNum=0x0, portConfig_addr=0xd0020990)
[W : PPU[1] Thread (CPUThread)[0x0003c444]]: sys_semaphore warning: sys_semaphore_create(sem_addr=0x3122ab28, attr_addr=0xd0020960, initial_count=0, max_count=1)
[E : Audio Thread]: alcOpenDevice: OpenALC error 0xa001
[E : Audio Thread]: alcCreateContext: OpenALC error 0xa001
[E : Audio Thread]: alcMakeContextCurrent: OpenALC error 0xa001
[W : Audio Thread]: Audio aborted
[! : RSXThread]: RSX thread exit...
[!]: Closing memory...
Do any of u guys ever come across this error message ?
Code:
[E : Audio Thread]: alcOpenDevice: OpenALC error 0xa001
[E : Audio Thread]: alcCreateContext: OpenALC error 0xa001
[E : Audio Thread]: alcMakeContextCurrent: OpenALC error 0xa001

So many revisions and yet this error still persists..
is it a misconfiguration from my side ? Undecided
(04-03-2014, 05:01 AM)tr4nquility Wrote: [ -> ]Do any of u guys ever come across this error message ?
Code:
[E : Audio Thread]: alcOpenDevice: OpenALC error 0xa001
[E : Audio Thread]: alcCreateContext: OpenALC error 0xa001
[E : Audio Thread]: alcMakeContextCurrent: OpenALC error 0xa001

So many revisions and yet this error still persists..
is it a misconfiguration from my side ? Undecided

Might be a problem on your end - OpenAL isn't initializing properly (0xa001 = invalid [audio] device). Check your sound card settings or try just using null audio instead of OpenAL.
Pages: 1 2