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

RC file woes

Messages
70
Country
unitedkingdom
Good morning devs,

I was happily working away on my gauge this morning and When I compiled to do some testing I got the following error : RC2135 file not found: res\Comm1\Co1_cpt.BMP and the same for all the BMPS relating to my Com textures.
http://prntscr.com/k6c444

Ive had a look on variaious posts from stackoverflow and the MSDN sites, from my understanding it could be a problem with the RC being compiled in the incorrect format.

Now I did change from vs2008 to vs2015 community edition, and updated the project when VS asked me too.

my RC file
http://prntscr.com/k6c4je

My header file
http://prntscr.com/k6c4ou

has anybody came across this problem before?

Thank you
Daniel
 

JB3DG

Resource contributor
Messages
1,325
Country
southafrica
Your res folder still present and the path unchanged?
 
Messages
70
Country
unitedkingdom
hey guys

I can confirm that everything compiled with no issues before hand, and the only changes made was changing from vs2008 to vs2015. Originally the texures where coms is now was used for a different gauge. I changed the gauge to 3d and made the changes to use textures for coms instead.

I tried commenting out the problem gauge and the file compiled with out any problems. I'm going to go through it line by line and try compiling with just one BMP at a time.
Thank you for the link Bill ill take a read through it tonight.

Daniel
 

DragonflightDesign

Resource contributor
Messages
1,082
Country
northernireland
Okay... I'm going to tell you to do something really stupid. The RC and H file screenshots indicate that those two files are seeing each other correctly, but is the C/CPP file seeing them? Open the C/CPP file and make sure that the bitmap names are all in purple/violet. Remove one and type it back in - if the colour remains white, open the gauge master file, the RC file and the H file in that order. This forces VS to re-read the resources and you should see the bitmap name in the C/CPP file change colour to violet. The bigger the gauge, the slower VS is at recognising all the linkages between code and resources.

Lastly, CLEAN the project before doing a REBUILD.

It probably won't help but yes, I do see that behaviour and that's how I fix it.
 
Messages
70
Country
unitedkingdom
Update
I have tried all the tips, when deleting the text and then re-writing it went straight to the purple/vilot colour almost instantly. I then tried your other tip, but when I tired to open the RC file in the VS text editor, it complained about the bitmaps, that it could not find them. I am going to create a new RC file with the same name and rename the old one and then copy paste to see if that works, ill update here if that works

Thank you guys for the help so far

Daniel
 
Messages
70
Country
unitedkingdom
I fixed my issue. It was a naming convention that I missed. The comm 1 folder should have been comm1. dang whitespace lol. I need more coffee :coffee:

Daniel
 

n4gix

Resource contributor
Messages
11,674
Country
unitedstates
Yay! I'm delighted to hear you found the problem! :coffee:
 
Top