Page MenuHomeFeedback Tracker

Sound Distortion when starting engines in first person view on 1.46 RC branch
Assigned, WishlistPublic


I haven't tested every vehicle but when starting the engine of the T100 and civilian speed boat whilst in first person view, the engine sound is loudly distorted. This does not happen in third person view.


Legacy ID
Steps To Reproduce

Place an empty T100 and civilian speed boat in the editor.
Use first person view.
Get in the vehicles and start the engine.

Additional Information

Tested on vanilla - using Corsair Vengeance headphones.
This has just become an issue on 1.46 RC. Didn't happen in 1.44 stable.

Event Timeline

Bohemia edited Steps To Reproduce. (Show Details)Jun 3 2015, 7:18 PM
Bohemia edited Additional Information. (Show Details)
Bohemia set Category to Sound.
Bohemia set Reproducibility to Always.
Bohemia set Severity to None.
Bohemia set Resolution to Open.
Bohemia set Legacy ID to 1312092339.May 8 2016, 12:09 PM
Bohemia edited a custom field.

Always good thing to add is your sound system, so what headset/phones/speakers you use?

HOLY FREAKING SHIT when I tested this with my Logitech G930. Related to this stuff likely but it's freaking loud, thank god I wasn't wearing them on my ears

No weird sounds with good quality headphones. BIS really need to look this stuff because many people are using headsets.

I think that if this had been an issue before, I would have noticed it. You don't forget it in a hurry.

Adam added a comment.Jun 4 2015, 8:50 AM

Hey, i was unable to reproduce the issue. Could you, please provide more info? Thanks!

Happens also in helicopters.

My sound card is the Sound Blaster Omni, Headphones are Beyerdynamic DT 770 Pro.
When I set the sound card to stereo in the windows control panel the distortion isn't present. But when I configure it as 5.1 the problem occurs every time.

Adam added a comment.Jun 4 2015, 9:58 AM

Do you have soundcard by any chance?

Yes I have a soundcard - or did you mean alky_lee?

Adam added a comment.Jun 4 2015, 11:33 AM

We have managed to reproduce the issue and it is now shceduled for a fix. Thank you!

After todays fix in dev branch this has now been resolved. Quick work guys.