RV7 crashing on 64bit system if not installed in x86 folder ?

[mason]

I have Win7 64, Fsx gold edition, fsx is in hard drive c, not in x86 program files. When i go to load rv7 it shows baytower on list with all the models, but as soon as i click it fsx locks up along with computer. I have ati 6970 video card. checked config and seems to work but still locks up. also checked bts lic file and it is in windows as near as i can tell. Not sure if flight1 installs files in wrong places or what. thanks for help. also noticed during install that it never asked for keys, it just installed the plane.

[maherd]

Hi Mason, I don't usually recommend uninstalling but I think in your case it's a good first step.
--> uninstall script:
Start > All Programs > BayTower > VANS-RV7 > Uninstall > Uninstall_RV7_v*

Download the latest installer to confirm you have BTS_RV7_v01-06-08.exe (<-- this is the link)
And use the "reinstall option", let me know if you've misplaced your key and password.
Let the installer run its course and use it's default install folder.

It's possible you didn't complete the entire install when you unpacked the F1 installer the first time...and this is why you didn't get asked for a key as you installed today. That's not a problem as far as I know, but it's sort of non-standard. If we do an updated and fresh standard install we'll have a better footing to work from. I'm not sure of the implications of not using the x86 folder. It's possible this could affect the RV's C++ gauges...so we'll check that next.
Danny

[mason]

Uninstalled as directed, then reinstalled, then went 2 flight one website to make sure key was activated. checked permissions on some files and had to activate some of them. Noticed there was no sound files in rv7A folder only config so took sound files and copied them from rv7 folder. made sure config tool was set to directx9 and also in fltsim. model displays in aircraft list and also looks good when i click details. Still locks up fltsim and computer when i click load. also i know antivirus program is off. Just checked that guages load for all other aircraft that i have. Checked dxdiag and it says dx11 but ddi version is 10.1, but all other planes work so this should not be a factor. I must be missing something somewhere. Also what is best time to contact so i can get reply as im in mtn time zone. This is a great plane so i dont want to give up yet!

[mason]

Greetings, I think i might be making progress here. I deleted all my config files and put settings back in fsx. when i restarted fsx it asked to approve some guages. It went thru the first one and then when i went to approve btssound.dll it locked up game and computer. this is farther than i have got before. this file is in fsx guages. Is this the right folder? In the old flightsim i think it would have been the modules folder. Also noticed btsrv7configG is at the top of this list in this folder. Is this the right place? Thank you for all your time. I still do not regret buying this plane as i think its an awesome one! Just need some help as I know just enough to get things messed up!

[maherd]

Hi Mason, I'm in the Pacific Time zone...so I’m just next door Thanks for exploring this a bit more, it's good information.

The name of the sound gauge is "btsSND.dll" specifically, is this what you meant? "btssound.dll" is no longer used or included, it can be removed from your safe-list in FSX.cfg. Be sure to confirm you are using v01-06-08 if you haven't already.

It's possible to comment out the dll's in the PANEL.CFG file. And that's the best way to debug this. Here's an example below. Use // and renumber all the gauge# to keep the gauges in sequence. The RV will be missing some functionality, but it should not crash. By a process of elimination you should be able to find which dll (possibly all of them) is causing the crash. There are four panel.cfg's so just a small reminder to test the matching RV. These are all 32bit dll's so one suspect is how they are managed on your 64bit system (outside of your 32bit programs folder). Did you move your FSX folder? It could be that FSX's registry path is invalid - there's a Flight1 fix for this.

[VCockpit01]
size_mm=256,256
pixel_size=256,256
texture=$vcDigiFlightII
background_color=0,0,0

//gauge00=btsXML!BayTower_XMLSound, 0,85
//gauge01=btsSND!sound, 0,0
gauge00=btsRV7_configG!configGlobal, 0,0
gauge01=btsRV7_configL!configLocal, 0,0
gauge02=btsRV7!propDrag, 0,0
gauge03=btsRV7!sim, 0,0
gauge04=btsRV7!digiFlightIIVS, 0,0,256,84
gauge05=btsRV7!pidController, 0,0
//gauge08=btsENG!control, 0,0,0,0

PS.

Noticed there was no sound files in rv7A folder only config so took sound files and copied them from rv7 folder.

Several sound folders only include a config file, but copying wav files to these locations won't hurt.

Also noticed btsrv7configG is at the top of this list in this folder. Is this the right place?

Yes, %\Microsoft Flight Simulator X\Gauges is the correct location. btsRV7_configG is at the top of the list because it is a folder (contains XML script).

[mason]

Thanks for your time and help, i will give this a shot and get back to you!

[mason]

Deleted btssound.dll out of fsx guages and it loaded after i approved the next guage! Loaded aircraft on runway and it is missing canopy, tail and wings. All the sounds seem to work good though. On sliding canopies there is windshields and top of dash, on tip up canopies it is missing top of dash and wings and tail. did the unlock fix to no avail. Im going to double check a couple of things. Woohoo, getting close now! Thanks for your time!

[maherd]

Great, that's progress, this sounds like a Flight1 license problem. It's likely F1 is still looking in x86.
So the next question is, did it take any special steps to install FSX outside of /Program files(x86)?

[mason]

No it didn't take any special steps, just pointed it to c drive. Also i have bn2 islander installed so im not sure what the difference is. But yes you are right it said i have an invalid licence. Im going to compare the installs between bn2 and rv7! the bn2 works fine. will get back 2 you.

[maherd]

Hi Mason, There are a couple of things we need to check to confirm your installation worked. Win7 security may have prevented a complete installation or somehow an install component may have missed your custom FSX path.

1) Search (Ctrl+F) your C: drive for BTS001.lic and post its locations...you should have two.
For example:

C:\BayTower Studio\BTS001.lic
C:\WINDOWS\BTS001.lic

2) Search your C: drive for baytwr.dll and post its location. (this needs to be in a 32bit app folder)
For example:

C:\WINDOWS\system32\baytwr.dll

3) Download fsx_reg_utility.zip, it is from TweakFS. Use it to confirm your FSX registry path. Both HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE should show your current FSX path. Press "Get FSX Path"...once for HKEY_CURRENT and once for HKEY_LOCAL_ Post your registry path here as well.
For example:

C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\

With those three bits of information I think we'll have a good idea what's going on

Danny

[mason]

Here is first post. not sure exactly how to do this but tried to post searches on this page and it wont let me by using ctrl c and ctrl v. Anyway it only shows bts001.lic in baytower studio folder. Going to next step. Ok, it is showing nothing in the windows system32 folder. Going to next step of path utility. I dont know how to copy it to this page, just did the utility. It shows hkeylocalmachine setup path as C:\FSX\. It shows hkey current user as appPath C:\FSX\. Am going to set path from root folder and add to current user key.

[mason]

How can i get the baytowerdll file if its not on my computer?

[maherd]

Mason, I'll email it you shortly.
Danny

[mason]

It is not showing the bts001.lic in windows and i know its there because I copied it from the bay tower studio folder. cannot figure out why.

[maherd]

Hey, Mason your FSX registry looks valid, so we can focus on the other files now
I've just sent you baytwr.dll and you already have BTS001.lic
Now copy these files into the following locations:

C:\BayTower Studio\BTS001.lic
C:\WINDOWS\BTS001.lic
C:\Windows\SysWOW64\baytwr.dll

Also revert your panel.cfg so all the RV7's gauges are running again.
Test the RV again, hopefully this will work.
Danny