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

FS2004 Could not find the following map?

Messages
1,637
Country
unitedstates
Haven't ran SBuilder in years (that's the FS2004 version). So I re-installed, started a new project, Clicked on 'Map', selected a bitmap and get the "Could not find the following map" error.

I see the map but not in SBuilder. It's in 24bit format. Tried a few locations to load it from but no luck. Is there something I am forgetting with SBuilder?

Is there a bmp size limit in SBuilder? In SbuilderX the image shows up fine. Size is around 430MB in 24bit format.
 
Last edited:
Ive had a similar error and I was never 100% sure, but I believe it was the map being too large for SbuilderX to handle. Took roughly 26 (more or less, cant remember that far back) map screens at 1280*1024 hi-res bitmaps and stitched together into one large file. It was a few hundred MB's when finished and covered the entire surface area of the class B airport plus some overlay I was working on. It was 278,784,000,000 square feet of land unless my math is off, which is usually the case. Center base up to approximately 10 miles out in a square basically
 
Thx for the response Kevin,

I did try a small bmp, like under 100kb and got the same error message so that sorta lead me to believe it was not a size issue. But got a little frustrated as SBuilder seemed to crash no matter what i did so I put it away last night. May attempt again tonight.

Could be the install, seemed pretty straight forward, not really an "install" to me. Location? Could be some paths? I read where the bmps have to be in the SBuilder root directory?
 
Try using a different image format. I think I use JPG or png in sbx. cant remember as havent opened it in 2 months. been playing with the new blender releases.



I read where the bmps have to be in the SBuilder root directory?

Definately not true. My project files and sbx are in different locations on my hd. Only the output goes to the root dir for sbx on my machine.
 
Last edited:
Having the same issue as well. I had to do a reinstall of Windows anyway, so I did that, tried Sbuilder again and still getting the same error.

It's pretty baffling to be honest :confused:
 
Hi guys,

For me I think it was one of two things.

1. Map was too big 430MB was more than SBuilder could handle. It works fine in SBuilderX.

2. May be just a bad image file. Try another one.

Hope that helps.
 
still unsure, filetype format and size can be the issues
Went down to 800x600 (about as small as it can go while still being useful) and still no luck. Tried moving Sbuilder to various folder locations, still no luck.

I've given up trying to use background images, and have resorted to the somewhat less precise method of slewing around in FS, and then tabbing into SBuilder to mark the spot. Time consuming as heck, but there's just no other way.
 
Back
Top