I know the Source engine doesn't like spaces or periods, but you can work around that by placing the variable containing them between quotation marks (like we have to do for the bone names in the *.qc). But the bat file Psycho-A put together for the SDK wraps the filepaths in quotes already, so that's not it. And the model compiles, so it's not the Source engine anyway.
This is frustrating.
The fact MooCHa has the issue on one PC but not another makes me think it's something external interfering with the Formatter. What, though? Is it hardware or software?
I'm still stumped on this. I fear you'll have to try all the obvious things. Move files, rename files, make sure none of the files are read-only or require admin rights, whatever. I'm not a programmer, I dunno how you're supposed to do this.
The Guest on MODDB that reported the same issue said not even the Poison Ivy example works for them. You could run that one to confirm that it is the Formatter, and not something with your projects. I assume it'll have the same issue on your end, because my guide just walks you through editing the *.qc to look like the Poison Ivy one.
The only time I've had wrong version display in game was when I used the actual Alien Swarm install and changed all paths as a last ditch attempt on this 5950x PC to test.
It is worth noting that I did a complete format and clean OS Win 10 Pro install and still had the same issue afterwards on this PC. It even had me thinking it was to do with me having a 16c/32t CPU at one stage. It still boggles me now.
One thing when mine didn't work. I had a host of games to choose from the dropdown rather than just the 2 options in Crowbar.
I don't know if this could be a reason here, but I remember bugs when path names got too long, and Psycho-A really used a file structure for the SDK that creates very long path names...
I don't know if this could be a reason here, but I remember bugs when path names got too long, and Psycho-A really used a file structure for the SDK that creates very long path names...
I have tested the exact same identical install paths on 2 separate rigs. I did that to try get working this one working I didn't plan on using my gaming rig at first, but I had no choice.
Others should still look at that, though. The issues could be unrelated.
In regards to that last post. I decided to try an SDK install on old MSI Gaming laptop I refurbished last year. Intel i7 7th Gen 4c/8t CPU with a 1060 on it.
I have set up the SDK with no issues on the latest RC of the UP. Not that that part matters, tbh. The file path naming schema is exactly like the 2 other PC's
The SDK Main menu pops up fine and I compiled Poison Ivy with no issues, instantly.
All great feedback and points! ilex I'll try and run through all those standard cases and see what happens. Wesp5 The pathfile length is one that popped into my head as well since I've run into it on github/sourcetree and SVN too. I tend to go for verbose path names but it bites me in the butt later down the line, so it very well could be that in this case as well.
MooCHa appreciate you running this down on multiple machines, that's a lot of work!
If I do end up getting it working, then I'll make sure to post whatever the issue was here so we can help future people as well.
All great feedback and points! ilex I'll try and run through all those standard cases and see what happens. Wesp5 The pathfile length is one that popped into my head as well since I've run into it on github/sourcetree and SVN too. I tend to go for verbose path names but it bites me in the butt later down the line, so it very well could be that in this case as well.
MooCHa appreciate you running this down on multiple machines, that's a lot of work!
If I do end up getting it working, then I'll make sure to post whatever the issue was here so we can help future people as well.
Please do let us know.
I can say all systems tried on my end have been tried with new OS install Win 10 pro and 1 try prior(my culprit) on a 22/23 month install of same OS. Same result.
I'm wondering what CPU, GPU, Mobo that you have? I'm just pissing in the wind at this point.
The issues I had here with stuff not compiling did come down to being hardware which wa indeed the CPU being 16c / 32t
The temp workaround for me has been through testing and giving feedback to SDK author is that we arrived at this
Type msconfig into Windows Run program or Search bar. Choose Boot tab page, click Advanced options... Check box - Number of processors: and from drop list, I chose 31 then reboot.
All of my issues with compiling and SDK menu issues with it not loading to select Crowbar hasdisappeared. You will only lose 1 thread and still have 16 cores so not a lot of loss.
If 31 doesn't work for you then start from 16 and proceed in 4's upwards. You need to uncheck the box and reboot then set the value again to change it and do another reboot if you want a higher number than that you previously selected.
I have never encountered such an issue and I did too many experiments with this tool to count. But if it is a path related issue somehow, we have a tool that can edit most stuff about a MDL file, so you should be able to correct small mistakes like that. Its name escapes me at the moment, I am not at home yet so I can't even check what it was called. It is a tool I found and asked Wesp5 to include, because it was really useful to me. All I can recall is that it has a green icon, I think.
I have never encountered such an issue and I did too many experiments with this tool to count. But if it is a path related issue somehow, we have a tool that can edit most stuff about a MDL file, so you should be able to correct small mistakes like that. Its name escapes me at the moment, I am not at home yet so I can't even check what it was called. It is a tool I found and asked Wesp5 to include, because it was really useful to me. All I can recall is that it has a green icon, I think.
My issues fully resolved with doing what I said in my last post after going through a bunch of stuff in another thread here with Psycho-A .
If you have a 16c/32t CPU please test it.
The path issue in my case can arise if you don't click CrowVtmb from sdk menu(SDK Menu doesn't launch/ work unless use fix in last post for me at least on my 5950x). It can also happen if you click CroVtmb.exe instead of Launcher.bat in crowbar folder in SDK tools regardless. The SDK Launcher menu points to the .bat.
Social Media