Not all portions of executable built from vi function

[flyingfisherman]

Hello,

I've been working on creating a groundstation for a UAV. Nearing the end and we were looking to compile all of our vi's in the project into an executable. Not necessarily needed, but it makes our lives easier in some regards. All the other portions of the code compile and operate correctly except for this vi. (see attached) This was found on a forum as a great example for an artificial horizon. We've been making some tweaks on it, but this is the original version. The important part of the vi, the artificial horizion, does not operate when compiled into an executable. No one working on the project is well versed in converting vi's into executables, so we're hoping someone else might be able to spot what's causing the issue. As the file name notes, we are using labview 2011.

Thanks!

[crossrulz]

I see a call in there to the This VI's Path in order to figure out where a PNG file is.  The problem with the This VI's Path is that once you compile the code into an EXE, the path of that VI is actually inside of the EXE.  Not what you want.  Instead, use Application Directory.  This will give the folder of the EXE.  When in the development environment, it gives the folder the the project file is in.