Popcorn Posted May 14, 2010 Report Posted May 14, 2010 Hello all, I'm a bit of a newbie when it comes to FSUIPC. I have had it installed for some time, but have never made any modifications to it. I recently installed the Majestic Dash 8 Q300 version 2.004b on my machine. I'm using FSX SP2 on Windows XP SP3 32 bit. I have installed a registered FSUPIC version 4.60a as well. I have many other system deep aircraft which work just fine such as Level D 767, Captain Sim 757, all PMDG FSX aircraft, Flight 1 Mustang/ATR/Super 80 Pro, FS Labs Concorde X, and Wilco E-Jets/737. All aircraft work fine except for the Dash 8. When I load the Dash, FSX crashes and I get an error about needing smartassembly. I have the latest drivers for my audio and video, I have the most recent .net installed and the most recent direct x installed. After some troubleshooting, I figured out that I could load the Dash without any problems if I removed the Dash8All.gau file from the guages folder, but the minute I put it back and try to load it up, I get a crash. I'm wondering if there is some conflict between the dash's guage file and FSUIPC. Can someone help me out as I tried support through Majestic and while they tried to help, I'm basically being told it's processes running int he background. That doesn't work for me because all of my other aircraft work just fine. Thanks for the help. Chad
Pete Dowson Posted May 14, 2010 Report Posted May 14, 2010 All aircraft work fine except for the Dash 8. When I load the Dash, FSX crashes and I get an error about needing smartassembly I don't think any of these aircraft use FSUIPC in any case. Certainly "smartassembly" errors are nearly all ones relating to some mis-installation. It needs something you don't have. Have you tried uninstalling it and re-installing it in case something went awry? I'm wondering if there is some conflict between the dash's guage file and FSUIPC. No, FSUIPC on FSX uses SimConnect throughtut and there's really no relationship with any FSX gauges. Can someone help me out as I tried support through Majestic and while they tried to help, I'm basically being told it's processes running int he background. That doesn't work for me because all of my other aircraft work just fine. Thanks for the help. If the authors of the aircraft haven't a clue I'm afraid I have no idea what to suggest, except to get your money back on an aircraft you can't use. Sorry. Try reinstalling it first. Regards Pete
Popcorn Posted May 14, 2010 Author Report Posted May 14, 2010 Yes, I have tried reinstalling a few times and I get the same result. I'm now wondering if the issue is with simconnect. Is there a way to download and install a newer version of simconnect or should I just try to install SP2 all over again?
Pete Dowson Posted May 14, 2010 Report Posted May 14, 2010 Yes, I have tried reinstalling a few times and I get the same result. I'm now wondering if the issue is with simconnect. Is there a way to download and install a newer version of simconnect or should I just try to install SP2 all over again? If FSUIPC4's log (in the FSX Modules folder) says it is okay with SimCnnect, then there shouldn't be a problem. Possibly, however, FSUIPC is getting on okay with the SP2/Acceleration version but your aircraft is written to only use the SP1 or original base versions and perhaps they are corrupted. Show me the FSUIPC Install log (also in the FSX Modules folder). That will show if they are all okay or not. I have two PCs here, one on Win7 and the other WinXP, and both with good SP2 SimConnects but broken SP1 and base SimConnects, and nothing I do with fix them. At least short of a Windows re-install. I investigated this for two solid weeks and got nowhere. It is too complicated. Regards Pete
Popcorn Posted May 18, 2010 Author Report Posted May 18, 2010 Pete, thanks for the help, but the problem has been solved with a clean FSX install. You must have been right that the dash 8 was looking for something that wasn't there. Thanks for your help though. Chad
Pete Dowson Posted May 18, 2010 Report Posted May 18, 2010 Pete, thanks for the help, but the problem has been solved with a clean FSX install. Good! Thanks for letting me know. Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now