Vtex troubleshooting: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (Error loading texture ( pfm ))
(Redirected page to Vtex (Source 1)#Troubleshooting)
Tag: New redirect
Line 1: Line 1:
The following is a list of errors and problems that can occur while using [[Vtex (Source 1)|Vtex]].
#REDIRECT[[Vtex (Source 1)#Troubleshooting]]
 
When listing a new error here, please follow the established format.
 
== Local Steam Service is not running ==
Vtex will give the following error:
 
SteamStartup() failed: SteamStartup(0xf,0x0012F0E4) failed with error 108: The local Steam Service is not running
 
Steam must run while Vtex is run. Start Steam to fix this.
 
== Problem figuring out outputdir ==
 
Vtex will give the following error:
 
Problem figuring out outputdir for <path>
 
As a first step, check that the texture to convert is really in the <code>\sourcesdk_content\gamedir\materialsrc</code> folder, where ''gamedir'' is the game folder (<code>cstrike</code>/<code>dod</code>/<code>hl2</code>/<code>hl2mp</code>).
 
If the texture is in the correct folder, the error might instead be caused by a complication with the environment variables. Primarily, this should be able to be eliminated by using [[VConfig]] and ensuring the selected mod has been run at least once. However, there are cases where this doesn't solve the problem.
 
One solution is to remove the instance of the VProject Environment variable. In Windows XP this can be accomplished by the following:
 
#Right-click on ''My computer'' and click on ''Properties''.
#Select the ''Advanced'' tab.
#Click on ''Environment Variables'' near the bottom of the window.
#In the ''System variables'' section scroll down and highlight the line ''VProject''.
#Click the ''Delete'' button.
#Click ''OK'' twice to exit.
 
However, this solution will create the ''Unable to find gameinfo.txt'' error instead. {{TODO|Delete this non-functioning solution alternative?}}
 
'''Alternative Solution'''
 
vtex.exe cannot understand spaces in the input file. One solution is to create a folder directly on the C:/ drive with the same name as the original one the vtex shortcut was pointing at. For example, create C:/tf instead of C:\Program Files\Steam\steamapps\<account_name>\team fortress 2\tf. Update the vtex.exe shortcut to point to this new folder. In this folder, put the gameinfo.txt from the original folder, as well as an empty materialsrc and materials folder. Place your file to be converted in the new materialsrc folder. Now drag-and-drop the file onto the vtex shortcut, and the output will be in the new materials folder.
 
== "Unable to find gameinfo.txt" ==
Vtex will give the following error and instructions:
 
Unable to find gameinfo.txt. Solutions:
1. Read http://www.valve-erc.com/srcsdk/faq.html#NoGameDir
2. Run vconfig to specify which game you're working on.
3. Add -game <path> on the command line where <path> is the directory that <code>gameinfo.txt</code> is in.
 
This error will occur after ''VProject'' has been removed using the steps above.
 
Open Source SDK and change the ''Current Game''.
 
{{note|The link at step 1 won't provide a solution. (The page is really old.)}}
 
== Setup file gameinfo.txt doesn't exist ==
The Nov 7th, 2007 SDK release includes Orange Box with TF2 and trying to use vtex in this new SDK update to create a vtf file for Team Fortress 2 results in the following error message:
"Setup file 'gameinfo.txt' doesn't exist in subdirectory 'C:\Program Files\Steam\steamapps\player name\sourcesdk\bin\orangebox\bin\vconfig'. check your -game parameter or VCONFIG setting.".
 
Assuming that this is the same error as "Unable to find gameinfo.txt" above, then trying to run <code>vconfig.exe</code> results in this error:
"This application has failed to start because Steam.dll was not found. Re-installing the application may fix this problem."
 
Solution:
#Create a shortcut to vtex.exe which is located in "C:\Program Files\Steam\steamapps\player_name\sourcesdk\bin\orangebox\bin\vtex.exe" and select Properties.
#At the end of the Target text add -game "C:\Program Files\Steam\steamapps\player_name\team fortress 2\tf" -nop4
 
Valve intends to fix the problem with requirement of a <code>-nop4</code> argument to be added to the target.
 
== TGA is bogus ==
Vtex will give the following error:
 
TGA <path> is bogus!
 
The texture image you are trying to convert is not recognized as a valid targa (.tga) file. Make sure that it is, and that it is either 24 bit/pixel or 32 bit/pixel. (16 bit/pixel is not recognized.)
 
== "Warning: falling back to auto detection of vconfig" (Windows Vista) ==
Vtex will give the following error:
 
{{TODO|Please provide an exact quote of the error.}}
 
Make a shortcut for vtex.exe and add ''-game [path to game directory]''
:'''Example:''' -game c:/steam/steamapps/sourcemods/Awakening
 
If there are spaces in any of the folders in your path use "
:'''Example:''' ''-game "c:/program files/steam/steamapps/sourcemods/insurgency"''
 
== Error loading texture texturename.pfm ==
The byteorder ( endian ) of your .pfm is probably not the correct one.<br>
If you exported your texture from photoshop, this might happen depending on the specific photoshop version you are using.<br>
A workaround for this issue is by converting to .pfm using [https://imagemagick.org/ Imagemagick] ( Make sure to download the version specific to your OS that has HDR imaging enabled! )<br>
Run your texture ( .tif, .hdr, .exr ... ) through the tool with <code>-endian LSB</code> and the resulting .pfm should no longer make vtex complain!
 
== See also ==
* [[Vtex (Source 1)|Vtex]]
 
[[Category: Tools]]
[[Category: Material System]]

Revision as of 21:31, 13 April 2023

Redirect to:

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=Vtex_troubleshooting&oldid=296396"