like i said gave chatgpt the code and it fixed it.// Attach once on spawn
public class PetSfx : MonoBehaviour
{
[EventRef] public string IdleEvent;
StudioEventEmitter _idle;
public static void RateLimitedOneShot(string eventPath, Vector3 pos)
{
var now = Time.unscaledTime;
var key = eventPath;
var state = Gate.TryGetValue(key, out var s) ? s : (0f, 0);
if ((now - state.lastTime) < MinInterval || state.active >= MaxInstances)
return;
state.lastTime = now;
state.active++;
Gate[key] = state;
var inst = RuntimeManager.CreateInstance(eventPath);
inst.set3DAttributes(RuntimeUtils.To3DAttributes(pos));
inst.start();
inst.release(); // schedules release after playback
// decrement active a moment later
RuntimeManager.StudioSystem.scheduleDSP(0, 0); // or use a callback to decrement on STOPPED
Yes, because ChatGPT is all knowing and knows LEâs code and what is causing the issue. Tell me youâre not a programmer without telling me youâre not a programmer.
Itâs not a general issue that happens with everyone. Itâs a specific issue that happens with a few people. That means itâs related to something theyâre doing with the system sound that is having issues with your system.
Best way to fix it is to send bug reports, not be passive aggressive. And certainly not trusting that ChatGPT knows how to fix code it isnât even aware of.
yeah actually i am> thanks though. Ive been at their chops with this fix since alpha launch 4 years ago. ive done nothing but send bug reports. they wont acknowledge it at all. itâs been a problem for 4 years yet they wont fix it
Itâs always coding. But itâs also always the system.
If this was an issue that everyone had (like the stash issues), then you could say itâs just coding. But this is an issue that only happens to a few people. The majority of people donât have this issue and never had.
So itâs likely simply some obscure interaction that is hard to pinpoint and/or debug. If youâre a developer you should be aware of that. Sometimes issues only happen on a few clients for some obscure reason.
Quite a common occurrence when you have such a wide variety of hardware/software/drivers all affecting your code.
4 different pc"s? with 100k more in forums lol? not the pc. itâs coding. like i said 4 different pcâs in the house 2 all amd and 2 all intel. all of them have this problem. itâs coding and iâve said that and sent to them multiple time with coding to correct it. so if they all of sudden decide to use it after 4 years it will be amazing
Since you likely installed them all, you likely installed them similarly. It could even be some software issue that is causing it because of something you installed.
Yes, more people have this bug in the game than there are people playing.
Most people donât have this bug. In fact, there hasnât been a thread about it for a long time. So it clearly canât affect that many people.
It seems to be more prevalent this season, so itâs likely something they changed. Some of it seems to be related to MTX (so not related to your issue at all, because that was happening since before them).
So yes, if it were simply coding, then everyone would be having this issue. When it clearly isnât true.
Itâs the way the code is executed which isnât sitting right with a few computers for some reason.
Which doesnât mean itâs not on them to fix it. Because it is. But these issues are notoriously hard to figure out.
I once had a game that blue screened my pc constantly. It was the only game that did this. I eventually got lucky and figured out that it was a multi-usb hub that was causing it and it stopped happening when connected to a different USB port.
Was it the devs fault or the coding that they didnât predict this situation?
Youâre just angry and wanting to lash out, but that doesnât make you right.
look at the forums. thereâs 100k+ having this problem ive done all there âfixesâ along with all the other people in forums. I know how computers work and how to remedy common problems. this does not do it. again itâs coding. if this many problem are having this problem it;'s a big deal. but LE wont comment on it nor will they put it in their common bugs known in their page
There arenât even 100k people in the forums altogether, let alone with this problem.
This issue was almost never reported before this season. The issues from this season donât seem to be the same ones you have. There are at most a few dozen reporting it this season and they all seem to be related to pet MTX.
Before this season, I canât find a single complaint about this issue since launch.
So maybe you should be the one looking at the forums more closely.
Again, I can understand youâre frustrated. Itâs annoying to want to play a game and not be able to. But being hugely hyperbolic and passive aggressive doesnât really help your case.
No, I didnât look for something that no one has complained in 2 years. If people complained about it 4 years ago and they donât complain about it now, that means theyâre not having this issue anymore (or they left).
It also means that barely anyone (if any) of the 250k players at launch had this issue, because some would complain about it.
So no, you definitely canât say that 100k+ players have this issue without sounding extremely hyperbolic. Especially when there arenât even 100k players playing this season. Itâs like saying that 20 billion people on this planet have webbed fingers.
I did look. I searched for sound bug and sound issues and there isnât a single mention of your problem since the 1.0 launch. I didnât bother looking further back because itâs not relevant. If no one complains about something like this for 2 years, then itâs not a global issue.
As I said, there are only complaints this season and theyâre related to pet MTX. No one else seems to have your issue since the launch.
I think itâs you that actually didnât look and didnât realize that youâre the only one with this problem.
You seem to have some reading or comprehension issues.
I said I looked as far back as the game launch last year. Because a bug that hasnât been complained about in 2 years isnât a bug that people are having. This is bug that only you are having and maybe a dozen other people.
Does that help to understand? A 2021 thread about a single person having an issue isnât relevant. And it certainly is very very far from â100k+â.
As I said before, youâre angry and frustrated and so youâre being hyperbolic and a drama queen. Honestly, your attitude makes it very hard to sympathize with your issue.
game has been out in alpha since 2021 like i said. it seems like you cant comprehend what you read. first comment said that. if you have trouble with comprehension my wife is a 3rd grade teacher certified in reading and comprehension. i can get you free lessons. seems like you need them
Yes, itâs been out since 2021. And it also had a lot of bugs that have never happened since, or happened only to a couple of people.
It doesnât change the fact that the problem you have is something that is happening to only you and no one else has complained about it in more than 2 years.
Also, the post you linked doesnât seem to have anything to do with your issue. That link is about LE assuming a different sound source when you have monitors with speakers and thus having no sound. There was nothing there about it crashing every 20 minutes like you have.
So not even that post is relevant for your very specific issue that no one else seems to have.
Or, maybe your issue is simply the same everyone else is having this season alone, and that didnât have it in the previous seasons, and itâs related to the pet MTX bug. Which is solved by unequipping the pet.
Either way, itâs not a âlong standing bug that 100k+ people haveâ. Whichever way you want to slice it, youâre not right about this.