• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

SB Error in named vtp field

CrashTestDummy

CrashTestDummy

Messages
181
Country
vaticancity
SB9

Draw a poly...
Right click select VTP2
In VTP2 select named texture
Double click on field

Error 76 Path not found... and whole app crashes...
Its always done it...

I dont know how to fix it... have never seen it work?

Thx
 
It could be a bug crept into the last release of SB9.

There is a work-around. The SBuilder\Tools folder contains a file named lines.txt. This file can be edited.

Code: 
[Texture.1261]
Title=Bridge dirt / 10 lanes / undivided median
Color=0 200 50
Textures=na.bmp

[Texture.5001]
Title=Custom Line Texture
Color=0 200 50
Textures=na.bmp
NamePack=yyy

[Texture.5002]
Title=Custom Line Texture
Color=128 255  128
Textures=na.bmp
NamePack="Wi.bmp;Hw.bmp;Sp.bmp;Su.bmp;Fa.bmp;Lm.bmp" 2 1 0 4

In this case, after Texture.1261, there are 2 examples of adding textures to the list. Texture.5002 shows how to add a fully named set... about changing the 2 1 0 4 at the end... change to 2 0 0 4, otherwise it will expect some effect info. Use the Texture.5002 as a template to add more line texture combinations, and SBuilder will add them to the SCASM code before compiling.

Here's an example I made:

Code: 
[Texture.5003]
Title=Custom Line Texture
Color=128 255 128
Textures=rbanksu.bmp
NamePack="rbankwi.bmp;rbankhw.bmp;rbanksp.bmp;rbanksu.bmp;rbankfa.bmp;" 2 0 0 4
5 seasonal textures, no night texture, no effect ( 2 0 0 4 ).

Dick
 
Last edited:
Wow!!!! there is a fix for this? I will give it a try.

Whats the difference between named and assembled?
 
Named textures allow you to use any DXT1 texture... not just those from the fs2004 terrain.cfg file.

I swear I used to be able to name textures, but my copy of SBuilder also crashes if I try to use named textures. Perhaps a folder is missing, as it indicates a path is invalid.

If named textures work for anyone, I'd be interested in seeing your SBuilder folder structure.

Edited++++++++++++++

I uninstalled FS9 and deleted SBuilder. I then reinstalled FS9, and recopied SBuilder to my program Files folder ( WinXP ). The named texture option now works. Go figure.


Dick
 
Last edited:
Yeah rhumba,

I think we need to ask Luis Sa what the named code is trying to read in FS9...

I have reinstalled SB 10 different ways ;) no luck... all works except for named textures.

I think its crashing on the FS9 config and not line.txt ini... and I have a feeling it happens as soon as one has loaded expanded 3 rd party sceneries...

And that means SBuilder named is broken... cant design if you designing to 3rd party scenery you cant see...

Now I need this... I want to try design my own road textures... so the question is how do you put new assembled textures into FS9 directly, so they show in assembled... so we can just ignore the named feature.

I think SA assumes a file is there and its not because a 3rd party package has replaced it... in FS9... crash!

My installation is 15 gigs... I'm not reinstalling FS9... I cant even remember all the stuff I've installed... like perfect water and some mountain lodge in brazil and...

So now I'm looking for a good VT texture making package... suggestions ;)

PS its not a new bug because even if I load SB_205 it also crashes... I think its a scenery hell problem... someone out there has done something naughty to FS9 ;) ... and SB named doesn't like it.

SA... read up on throwing exceptions (try catch) because we have no idea where its failing ;)
... when SB is good... its very very good... but when SB is bad... its very very bad... allot like my wife :)
 
Last edited:
Perhaps Luis will respond to this thread. SBuilder was written in the old Visual Basic 6... My experience was the same as yours. 205 or 206 made no difference. I actually think deleting SB's ini, and uninstalling/reinstalling FS9 works fine... then let SB reset upon restarting works.

But that doesn't tell us the 'path' that is missing.

Dick
 
Well I tried named selections on a project I have been working on and it did not ctd. I didn't make any custom textures but, it still brought up the named selections window. I have been avoiding this because it would always ctd. However i didn't change anything in the program. :confused:

The only clue I am seeing is in the lines text. Actually the majority of vtp lines in the file are associated with a na.bmp. This is a blank bitmap located in the bmp folder of the sbuilder install. This would also explain why vtp roads always look the same. For example the 8 lane highway always looks like the single lane highway(divided or not). Perhaps we need a texture pack to fill in the voids.

Another clue is in the world/scenery/texture folder. There are several road bmps used by sbuilder as well as some that theoretically could also be used by changing the na.bmp to something else in the lines.txt. I hope this make sense as I am just thinking out loud.

Dan
 
Hi CrashtestDummy.

Here's what I've found:

Simply deleting the SBuilder.ini ( which will then be rebuilt ) doesn't solve the problem, nor does simply deleting the SBuilder folder, and remaking it from the zip file.

The 'path' problem is the registry entries for FS9. It's the registry that SBuilder is trying to read, and re-installing FS9 rebuilt the registry for me. There are some programs that will 'repair' FS9's registry entry, but they do not rebuild it to it's original state, and SBuilder will fail on them.

Here's my registy entry ( WinXP ):

Code: 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\microsoft games\flight simulator\9.0]
"MP9Check"="3"
"Zone"="http://zone.msn.com/asp/fs04redir.asp"
"Version"="9.0"
"Launched"="1"
"PID"="xxxxx-xxx-xxxxxxx-xxxxx"
"DigitalProductID"=hex:
"EXE Path"="C:\\Program Files\\Microsoft Games\\Flight Simulator 9"
"CDPath"="D:\\"
"VersionType"="RetailVersion"
"InstalledGroup"="5"
"LangID"=dword:00000009

fs9registryentryq.png


I altered the product ID number to the above. If you are having problems with SBuilder, you might want to compare your registry entry to this. I deleted my regisrty entry for fs9, then ran a widely available fs9 registry repair utility... and then I get the path not found error! If I re-enter the saved registry values ( my exported FS9Registry.reg file ) then it works fine. And it works without deleting the SBuilder.ini file.

Dick
 
Last edited:
Thanks Rhumba... no thats not it, my reg is identical and I ran FS9 repair just to make sure.

Also when I make photo scenery... SB knows where the main scenery files are, it puts stuff in them... so it knows where FS9 is.

Thanks for trying... its probably something silly and we'll never find it.

My guess, its something in the Scenery.cfg file... I think SB parses it and mine is different, probably has some old rubbish in it... that I've got rid of but it still has a ref and SB doesnt like it...

I imagine... if I ever do see the dialog... that its going to try show me all the textures... so I imagine that its asking FS9 or some scenery file for them... and I have something that doesn't exist anymore... and SB cant catch the error.

Ask Luis SA what would happen if an installation program installed scenery... and then the user killed all the files because they didnt like it...

I know FS doesnt mind that... but I think SB hates it when it picks up phantom scenery textures...

Don't worry... without a good error message we might never know... I'm resigned to learning how to do it manually... but hey I still like SBlder ;)
 
Last edited:
You must log in or register to reply here.
Back
Top