Community Forum

warninglightbar

Forum Overview >> Editor

CategoryEditor
Created25.11.2021 01:08


Eirik Amundgard (bimmy34) 25.11.2021 01:08
hello i try to install a warninglightbar on a tractor, so i was just wondering what to do with this codes? and how to fix this!

I aint the author of the mod and this is for private usage!


The texture streaming needs <UvUsage> to work efficiently, custom shader: C:/Users/Bimmy/Documents/My FS 22 Mods/6R_Series/LED_Dynamic/LED_Dynamic/shaders/vehicleShaderTZG.xml
C:\Users\Bimmy\Documents\My FS 22 Mods\6R_Series\series6R.i3d (100.09 ms)
Error: Could not parse GISL program.
(744): ERROR: 'getDefaultTexCoords' : no matching overloaded function found
(765): ERROR: 'RDT' : undeclared identifier
(766): ERROR: 'y' : vector field selection out of range
(766): ERROR: 'y' : vector field selection out of range
(767): ERROR: 'y' : vector field selection out of range

Error: Failed to compile shader 8CC90F15-00002605-00000000-01C00000.

Bilbo Beutlin (BBeutlin) 25.11.2021 01:13
Simply said: you try to use obsolete shaders and textures.

Eirik Amundgard (bimmy34) 25.11.2021 01:17
Okay thanks! im new to converting and stuff and tried to buy modding tutorials today but it didnt go through.. can you simply help me understand how to make it work? like for the textures do i need to make brand new files? and for the shaders do i need to rescript them?


Eirik Amundgard (bimmy34) 25.11.2021 01:20
Okay thanks! im new to converting and stuff and tried to buy modding tutorials today but it didnt go through.. can you simply help me understand how to make it work? like for the textures do i need to make brand new files? and for the shaders do i need to rescript them?


Bilbo Beutlin (BBeutlin) 25.11.2021 02:27
Sorry, I have not yet explored the new graphics methods in fs22 like "texture streaming".
And this "vehicleShaderTZG.xml" is obviously an unknown customized shader.

What I can recommand so far is trying a standard vehicleShader, either from $data/shaders/ or for FS19 compatibility $data/fs19support/shaders.

Jordan Nault (KTM125sx) 27.11.2021 17:44
found out that even if you use the $data/fs19support/shaders/numberShader.xml it will generate that exact error in some cases. you will have to replace the dashboards numbers for fs22 assets i think in order to solve that issue.


Andreas Zinnow (DancerVlt69) 12.12.2021 04:09
I've use this way, to solve the issue:

- Remove the Shader, the Abedo and the Gloss Map from the number/digits
- add the default_normal.dds from the game path (eg. <your path>/FarmingSimulator 22/data/shared/default_normal.dds) as Normal Map

The Albedo Color values are only dummies and only for a better orientation of the digit positions.

- in the <vehicle.xml> you will find some <dashboard/s> sections. Eg the RPM of the engine (and other) you can find in the section <motorized>, subsection <dashboard>
- the entries should looks like so:

<dashboard displayType="NUMBER" valueType="rpm" numbers="numbersRpm" precision="0" numberColor="0 0 0 1" groups="MOTOR_ACTIVE"/>

* numbersRpm is the i3d Mapping Node, and should link in the i3dMapping section to the IndexPath of the transformGroup in the Giants editor
* numberColor has 4 values: R G B and transparency. RGB 0 0 0 = Black , 1 1 1 = White, Transpareny 1 = full visible, 0 = invisible, 0.5 = 50% visibility

Hope this can help a little bit and solve your issue


Ole Kristian Stenseth (xPelZx) 08.06.2022 00:09
"The texture streaming needs <UvUsage> to work efficiently, custom shader"

I got it to work for me, I just paste/copied:

<UvUsages>
<UvUsage textureName="baseMap" uvType="uv0" uvScale="1.0"/>
<UvUsage textureName="normalMap" uvType="uv0" uvScale="1.0"/>
<UvUsage textureName="glossMap" uvType="uv0" uvScale="1.0"/>
<UvUsage textureName="mMaskMap" uvType="uv1" uvScale="1.0"/>
<UvUsage textureName="mDirtDiffuse" uvType="worldspace"/>
<UvUsage textureName="mMossDiffuse" uvType="worldspace"/>
<UvUsage textureName="mSnowSpecular" uvType="worldspace"/>
<UvUsage textureName="mParallaxMap" uvType="uv0" uvScale="1.0"/>
</UvUsages>

and added it under </Parameters> on the custom shader and now Im not getting the error anymore ^^


Note: Log in to post. Create a new account here.