Are you sure you are naming the custom lock sound correctly (LockChime.wav, case sensitive) on the USB drive and in the root folder? And it might be helpful switching to a standard and then to the custom again after you do that. Another reason for the file to be rejected might be that it exceeds 4mb.
List of software bugs
- Thread starter K.I.T.T.
- Start date
i've tried just about everything: LockChime.wav, lockchime.wav. i've switched it off then on, used a different USB drive, did a power cycle, and it definitely is not over 4MB because I’ve tried many different sounds all under 1MB.
Out of curiosity, when you download the audio file, what format does it download in? It may have something to do with that. For example, if it downloads in a .mp3 format, but you just rename it to a .wav format, then it may be that the car is still seeing it as .mp3.
i haven’t considered that only because i downloaded all of the sounds from the NATA website, so i assumed they are already in the correct format.
I would definitely check. Maybe try downloading it to a PC first to check the file format, and then putting it on a USB from there.
Well, wait... just renaming won't do any good: 100% the file will not be recognized as an uncompressed wave form, which is the only format allowed. If a mp3 or any other format than wav was downloaded, it must be converted to .wav, otherwise it will be simply unreadable by the car application.
You're correct! If you download the file, and it downloads as anything other than a .wav format, then it has to be put through a program that will convert it to a .wav format. Otherwise, the car won't recognize the file and ignore it entirely. You can usually check the file format it is in by checking the properties of the file. On Windows, you can do this by simply right-clicking the file and then clicking on properties and then going to the details tab and scrolling down to find the file type. However, I wouldn't know how to do this on any other platform like IOS, macOS, Android, or others.
Would be interesting if there was a toggle for this in FSD. For ex. bi-directional green light reading when in the middle/start of an intersection. Or the ability to only turn if the distance from my car to the oncoming car is minimum feet/some criteria.
I think, there is a major bug in street recognition:
At least in Germany there are often " islands" in the middle of the street.
- at the edge of a village to slow down traffic (outside you may go 100km/h, inside village 50km/h)
- In the town as guard for passants when crossing a busy street
The SW NEVER shows them. Did not experience a direct hit, but in AP it doesn't slow down and comes very near - like ' ups, didn't see it'
At least in Germany there are often " islands" in the middle of the street.
- at the edge of a village to slow down traffic (outside you may go 100km/h, inside village 50km/h)
- In the town as guard for passants when crossing a busy street
The SW NEVER shows them. Did not experience a direct hit, but in AP it doesn't slow down and comes very near - like ' ups, didn't see it'
Last edited:
Is it only me or do have others this problem too:
When I want to enter a voice command to the navigation, it finds the most complicated streets. But it NEVER finds a favorite- like 'home address' or 'franklin' ( name of a stored address)
When I want to enter a voice command to the navigation, it finds the most complicated streets. But it NEVER finds a favorite- like 'home address' or 'franklin' ( name of a stored address)
I don't think that is a bug, just lack of a feature. It doesn't recognized saved addresses in your favorites when you name them.
Redundant green vertical bar on charge screen cause new charging station image is already on main display while the phone app needs a tiny charger station.
Grok response latency needs to be shorter and spotty connection while using phone hotspot causing too many silence pauses.