kozarovv
Developer
0x0E is accuracy command, correct value is memory offset. 0x11 is probably the same, but for COP2 (but here i'm not sure).@kozarovv i been thinking in something... maybe the netemu commands 0x0E, 0x11, and 0x13 could be... speeds ?
Are the commands marked in blue in the table here http://www.psdevwiki.com/ps3/Talk:PS2_Emulation
At least one of them... could be the "speed of the emulated optical drive", if this is true it makes sense for the command to allow to do a very fine adjustment of speed
Also... this speed varies a lot if the optical media is CD or DVD... maybe there is a command for each or some kind of identifyer (first byte of the value indicates "media type" ?)
What do you think ?
Anyway... incase this commands are not directly related with speeds of the optical drive (so part of this theory is wrong) i think could be related with the speeds or bandwiths of other components of the emulated PS2 machine (so maybe the other part of this theory could be right)
About 0x13: "config_cmd_0x13set(), set *0x1BDC790 to ((value2 <<32) | value3) Memory card related (timing? reported free space?), Value 2 seems to be always 0"
Netemu probably have command to set read speed, but can also have accurate speed as default, without option to change it. Good example for second option is game Shadow Man 2 : The Second Coming which require very accurate reads, but it work without any config on PS3. While OPL require accurate reads command, and pcsx2 is not able to get so accurate reads at all.