a340500 Posted February 22, 2011 Report Share Posted February 22, 2011 Hi There, Please advise if there is some issue My traffic 5.3 / 5.3a / 5.3a1 and 777-HD. I get all sorts of error messages.. 777-HD worked without a hitch on my traffic 5.2 / 5.2a Whats changed? Thanks and Regards, Mario Quote Link to comment Share on other sites More sharing options...
Burkhard Posted February 22, 2011 Report Share Posted February 22, 2011 Hi There, Please advise if there is some issue My traffic 5.3 / 5.3a / 5.3a1 and 777-HD. I get all sorts of error messages.. 777-HD worked without a hitch on my traffic 5.2 / 5.2a Whats changed? Thanks and Regards, Mario What error messages do you get? Did you make a full 5.3a install or an incremental update? You may have to install 777-HD again after any MyTraffic update, depending on the error messages you get. Quote Link to comment Share on other sites More sharing options...
a340500 Posted February 22, 2011 Author Report Share Posted February 22, 2011 What error messages do you get? Did you make a full 5.3a install or an incremental update? You may have to install 777-HD again after any MyTraffic update, depending on the error messages you get. Hi Burk, Thanks for your quick response, please see steps I took below. 1. Incremental upgrade using MTXV53_Crossgrade.exe from ver 5.2a to 5.3 then patched to 5.3a and consequently 5.3a1 2. Installed 777HD Demo from Directory : D:\Microsoft Flight Simulator X\MyTraffic\MyTrafficAircraftInstallers which installed perfect. When running HD AI Paints Deployment shortcut from desktop noticed the version was 1.0.1.1. I then unistalled 777-HD Demo. 3. Installed full version using FWS-777-HD.exe. On installation, noticed it was version 1.0. It installed successfully. 4. Ran HD AI Paints Deployment shortcut on desktop and I get the following error: Can't attach the error as screenshot (sucks that it only allows 20K) so here is a typeout..: High Definition Paints for AI Aircraft An error occured. If you are inable to resolve it, please contact product support Unable to cast object of type 'System.DBNull' to type 'System.String'. at DHPaints.OperatorsCollection.AddRow(DataRow dr) in C:\Documents and Settings\Administrator\My Documents\HDPaints Deployment\ClassLibrary1\OperatorsTable.cs:line116 at HDPaints.MyTrafficAeroplane.AddToOperatorsCollection(OperatosCol lection operatorsCollection) in C:\Documents and Settings\Administrator\My Documents\HDPaints Deployment\ClassLibrary1\MyTrafficAeroplane.cs:line396 at HDPaints.Form1.AddMTXAircraft(String configFile) in C:\Documents and Settings\Administrator\My Documents\HDPaints Deployment\ClassLibrary1\Form1.cs:line199 at HDPaints.Form1.LoadPackages() in C:\Documents and Settings\Administrator\My Documents\HDPaints Deployment\ClassLibrary1\Form1.cs:line 174 at HDPaints.Form1..ctor() in C:\Documents and Settings\Administrator\My Documents\HDPaints Deployment\ClassLibrary1\Form1.cs:line 132 at HDPaints.FrontEnd.Main() in C:\Documents and Settings\Administrator\My Documents\HDPaints Deployment\ClassLibrary1\FrontEnd.cs:line18 that's it.. Please advise fix.. Thanks and warm regards, Mario Quote Link to comment Share on other sites More sharing options...
Burkhard Posted February 22, 2011 Report Share Posted February 22, 2011 Thanks, I contacted the 777 programmer to ask if he has an idea. What has changed from 5.3 to 5.3a is that there are more model folders with changed name, so while up to 5.3 there was a model=FSX, this has changed to model=HighFSX. No idea if that can be the reason. Quote Link to comment Share on other sites More sharing options...
flying-w Posted February 22, 2011 Report Share Posted February 22, 2011 Thanks, I contacted the 777 programmer to ask if he has an idea. What has changed from 5.3 to 5.3a is that there are more model folders with changed name, so while up to 5.3 there was a model=FSX, this has changed to model=HighFSX. No idea if that can be the reason. I think it's a blank callsign. 777-HD simply comments out the model name and adds its own during deployment, and reverses the operation to go back to defaults. There is a fix coming to deal with it. Simon Quote Link to comment Share on other sites More sharing options...
Burkhard Posted February 22, 2011 Report Share Posted February 22, 2011 I think it's a blank callsign. 777-HD simply comments out the model name and adds its own during deployment, and reverses the operation to go back to defaults. There is a fix coming to deal with it. Simon Thanks, that was fst! Quote Link to comment Share on other sites More sharing options...
flying-w Posted February 22, 2011 Report Share Posted February 22, 2011 The problem occurred on the best possible day, a holiday, so there was time to work on the freelance side of the world. I heard back from Mario to confirm it is now working. Quote Link to comment Share on other sites More sharing options...
a340500 Posted February 22, 2011 Author Report Share Posted February 22, 2011 The problem occurred on the best possible day, a holiday, so there was time to work on the freelance side of the world. I heard back from Mario to confirm it is now working. That is correct, it works a treat. Thank you very muck Burk and Simon for your prompt response to resolution. Highly appreciate your great efforts. Cheers, Mario Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.