Jump to content
  • Wall of red text spam

    • 7.31.21 Released

    For the last week or so I've been getting a wall of red error text when I'm near laser lights or dance floors that are recieveing an audio in signal from a booxbox (tested various setups to see what would cause the errors at my base, does not cause an error if a dance floor or laser light is recieving a power in rather than an audio in) and I've encourtered the error a couple of times while just out and about around the map and even 1 time with no bases nearby.

    I changed no settings in my client since the start of wipe to cause this, I've verified integrity of game files, issue persisted. I've reinstalled rust, issue persisted. I've even clean installed rust by uninstalling via steam and deleting the rust folder from the steam directory before reinstalling and still have this issue, the clean install was performed on the 17th of July.




    Priority: Low Server: Scourge

    User Feedback

    Recommended Comments

    • Staff

    Noticed you can't read the red text on my screen due to poor quality so copied from the output_log.

    C:\buildslave\unity\build\Modules/Audio/Public/AudioSource.cpp(2134) : Error executing m_dryGroup->getWaveData(samples, numSamples, channelOffset) (An invalid parameter was passed to this function. )

    Link to comment
    Share on other sites

    Hi, I just wanted to share that I'm getting the same red writing. I've verified my game files many times and reinstalling my game seems to only fix it for a day then it pops back up. I'm sure its something that Facepunch needs to fix on their side of things but wanted to share so you know you're not alone.


    Link to comment
    Share on other sites

    • Staff

    I made a support ticket on the facepunch website a couple of days ago and have had the following response. 
    "-Go to "device manager" on Windows and update all audio drivers. 
    -Go to your Windows sound settings through control panel and disable all playback devices you're not using"
    Drivers were all up to date, disabled a couple of playback devices that were not being used like my monitor and this has fixed the issue.

    • Like 1
    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Status Definitions

    Pending = We are still working on this report.

    Working = The issue is currently being looked into by a developer.

    Fixed = The issue has been fixed and the resolution will be available in the next version.

    Released = The fix has been released and is now live.

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.