My texture can't be found on my disk?

[SunnyGoLucky]

So i'm working on bringing a custom model into SFM and the thing only uses one texture. Thing is, both the VMT and VTF are on the same folder (so the directory would be "materials/models/(model)/(texture).vtf/vmt) and yet, I get an error in console saying that it "can't be found on disk". Funnier (or not) is that the texture goes on just fine if a $basetexture string attribute is added manually.

I have no clue what's going on so if someone could help explain how to fix this problem, i'd appreciate it.

[ZergSquad]

post your QC here ?

and your texture vmt and vtf filename :)

[SunnyGoLucky]

Originally posted by ZergSquad:

post your QC here ?

https://i.imgur.com/zUaUTev.png
here it is.

[Zappy]

Please reboot Source Filmmaker, make a new session (without loading a map), click "Windows" > "Console" at the top-left of Source Filmmaker's main window, click on the "Clear" button at the bottom-right of the console, open the model browser, select the model in question, click "Open" to place it into the session, select all of the text now in the console, press Ctrl+C to copy that, and paste it in a comment here (preferably between [code] and [/code]).


In addition to that, please copy the entirety of the model's QC file, and paste that here too (also preferably between [code] and [/code]).

And also do the same with the model's VMT file(s).

[SunnyGoLucky]

Originally posted by Zappy:

Please reboot Source Filmmaker, make a new session (without loading a map), click "Windows" > "Console" at the top-left of Source Filmmaker's main window, click on the "Clear" button at the bottom-right of the console, open the model browser, select the model in question, click "Open" to place it into the session, select all of the text now in the console, press Ctrl+C to copy that, and paste it in a comment here (preferably between [code] and [/code]).


In addition to that, please copy the entirety of the model's QC file, and paste that here too (also preferably between [code] and [/code]).

And also do the same with the model's VMT file(s).

Ok so the model's QC looks like this:

$modelname "sunny\memcake\squidmem.mdl"
$cdmaterials "models\sunny\memcake"

$scale 5
$body memcake "squidmem.dmx"
$sequence idle "squidmem.dmx"

As for the console thing, opening the model up for the first time displays this:

Binding unchaced material "potterywheelpanelframe", artificially incrementing refcount
"materials/models/sunny/memcake/squidmem.vtf": can't be found on disk

Originally posted by ZergSquad:

and your texture vmt and vtf filename :)

both the vtf and vmt's filenames are "squidmem"

[Zappy]

Originally posted by SunnyGoLucky:

Ok so the model's QC looks like this: - As for the console thing, -

What about the contents of the VMT file(s)?

[SunnyGoLucky]

Originally posted by Zappy:

Originally posted by SunnyGoLucky:

Ok so the model's QC looks like this: - As for the console thing, -

What about the contents of the VMT file(s)?

"VertexlitGeneric"
{
	"$basetexture" "models\sunny\memcake\squidmem.vtf"
}

there's only one and that all there is in it

[Zappy]

Originally posted by SunnyGoLucky:

- there's only one and that all there is in it

What happens if you replace the back-slashes ( \ ) with front-slashes ( / ), and get rid of the ".vtf" extension at the end? As in, what happens if you replace...

	"$basetexture" "models\sunny\memcake\squidmem.vtf"

...with the below?

	"$basetexture" "models/sunny/memcake/squidmem"

[SunnyGoLucky]

Originally posted by Zappy:

Originally posted by SunnyGoLucky:

- there's only one and that all there is in it

What happens if you replace the back-slashes ( \ ) with front-slashes ( / ), and get rid of the ".vtf" extension at the end? As in, what happens if you replace...

	"$basetexture" "models\sunny\memcake\squidmem.vtf"

...with the below?

	"$basetexture" "models/sunny/memcake/squidmem"

tried it. It gave me the same disk error in console that i posted above

[Zappy]

Originally posted by SunnyGoLucky:

tried it. It gave me the same disk error in console that i posted above

Please show me 2 screenshots of Source Filmmaker. Make sure that both the model and the rest of Source Filmmaker's interface are visible.

