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

Error Handler: Invalid characters in the path

Messages
3
Country
portugal
Hi,
When I try to import one bgl file with the last version 1.4.0.0f6cf67c DEV 11-10-2015, I have this message:

Error Handler
An error occured during importing D:\Cascais\Scenery\lpcs_tires3d.bgl
Error:
Invalid characters in the path.

The last line in the log is:
16:23 SCASMReader Information Starting reading of subobject 0

The path of the files do not have invalid chars.

With the version 1.4.0.0 7382183 DEV 26-05-2015 everything works fine and I can import and convert without errors, but in this version I do not have the P3D V3 export option.

Is this a bug or anything I'm doing wrong?

Thanks :)
Framac.
 
Sounds like a bug, I'll have a look.
 
Hi,

That was a bug from a recent change indeed. I have fixed it now and the development release of tomorrow will work again.
 
Back
Top