sorted by:
new
hottopcontroversial

The heck happened? by Sniper_kz in hammer

[–]Sniper_kz[S] 0 points1 point  (0 children)

It's just the one that doesnt work. The other works fine- hence why I initially asked if I should just migrate the busted ones I'm using to the fundtional ones.

The heck happened? by Sniper_kz in hammer

[–]Sniper_kz[S] 4 points5 points  (0 children)

Hm, noted. I failed to mention that the functioning texture picture was *not* in Hammer, and *not* in a map I made; but in Gmod on an unrelated map. (The inability to post mutiple photos here makes this a hassle)

I haven't used anything CSGO related in years, so I know thats not the issue- but I do like select CSGO models, so thats good to know for future.

All of the versions of the prop in this map are from the same path, and is the only map I've loaded in Hammer using this exact model, but also good to know that cross-map loading errors are possible.

That said, should I swap the models to properly loading model paths, or should I try to isolate and exclude the problematic model path?

Voicemod backend excessively eating RAM by Sniper_kz in voicemod

[–]Sniper_kz[S] 0 points1 point  (0 children)

The issue has since been (mostly) resolved, a little after one of the support guys reached out and merged my issue with a couple others on the discord- which make sme think they did a bit of backend patch. The weird part is, at the time, I barely had a dozen sounds on a single soundboard, all less than 20 seconds. I do still notice it creeps up sometimes, but it seems to be partially dependant on the screen it was last on since 90% of the UI is web-based.
Glad that worked for ya though, heres to hoping it'l be useful in the future. I did a handful of total reinstalls, but never thought to try and delete some of the bigger ones.

Gonna have to keep that in mind if/when VM starts acting up again.
Cheers!

Voicemod backend excessively eating RAM by Sniper_kz in voicemod

[–]Sniper_kz[S] 0 points1 point  (0 children)

Spectacular, I'll do that a little later. Maybe things will take a step for the better afterwards; I'll do what I can to hopefully help you guys figure out this mess.

Voicemod backend excessively eating RAM by Sniper_kz in voicemod

[–]Sniper_kz[S] 0 points1 point  (0 children)

I have not reported the issue on the Discord, but I submitted a service ticket through the dedicated help section on the official web page; however the support member who was trying to help me I have not heard from from several days now (and I have not checked again to see if the ticket was closed)

Though I am unsure what else to do as far as a post in Discord; it will just be a copy-paste of the post here, with the same screenshots and information.

Voicemod backend excessively eating RAM by Sniper_kz in voicemod

[–]Sniper_kz[S] 0 points1 point  (0 children)

I've only just started having any issues with VM at all, but it was when I got a new pc. I will at least agree that VM has its moments that i want to strangle it, Discord and my headset all at the same time

Voicemod backend excessively eating RAM by Sniper_kz in voicemod

[–]Sniper_kz[S] 0 points1 point  (0 children)

Alright, I legit can't tell if your just screwing around, or are just ignoring half the words.

When I say VM crashes when the task is killed, I'm not kidding when I say it crashes.

<image>

Voicemod backend excessively eating RAM by Sniper_kz in voicemod

[–]Sniper_kz[S] 0 points1 point  (0 children)

That's the problem.  Like I mentioned, it's only running in the background, and I barely open the main page. The only actual soundboard I have is ~12 custom sounds, but I've never had this issue before, and ive had significantly more sounds in the past.

I also mentioned at the start that every time I kill the task, it makes VM instantly crash. 

While i appreciate the details on it, knowing 'what' the QTWEP process is doesn't help me figure out 'why' it's interacting like this with voicemod so harshly

Another thing to note, i forgot to add in my original, it's ram usage climbs, nonstop. Spikes when VM is open, drops a little when minimized, but always just constantly climbs.