- The first screenshot should be in a new session, where you've just spawned the model, with it looking untextured.
- The second screenshot should be in the same setting, but after you've added override materials to the model, pointed $BaseTexture at the VTF there, with the model looking textured. Make sure that the override material in the Element Viewer is visible in this screenshot.

[SunnyGoLucky]

Originally posted by Zappy:

Please show me 2 screenshots of Source Filmmaker. Make sure that both the model and the rest of Source Filmmaker's interface are visible.

- The first screenshot should be in a new session, where you've just spawned the model, with it looking untextured.
- The second screenshot should be in the same setting, but after you've added override materials to the model, pointed $BaseTexture at the VTF there, with the model looking textured. Make sure that the override material in the Element Viewer is visible in this screenshot.

Hopefully i didn't misread anything but here they are.
Before the OM/$basetexture:
https://i.imgur.com/XUOazXp.png
After the OM/$basetexture:
https://i.imgur.com/9cRQEJt.png

[Zappy]

Originally posted by SunnyGoLucky:

Hopefully i didn't misread anything but here they are. -Images-

This implies that something stupid is going on.

Please change the VMT file to...

VertexlitGeneric
{
	$BaseTexture "models/sunny/memcake/squidmem"
	$Alpha 0.2
}

...then reboot Source Filmmaker, load the model, and check if it's translucent now.

If it's still opaque, not translucent, then like it or not, you've been editing the wrong VMT, with an identically-named VMT file being in a higher-priority search path, overriding your changes to the one in a lower-priority search path.

[SunnyGoLucky]

Originally posted by Zappy:

This implies that something stupid is going on.
If it's still opaque, not translucent, then like it or not, you've been editing the wrong VMT, with an identically-named VMT file being in a higher-priority search path, overriding your changes to the one in a lower-priority search path.

Well I tried and it did nothing. Also how would I have an identically named one if the squidmem VMT is the only VMT I have named that way?

[Zappy]

Originally posted by SunnyGoLucky:

Well I tried and it did nothing. -

The good news is that you haven't been doing something wrong with the VMT that you were editing, then.

The bad news is that you have a rogue "evil doppelganger" of that VMT somewhere.

The other good news is that you can find out where that "evil doppelganger" VMT is.



Please do all of the following:

- Save the session if you want to keep it, as the below can be a bit unstable/crash-pone
- Right-click a shot in the Clip Editor, and choose "Edit Clip" > "Set Clip Overlay"
- Make sure that the drop-down "Mod Filter" selection list at the top is set to "All Mods
- Make sure that the folder filter below that is set to "VMT Files" (so that it doesn't limit it to any given folder)
- Type or copy-paste "models\sunny\memcake\squidmem.vmt" (without quotes) into the search string "Filter" below the "Full Path"
- Wait for the VMT to show up below the folder filter, and then select the VMT
- Double-click the "Full Path", and press Ctrl+C to copy that*
- Open your VMT editor of choice, click "File" > "Open..." or such in it, press Ctrl+V to paste the full path that you copied*, and press Enter to open it or such.

You should now have the appropriate VMT file open, the one that Source Filmmaker reads. You may now either edit this VMT, or delete this VMT to (hopefully) make Source Filmmaker read from the other VMT that you were editing.



* Unfortunately, the material browser used for the shot overlay picker is very picky about what you can and can't do outside it.
If you seem unable to copy the "Full Path", just close the material browser, reboot Source Filmmaker, and try again, this time making sure to not click on anything outside of the material browser (not even this forum thread/comment) until you have copied the "Full Path" of the VMT.

[SunnyGoLucky]

Originally posted by Zappy:

The good news is that you haven't been doing something wrong with the VMT that you were editing, then.

The bad news is that you have a rogue "evil doppelganger" of that VMT somewhere.

The other good news is that you can find out where that "evil doppelganger" VMT is.

Well I did all that and then once I went to open the vmt, i was given this:
https://i.imgur.com/7XkNg3z.png

[Zappy]

Originally posted by SunnyGoLucky:

Well I did all that and then once I went to open the vmt, i was given this: -Image-

Oops. Put a double-quote mark ( " ) on both the left and the right side of the path, then try again.