Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Programmers/modders only - let's work on a fix

12
Comment below rating threshold, click here to show it.

Velkorious

Senior Member

11-01-2011

I'm making this thread because the other one's gotten....kinda spammy, and it's hard to keep track of progress there,

DO NOT POST IN THIS THREAD UNLESS YOU HAVE SOMETHING TO CONTRIBUTE THAT MIGHT LEAD TO A FIX

If you post an "aww help my mac client no work" then you will just be wasting our time which we could actually spend creating a fix.

This thread is for constructive discussion only.


Comment below rating threshold, click here to show it.

Velkorious

Senior Member

11-01-2011

Anyway....to start off I've been comparing r3dlogs for previous games as well as these recent ones which fail and cause the error. They're located in:

Contents > Resources > Transgaming > c_drive > rads > solutions > lol_game_client_sln > releases > 0.0.0.XX > deploy > (logs sorted by date)

The following was taken form an earlier, working r3dlog. However, the post-Shyvana logs cut end right before the bold lines you see, so I'm guessing that's where the bug is.

The supposed problems involving "LoL_Audio_en_US.fev" are normal. It's only after this file is loaded that an error occurs.

Quote:

[snip]
00013.680| 139956.0000kb| 0.0000kb added| ERROR| RADS::API::Impl::FileUnmanaged::FileUnmanaged: The handle that was passed to the API has been either invalidated or closed.
000013.680| 139956.0000kb| 0.0000kb added| NONE| RADS::API::Impl::FileUnmanaged::FileUnmanaged: Failed to open "Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev".
000013.681| 139956.0000kb| 0.0000kb added| WARN| r3dFileImpl: Can't open Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev (from file C:\Perforce\LoL\__LIVE__\code\gameengine\Audio Manager\AudioManager.cpp)
000013.681| 139956.0000kb| 0.0000kb added| ERROR| MyFMODFileOpenCallback: Failed to open Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev
000013.681| 139956.0000kb| 0.0000kb added| ERROR| Manager::LoadEventFile(); attempting to load en_US\LoL_Audio_en_US.fev. FMOD 23, File not found.
000013.682| 139956.0000kb| 0.0000kb added| ALWAYS| FMOD: Couldn't find localized audio in localized folder, looking in top-level FMOD folder. This is not a problem unless the second attempt fails as well.
000013.819| 141616.0000kb| 1660.0000kb added| ALWAYS| LoLAudio::Load(): Successfully loaded default desired language locale: LoL_Audio_en_US.fev
000022.177| 176336.0000kb| 34720.0000kb added| ERROR| RADS::Common::CRT::fopen_s: No such file or directory
000022.195| 176340.0000kb| 4.0000kb added| ERROR| RADS::Common::CRT::fopen_s: ("levels\map2\scene\textures\wheel01.dds", "rb&quot failed: No such file or directory
000022.195| 176340.0000kb| 0.0000kb added| ERROR| RADS::API::Impl::FileUnmanaged::FileUnmanaged: The handle that was passed to the API has been either invalidated or closed.
000022.195| 176340.0000kb| 0.0000kb added| NONE| RADS::API::Impl::FileUnmanaged::FileUnmanaged: Failed to open "levels\map2\scene\textures\wheel01.dds".
000022.196| 176340.0000kb| 0.0000kb added| WARN| r3dFileImpl: Can't open levels\map2\scene\textures\wheel01.dds (from file C:\Perforce\LoL\__LIVE__\code\Eternity\source\Riot\Eternity\SimpleEnvironment\Material.cpp)
000022.196| 176340.0000kb| 0.0000kb added| WARN| r3dTexture EX: levels\map2\scene\textures\wheel01.dds - not found. Dummy texture created.
000024.857| 178108.0000kb| 1768.0000kb added| ERROR| RADS::API::Impl::FileManagedCompressed::Tell: Only supported when file is opened for binary access.
000024.861| 178112.0000kb| 4.0000kb added| ERROR| RADS::API::Impl::FileManagedCompressed::Seek: Only supported when file is opened for binary access.
000029.734| 187672.0000kb| 9560.0000kb added| WARN| GroupDefinition::Load - particle file data/particles/orderturretfire_cas.troy failed to load Persistent sound LoL_Audio/Spells/OdinGuardianSpellAttack/cast
000035.646| 200452.0000kb| 12780.0000kb added| WARN| GroupDefinition::Load - particle file data/particles/slimecall_tar.troy failed to load OnCreate sound LoL_Audio/Spells/WrathoftheAncients/OnMissileLaunch
000036.218| 201840.0000kb| 1388.0000kb added| WARN| GroupDefinition::Load - particle file data/particles/nashor_rune_buf.troy failed to load OnCreate sound LoL_Audio/Spells/ExaltedWithBaronNashor/buffactivate

[snip again - log continues to document the actual game]



As for the error itself:

The client is calling the function mbstowcs_s() in the file string_s.c. This function converts a MultiByte String TO a Wide Character String. (mbstowcs)

http://msdn.microsoft.com/en-us/library/eyktyxsx.aspx

errno_t mbstowcs_s(
size_t *pReturnValue,
wchar_t *wcstr,
size_t sizeInWords,
const char *mbstr,
size_t count
);

It seems that it's being passed an invalid multibyte string. For whatever reason, the mac client's files which would handle this function are hiccupping on it. Why this would happen on Transgaming's C Runtime Library and not the one used by the Windows client, idk.


Comment below rating threshold, click here to show it.

Xtasy

Senior Member

11-01-2011

Quote:
000005.470| 282748.0000kb| 7592.0000kb added| ALWAYS| FMOD: Attempting to load localized audio for en_US
000005.470| 282748.0000kb| 0.0000kb added| ERROR| RADS::Common::CRT::fopen_s: No such file or directory
000005.471| 282748.0000kb| 0.0000kb added| ERROR| RADS::Common::CRT::fopen_s: ("Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev", "rb&quot failed: No such file or directory
000005.471| 282748.0000kb| 0.0000kb added| ERROR| RADS::API::Impl::FileUnmanaged::FileUnmanaged: The handle that was passed to the API has been either invalidated or closed.
000005.471| 282748.0000kb| 0.0000kb added| NONE| RADS::API::Impl::FileUnmanaged::FileUnmanaged: Failed to open "Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev".
000005.471| 282748.0000kb| 0.0000kb added| WARN| r3dFileImpl: Can't open Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev (from file C:\Perforce\LoL\__LIVE__\code\gameengine\Audio Manager\AudioManager.cpp)
000005.471| 282748.0000kb| 0.0000kb added| ERROR| MyFMODFileOpenCallback: Failed to open Data/Sounds/FMOD/en_US\LoL_Audio_en_US.fev
000005.471| 282748.0000kb| 0.0000kb added| ERROR| Manager::LoadEventFile(); attempting to load en_US\LoL_Audio_en_US.fev. FMOD 23, File not found.
000005.472| 282748.0000kb| 0.0000kb added| ALWAYS| FMOD: Couldn't find localized audio in localized folder, looking in top-level FMOD folder. This is not a problem unless the second attempt fails as well.
000005.530| 284440.0000kb| 1692.0000kb added| ALWAYS| LoLAudio::Load(): Successfully loaded default desired language locale: LoL_Audio_en_US.fev


This was a r3dlog from today. It seems that it managed to locate the file on the second attempt.

EDIT: But there's nothing after this for me.


Comment below rating threshold, click here to show it.

Velkorious

Senior Member

11-01-2011

I'm actually curious if spectator mode is partly to blame.

I recall that Emissary saying the mac client had issues with spectator mode, and I wonder if it involved modifying some client files which would have caused errors like this one.

Same day, mac client breaks and also Riot begins public testing of spectator mode.


Comment below rating threshold, click here to show it.

Boompje

Senior Wrenchmen

11-01-2011

The problem is probably located within the Cider Wrapper files. I'll help and support more tomorrow. I'm braindead after 15 hours of searching..

EDIT:

The spectator mode isn't the problem. On EUW we had it toggled before, and it gave no troubles


Comment below rating threshold, click here to show it.

Xtasy

Senior Member

11-01-2011

I'd have to say we can't rely on r3dlogs.

I took a look at a r3dlog from yesterday. It contained the same errors you listed. However, it still proceeded towards a game, completely functional.

BUT THEN AGAIN.

I have a series of three r3dlogs after the patch. The first one had the same errors, but cut off. The second and third ones, both reached

PlayGame Started

and the logs just end.


Comment below rating threshold, click here to show it.

Broken Symmetry

Member

11-01-2011

There are tons of errors in the logs, the trick is to know which ones are unusual. Finding a C runtime error in the game logs won't happen though.

So far I've tried Cider version 6635 and 7119. 6635 crashes, 7119 doesn't crash at the runtime but has an other issue.

Also, from the hopelessly cluttered thread:

Quote:
Broken Symmetry:
Here is a very dirty workaround to the current issue with the LoL client.
It requires:
  1. Crossover Games 10
  2. Python 3.2
  3. adl from the Adobe AIR SDK
  4. Knowledge on how to use the Terminal and work with Python files
  5. Ability to read readme files

If anything of the above doesn't apply to you, don't even try to run the workaround. It will not work. I won't be around for the next ~22 hours, so unless you get it working right away, don't post on the forums about it. Seriously, don't. Any post that complains about failure that can be traced back to ignoring one of the above points might severely delay further releases and fixes.

Furthermore, note that running LoL under Crossover reduces the performance and can be unstable. Don't be surprised if it turns out to be unplayable.

The workaround basically replaces the Maestro process that keeps PVP.net and the client alive as well as launches the client and passes chat messages along.

Finally, the files: http://www.mediafire.com/?v1jmha3e8w5hk82

Enjoy.


Comment below rating threshold, click here to show it.

Velkorious

Senior Member

11-02-2011

Ran some tests on the US fontconfig file, to see if it is the source of any invalid characters. Doesn't seem like it. Even when I dragged it out of the client, I still got the error.

Also I'm curious that the error happens right after loading the LoL_Audio_en_US.fev - a file which is updated every patch. I wonder if it's the source of the offending string.


Comment below rating threshold, click here to show it.

Boompje

Senior Wrenchmen

11-02-2011

Quote:
Velkorious:
Ran some tests on the US fontconfig file, to see if it is the source of any invalid characters. Doesn't seem like it. Even when I dragged it out of the client, I still got the error.

Also I'm curious that the error happens right after loading the LoL_Audio_en_US.fev - a file which is updated every patch. I wonder if it's the source of the offending string.


I still have an unpatched client ( I hope you too ) .. where is that file located?


Comment below rating threshold, click here to show it.

Velkorious

Senior Member

11-02-2011

rads/projects/lol_game_client_xx_XX/managedfiles/0.0.0.40/DATA/Sounds/FMOD/

It's probably best to move both of the files in there, if you're gonna try it in the current client. It won't contain any Shyvana sounds though.


12