0
0

[code:3lxijyhl]

4/10/06 4.04.33 – Dev release update

  • PS3 spu – Added SPURS mixer support. PS3 SPU version now non-beta!
  • PS3 spu – Added FMOD_DSP_TYPE_LOWPASS, FMOD_DSP_TYPE_ITLOWPASS,
    FMOD_DSP_TYPE_LOWPASS_SIMPLE, FMOD_DSP_TYPE_PARAMEQ,
    FMOD_DSP_TYPE_HIGHPASS effects.
  • Added – FMOD_ERR_MEMORY_CANTPOINT.
  • Event API – Added EventSystem::registerMemoryFSB / unregisterMemoryFSB.
  • Event API – Added EventProject::getNumEvents.
  • Event API – Added EventGroup::getParentGroup.

  • Fixed virtual voices swapping back to real and looping when they were
    supposed to be one shot.

  • Fix rare Sound::release crash if FMOD_NONBLOCKING is used.
  • PS3 spu beta – Fixed channelgroup volume level issue again.
  • Event API – Fixed loading crash introduced in v31.
  • Event API – Changed EventCategory::getInfo to return a global index
    if more than one project is loaded, instead of a local 0 based
    index.
  • Event API – Stopped EventSystem::getReverb crashing instead of returning
    FMOD_ERR_MEMORY if out of memory.
  • Event API – EventSystem::getEventBySystemID wasn’t respecting EVENT_INFOONLY,
    fixed.
  • Event API – Fixed projects not loading in v31 if max playbacks on events was
    > 63
  • Mac – Fix possible issue with loading plugins in OS X 10.3

  • FMOD_CREATECOMPRESSEDMEMSAMPLE flag changed to a more generic
    FMOD_OPENMEMORY_POINT, which supports .WAV and .FSB based PCM data now as well.
    To get the same behaviour as FMOD_CREATECOMPRESSEDMEMSAMPLE,
    (FMOD_CREATECOMPRESSEDSAMPLE | FMOD_OPENMEMORY_POINT) must be used.
    [/code:3lxijyhl]

This thread is for discussion / bugreports for the current release.
Download the current release from the front page at http://www.fmod.org

We are heading to 4.05.00 release now so no new stuff (of structural significance) will be added until all bugs are fixed in this branch.

  • You must to post comments
0
0

Hi, any specifics with the "Event API – Fixed loading crash introduced in v31" fix.

[EDIT] I did have a specific problem, but it turned out that the other programmers were using a different working directory folder and hadn’t copied across the latest dll’s (using v31 libs and v27 dll’s). They were getting the following error in case anyone else sees the same problem

Run-Time Check Failure #0 – The value of ESP was not properly saved across a function call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.