|
Post by DirkDP on Oct 6, 2015 20:07:42 GMT -5
I finally upgraded from 1.602 to 1.70. When I want to start up the Admin I get the "not Win32 application" error or something like that. This has happened on a previous build as well (I think one of the 1.5 ones). But from within FS, I can start the Admin from the FSC menu. I'm on WinXP x86 and FS9. DDP. Edit: I just noticed another post which may be about the same problem. fscaptain.proboards.com/thread/2353/fscaptain-1-7
|
|
|
Post by Lane on Oct 6, 2015 23:56:59 GMT -5
Welcome to the club.
I have seeing the same problem.
Regards Lane
|
|
|
Post by Travis on Oct 7, 2015 18:14:03 GMT -5
I'm so sorry, but the EXEs that are made from Visual Studio 2013 seem to be incompatible with Windows XP - and this is even with the official "build for XP" flags being set. Once 1.7.0 is finally finished, I'll coax my old Vista PC alive and use its older Visual Studio to try and compile an "XP Version." If that works for you, then we'll keep the tradition going as long as that PC boots.... DDP (everyone else can safely ignore this), You really should get someone in to fix that crack in your wall. Who knows what might slip through???
|
|
|
Post by DirkDP on Oct 7, 2015 20:13:49 GMT -5
DDP (everyone else can safely ignore this), You really should get someone in to fix that crack in your wall. Who knows what might slip through???
Well, season 9 got under way a couple of weeks ago, so... About the Admin.exe, I still have the v1.62, do I lose a lot of new stuff by using that in Windows? From within FS the "build airport database" of the v1.70 is greyed out, but everything else seems there. So I can still set things up inside FS. DDP.
|
|
|
Post by Lane on Oct 7, 2015 20:59:17 GMT -5
Guys,
I am using 1.6.2 and I think everything is working? I still have a lot of learning to do as I have been away approx 5 yrs. I am using dutch's DC3-C and I am using the Traditional FCOM F-keys because that was the one I used when I was Beta Testing. have been making some cargo runs. I have to set my flights up using the FCOM because there is a lot of things in the administrator I just don't know how to use. For now I will use Fs9 I get good FPS. I know it does not have all the good scenery and stuff Like FSX and FSX steam. Travis, I understand why you and the team have to make it work with the new Flight-sims That would like like trying to make it work with Fs95 fS98, Fs2000, Did I miss some? So till I get a upgraded PC with win 7 or Win 10 I will just be happy with Fs9.and FSC 1.6.2 I am sure I fine some good free addon's for Fs9. and make it look good again. Thank's for reading Regards Lane
|
|
|
Post by Travis on Oct 7, 2015 21:02:12 GMT -5
DDP, I disabled some items in the Administrator from inside FS that could conceivably result in a real mess - imagine starting a flight as "Joe Pilot" for "Landmark" and then opening the Administrator and changing your Pilot or Airline.... oops.... If you need to rebuild your airport database you can do this manually - first run \MakeRwys.exe if you've changed your scenery items, then run \FSCaptain\bin\SceneryScanner.exe afterwards or if you've only changed some ancillary FSCaptain data file (such as customs or private or even transitions....). Now if SceneryScanner.exe won't run for you, please let me know as I think I have more control over that (as part of the .Net Framework). A few hours ago I transported the 1.7.0 code over to my Vista PC and VS2010 gave me over 100 errors... things like "I don't recognize that data type" that work fine in VS2013. Changing them all will take several days of trial and error, which is why I have to wait until 1.7.0 is "done" before I can start investigating a code change for an individual OS....
|
|
|
Post by Travis on Oct 8, 2015 0:27:04 GMT -5
Lane, I would encourage you to try flights using the FCDU rather than the FCOM... the FCDU - even in FS9 - has much more capabilities. Check the Tutorial document for an example of a default B737 PAX flight with the FCDU. I've not found any PC with a better bang-to-buck ratio than the one you showed me. I hope that Santa / Saint Nick / Father Christmas / Whomever can find room for one for all our XP Captains out there. XP simply isn't safe these days.... Regards,
|
|
|
Post by bbrazeel on Oct 8, 2015 8:11:16 GMT -5
Lane, I use Dutch's dc3 too. U just went into panel.cfg and changed one entry from fcom to fcdu and that worked. It is the line. Not at home right now but it was a easy fix and gave me the new fcdu in the dc3
|
|
|
Post by Travis on Oct 8, 2015 16:13:27 GMT -5
The gauge window size may be off if you do that. If it is, you can use the ACARS Installer to remove the gauge and then to reinstall the FCDU with the proper sizing....
|
|
|
Post by DirkDP on Oct 8, 2015 19:32:03 GMT -5
If you need to rebuild your airport database you can do this manually - first run \MakeRwys.exe if you've changed your scenery items, then run \FSCaptain\bin\SceneryScanner.exe afterwards or if you've only changed some ancillary FSCaptain data file (such as customs or private or even transitions....). Both are running OK. DDP.
|
|
|
Post by DirkDP on Oct 8, 2015 20:57:40 GMT -5
And back to square 1...
Just using the 1.62 exe with the rest of 1.70 doesn't work. Payload of 11000lbs, yet no pax and overload (E-170).
Using the 1.70 exe from within FS to set up a flight doesn't work either. The admin wants to rebuild database but can't find makerwys and sceneryscanner, so no rebuild.
I did do the rebuild & scan manually (and it worked, new files were generated) but FSC doesn't seem to know that. Trying to set up a flight from the FCDU won't work either, airport not in database...
Anyway, I was in the process of setting everything up on a 21th century PC with Win7 so the problem will go away. I'll revert back to 1.62 on my trusty "industrial revolution" PC. DDP.
|
|
|
Post by Travis on Oct 9, 2015 0:50:58 GMT -5
And back to square 1... Just using the 1.62 exe with the rest of 1.70 doesn't work. Payload of 11000lbs, yet no pax and overload (E-170). Using the 1.70 exe from within FS to set up a flight doesn't work either. The admin wants to rebuild database but can't find makerwys and sceneryscanner, so no rebuild. I did do the rebuild & scan manually (and it worked, new files were generated) but FSC doesn't seem to know that. Trying to set up a flight from the FCDU won't work either, airport not in database... Yep - mixing and matching won't ever work for various reasons. A 1.6.2 EXE won't be able to understand the 1.7.0 airport.cfg or log files. Win 7 has just under five years or so of "extended support" so if you can chance a fresh install of Win10, that ought to buy you ten years and six days from now....
And if you do go back to 1.6.2, do so without any 1.7.0 config files or databases. If you made a full backup of your 1.6.2, I'd recommend a full install of 1.6.2 (to catch the gauges & the module) and then to refresh your \FSCaptain\ folder.
Thankfully, the "first install the old version" step won't ever need to be done any longer after 1.7.0... (we bake copies of the gauges and the module within the FSCaptain folder).
|
|
|
Post by peter on Oct 9, 2015 2:51:45 GMT -5
If "E-170" refers to the Feelthere\Wilco Embraer 170, it could be that FSCaptain gets confused by the aircraft.cfg file of this model. It contains multiple lines of the form atc_model=x and the problem with this plane is that these lines take different values. Try to set them all equal to the value in your FSCaptain aircraft config file (make a backup of the original file first).
Cheers, Peter
|
|
|
Post by fardel on Oct 10, 2015 8:59:39 GMT -5
Hello, I have installed FSCaptain 1.7.0 RC4 in Prepar3D v3.0 with EMT - all works fine and th dll.xml was updated right. Only problem if i run Admin.exe without EMT active I have a message becouse Admin.exe do not found the dll.xml in his location. If I run Admin.exe with EMT activated all works fine. Thank you for help
Paolo
|
|
|
Post by DirkDP on Oct 10, 2015 10:34:15 GMT -5
If "E-170" refers to the Feelthere\Wilco Embraer 170, it could be that FSCaptain gets confused by the aircraft.cfg file of this model. It contains multiple lines of the form atc_model=x and the problem with this plane is that these lines take different values. Try to set them all equal to the value in your FSCaptain aircraft config file (make a backup of the original file first). No worries here, checking the aircraft.cfg after I install an aircraft is the 1st thing I do. Here I've set the atc_model= to E170, E175... and also in the FSC config files. And I've used EditVoicePack, so ATC calls me "Embraer 170" instead of "Embraer Embraer Jet". Back on topic, I'm back with v1.6. I had everything backed up, including what goes into root, \modules and \gauges. DDP.
|
|