Here's a quote from my version of the HTML SDK mission creation segment:
"The images must be 380 pixels wide by 232 pixels in height and either 256 color or 5-6-5 format (use the Imagetool utility to convert 24 bit bmp files to 5-6-5 format). The Imagetool utility is in the...
Thanks Oscar. I wasn't sure where I should put the addon file so I just chose the DLC folder. Used the manager to select it and now it shows up as installed and works fine in Flight. Noticed a couple of transparent long boxes off to the left and suppose that's why it's still beta. They're...
As far as boot time: my personal experience has shown that having both Windows and FSX on an SSD is most important. This is followed by the number of installed aircraft. I do use the Turbo mode of Advanced SystemCare (free version) to prevent unwanted background tasks from running...
I am a user not a developer. I do not create aircraft but spend a fair amount of time modifying aircraft to my liking. My main preference is flying GA aircraft cross country and having a long term destination but taking any number of deviations as I find appealing. I like to fly under...
Per JRobinson's recommendation:
The Carenado Piper Seneca in FSX:SE.
I changed the path to point to FSX:SE, immediately installed the plane and no problems noted. I'll next try ORBXLIBS but I want to do a little bit of further checking.
Sounds good. I especially like the idea of the 2 .reg files. I'm going to have to go about this slow and I'm a bit burnt out right now but I certainly intend to try this.
Thanks, Jim F.
-edited for spelling
I took an alternative approach. I exported the entire key referencing both "10.0" entries. I next deleted the key pertaining to the original FSX. I restarted Windows and installed a Carenado aircraft and it installed without any problem to the original FSX folder. I next tried to...
What are you disagreeing with?
This is only a guess but in order to get the OPT working I added the sample dll.xml from the Mission Creation section to my AppData for FSX:SE and edited the path to point to it's location.
I don't know the reasoning behind this but all the ".exe"s are missing but all the ".dll"s are included. As none of the exes are used from within FSX, but are only used for creating additional content, this may play a part in why they were excluded. All of the dlls are used from within...
Hi Bill (n4gix),
From your post it sounds like the info I read regarding how an auto-installer locates FSX is correct. And after posting the images I realized that the complete path wasn't shown; they are in "HKEY_CURRENT_USER". Now, my ignorance is likely to come to the forefront here but, to...