• 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.

URI not valid

T

Tejal Bernardo

Messages
3,278
Country
spain
andTrying to make a bgl file for light placement, this is the warning "URI not valid",
Anyway I will post the script because not very sure, it's for Fx lights placement.

IMPORTOGR|highways_hierro_1.shp|*|HIGHWAY|NOREPROJ
PLACEPOINTSALONGLINE|FTYPE=LINE;highway=residential|50|5|type|light|hdg
CREATEXMLEFFECT|FTYPE=POINT|type=light|Fx_Strobe.fx|0|8|0
EXPORTBGL|FSX|ScenProc_Files|texture

In "PLACEPOINTSALONGLINE", in the first number, 50, Scenproc is demanding me two values. I can swear this line was copied from the fórums.

EDIT: All right I have checked that have to do with the destination folder and his address.
I will tell my life, it happen because I had to redirect the user files to the D:drive, being the first a Ssd drive it seem it was devoted to the boot functions and it got full fast enough, and consequently this have messed up a Little the folders address
Anyway I am getting zero files though
 
Last edited:
Hi,

The PLACEPOINTSALONGLINE function has changed, it now requires two values (and then will randomly choose between them). If you want just 50 enter 50;50.

So the uri error is fixed? Was it in the EXPORTBGL step that you got it?
 
Yes. solved the address issue (i think) "EXPORTBGL" is requiring three arguments.
Naaa, I forget the file name. not warnings now but zero files

IMPORTOGR|lines_lights_cal1.shp|*|HIGHWAY|NOREPROJ
PLACEPOINTSALONGLINE|FTYPE=LINE;highway=residential|50;50|5;5|type|light|hdg
CREATEXMLEFFECT|FTYPE=POINT|type=light|Fx_Strobe.fx|0|8|0
EXPORTBGL|FSX|luceshierro|D:\User Bernardo/ScenProc Files/texture

No matter, I think the shp file is wrong, almost for sure.
 
Last edited:
Check if IMPORTOGR actually imported some files. I think it might be case sensitive, so then you would need to write highway and not HIGHWAY.
 
Funny, I got a file "luceshierro_0.Bgl , 27 kb, anyway Arno, not take me into account too much, I have been testing this, not sure what I am doing, really. just that the URI warning was confusing, I am working with Scenproc after a whole reinstallation of the Pc.
 
Trying Fx lights placement. but zero files, take a look if this mean something.
 

Attachments

  • ScenProc_lights.jpg
    ScenProc_lights.jpg
    213.8 KB · Views: 504
Hi,

According to the log your file has been placed at the root of the D drive. Is there no file there?
 
Yes :whiteflag, I see some files were processed but didn't know I have been working with a changed destination folder. well no more excuses, by the way, it seem to work , I Heard the altitud of the lights could be changed ? Editing the .XML file and resampling again ?
I observed that for buildings the polygons are very irregular, no one could be called a perfect square or rectangle, what could be the appropiate value for "ParallelDot Tolerance and "Perpedicular Tolerance" if this is for this issue. thanks for all Arno.
EDIT: it seem there is a "side effect", the custom airport lights are switched off.
 
Last edited:
Hi,

Let me check the altitude. Maybe for xml effects I didn't add that argument. For xml objects it's there.

Those settings you mention don't alter the polygons. It only influences the special attributes for perpendicular and parallel edges.
 
All right, I have to mention no such "side effect", I forgot to include effect and mdl to the scenery. this is the mental state of a scenery developer, anyway all is working great. Arno I still not understood very well the last statement, could you explain a Little about those values. :scratchch Greetings.
Yes, I see the value altitude in the script, but something gone wrong
CREATEXMLEFFECT|FTYPE=POINT|fx_beacony.fx|0|8|0
the 8 number is the altitude, but could be the wrong place.
This is the line complete:
CREATEXMLEFFECT|filter|effect|heading Attr.|heading offset|Altitude|effect parameters
.....All right, all is fine Arno, just the first value was missing as can be seen above. "heading Attr.", adding all the values and working great.
 
Last edited:
You must log in or register to reply here.
Back
Top