LOL... I've blown up many a computer screen, memory chip, harddrive, keyboard, ... funny though ... I haven't killed a mouse yet.... My Cat on the otherhand..
Um... All that jargon I was saying... Look... In windows, there is this concept of a "Working Directory".
If you open explorer, and navigate to
c:\program files\SomeDirectory\ and click on somefile.exe than that program start's with its current directory set to:
c:\program files\SomeDirectory\
What happens is, when you "run a Program" inside Visual Studio, the program it makes and then runs is actually two directories DOWN from the project directory! The Gotcha is that the "Working Directory" is your project's directory.. (Where your source code is)
This is why when you use eplorer and navigate to
YourProjectFolder\bin\debug\ and click YourProgram.exe you just made
YourProjectFolder\bin\debug\ the working directory versus YourProjectFolder.
One cheap trick... to run your app outside of Visual Studio and get it to work the same way is to literally COPY your
YourProjectFolder\bin\debug\YourProgram.exe to
YourProjectFolder and then click it.
Go back to the Cool/Shoot dbFileExist("Filename.x") thing though. Only when you know your program sees the file like it should, should you continue to load and try to get things to work some way or another.
Oh... and the making another camera is Whack.... something else might be going on... like... you are calling dbSync() in your look right?
Load objects before loop... um... thats all for now
gotta go