Jump to content

Gypsy Baron

Members
 View Profile  See their activity

  • Content Count

    909

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by Gypsy Baron

  1. Posted

    I greatly appreciate your patience with this issue. Here is what I did. I cut and pasted your message onto notepad and saved it as an xml file. I then brought the xmi file into the same folder as the compiler exe file. I opened a DOS window and wrote:

    BGLComp.exe test1.xml (test1 being the name of the file I saved your message under).

    Here is what DOS showed:

    INTERNAL COMPILER ERROR: #C2623: Couldn't open file: test1.BGL.

    INTERNAL COMPILER ERROR: #C2585: Unable to create output file 'test1.BGL

    This is where I am at.

    Again, your time is greatly appreciated.

    Cheers,

    Ben

    Hummm..are you on a Win7 system? It may be a matter of permissions since the

    error indicates it can't create the output file.

     

    Any time I have had a failure with BGLCOMP it listed the error type and the line

    number of the inp[ut file where the error occurred.  I don't see that  above.

     

    Also, do you have the DOS Command input set to the folder where BGLCOMP resides?

     

    For instance, my SDK is on my "X:" drive, When I go to compile an XML file I first enter this text, which I have saved in that folder as a text file, to set the correct path'

    X:
cd Microsoft Flight Simulator X SDK\SDK\Environment Kit\BGL Compiler SDK

    After entering that text, corrected for YOUR path, you can then enter the

    "bglcomp.exe test1.xml" line.

     

       Paul

  3. Posted

    Add the statement "HotKeySelect=x" at the end of the CameraDefinition.nnn sections for

    the views you want to map in the Aircraft.cfg file.

     

    x = the number of the "View Camera x (select)" assignment from the FSX "Settings -Controls" menu.

     

    Those available for assignment are 0, 4 through 9.

    Then assign the button, switch or key-combo to those entries in that menu.

     

    nnn = the camerea definition number, .1, .2, .001, .002, etc in the Aircraft.cfg file.

     

    I assign views 4,5 & 6 plus F9 to the number 2 hat switch on my X-45 stick 

    which I have set for my rightm seat, engine controls, radio stack or other VC views

    and the left seat (VC default view - F9).

    I move about the aircraft with a flick of my thumb. I also use TrackIR so I can

    pretty much see everything I need to see with just those 4 assignments.

     

    Occasionally I add a 5th assignment on some aircraft if there is another area I need

    to see 'up close' with ease.

     

     

       Paul

  4. Posted

    L:Vars are "local variables"..variables that are used inside the gauge code to perform

    operations that are specific to that gauge. They are unique to the gauge/aircraft

    where they exist, unlike the 'global' FSX "A:Variables" and "K:events".

     

    As I mentioned in my post above, for each aircraft,, you can get the list of L:Vars

    using the FSUIPC4 function "List local panel variables".

     

    Once you find the one(s) you need, you put them in a MCRO file for that aircraft.

    This then allows those functions to be assigned to buttons/switches/axis with FSUIPC4.

     

    They will appear in the list of assignable function in the FSUIPC4 drop-down menu

    in the Buttons+Switches page.

     

    In order to use the L:Vars in FSUIPC4 you must 'declare' them with then MCRO file.

     

    I suggest you readt the FSUIPC4 "FSUIPC4 for Advanced Users.pdf" document to

    find out more about the use of MCRO files and other very useful information.

     

    What aircraft are you attempting to program those switches for?

     

      Paul

  5. Posted

    As Christopher indicated, you probably need to create a MVRO file for the aircraft in question and then

    determine the local variables used for those switches.

     

    You can get a list of the L:Vars for each aircraft by temporarily assigning a switch to the

    FSUIPC4 command "List local panel variables". When in the cockpit, activating that switch

    will dump a list of all the L:Vars to the FSUIPC4 log file.

     

    Most L:Vars have names which can be associated with their function so scan the list

    to locate the L:Vars associated with the fuel cut-off switches.

     

       Paul

  7. Posted

     

     




    If SOH were to be hacked and have all their downloads compromised, we'd never hear the end of how 'how could they be so foolish to keep running an old version of vbulletin that hackers know how to exploit'.



    It's like how you hear about company X being hacked and having all their credit card data stolen, and then people say 'well, MS fixed the vulnerability that the hackers used 18 months ago, they deserve it for not updating', you have to balance between the benefit of 'don't fix what isn't broke' vs 'not exposing yourself to obvious vulnerabilities'.

     

    I could understand 'updating' if a vulnerability is discovered and fixed, but  all to often today it seems that the 'updates' are more in the order of 'let's make it prettier' or 'let's add more bells & whistles - because we can'.

     

    For myself, any 'update' must meet a need that I have that the current version does not provide, otherwise

    I stay with 'what works'. Driver updates come to mind here. Incessant 'flash player' updates really agrivate me and I refuse to chase that ever-changing application.  Browser updates are another dubious area.

     

    I still use my Netscape 3.01 version to read some NNTP forums that I frequent. No HTML 'over-kill' or 'pretty colors' needed. Just simple, fast. text and where a picture is needed, an attachment.

     

        Paul

  9. Posted

    No, you can't revert back to default FSX by the flick of a switch. Consider this a tattoo. You can remove it, but it will require some time and effort.

     

    In that case I will have to pass on this.

     

      Paul

  10. Posted

    Is OrbX Global installed/removed via the FTX control panel in the same way that OrbX EU, OrbX NA and the Rocky Mountain packages are?

     

    The reason I ask is I fly multi-player with the 91st Bombardment Group and on our missions to Europe it is important that we all see the same visuals vis-a-vis the target area and enroute waypoints.

     

    I disable all my OrbX products when I create and fly the missions and use only the default terrain textures for those instances.

     

    Also, it is important to have the ability to define the load point in the scenery.cfg file, as is the case with the FTX stuff now. The 91st has some custom airfield scenery and it must be at a higher priority than the OrbX scenery or problems occur.

     

      Paul

  11. Posted

    You need to run each newly named copy of FSX.exe for it to create the FSX CFG file with the name you appended to FSX_xxx.exe. I would make a copy of your current CFG file for each new name so your basic cettings remain enchanged. Otherwise the new FSX EXE's  will create a new, pristine CFG file when first run that 'version'.

     

    I would do this and than make the setup changes so they get stored with the new CFG file(s)..

     

     Paul

  12. Posted

    Just be aware that the necessary files are located in the WoP3_B17 folder which is located in the A2A B17 "Panel" folder. The same is true of the C172 map files. They are in a folder within the C172 Panel folder.

     

    To just add the entries as in the post above, you need to either specify the FULL path name to the WoP3_B17 folder or, more easily, just place a copy of that folder in your main FSX "Gauges" folder. Then FSX can find the files via its normal search method.

     

      Paul

  14. Posted

    I made the mistake of bringing up the elevator *fix on the A2A forums. Better not do that again.

     

    Without the fix, I would never bring this ac out the hanger, with it, it's fantastic. My controls are perfect and I will not be calibrating them only for this aircraft alone when all others ( a lot ) work perfect.

     

    You, and others,  may want to check this post on the A2A forum:

     

    Here is the link

     

       Paul

  16. Posted

    Might I suggest that those experiencing disappearing click spots go to the A2A C172 Tech Support forum and post there.

     

    Be sure to include info on your system setup as related to multiple monitors, addon

    camera utilities, etc.

     

    It will help to identify possible common elements that could aid in coming up with a solution.

     

    One post here made mention of having to restart FSX to regain click spots.  That sounds a lot like what I have to do occasionally

    when TrackIR stops communicating with FSX. That is a problem

    related to Simconnect, I believe.

     

      Paul

  18. Posted

    Just make a copy of your fsx.exe file and rename it, say, fsx2.exe. When you run fsx2.exe it will create a new cfg file named fsx2.cfg.. You can call out different simobject locations in that cfg file while keeping your original cfg file intact. You can run fsx.exe or fsx2.exe and the two unique cfg files will let you have diferent setups for each.

     

    I do this for various types of flying. I have 5 or 6 'fsx.exe' copies with unique names.

     

    I also have a dual-boot WinXp 32/Win 7 x64 with two separate FSX installs. They do share a common "addon scenery" which is a separate logical drive holding all my addon scenery and aliased to the empty addon scenery folders in each fsx directory.

     

      Paul

  19. Posted

    In MP, the airport you are trying to spwn to must exist on the server and the gate configuration must match your installed airport.

     

    Also, the parking space/gate size must be large enough to hold the aircraft

    you are spawning.

     

    As mentioned above, if you go to the drop down menu and just select "Go to airport..."

    and hit OK you should wind up where you wanted to be.

     

      Paul

  20. Posted

     

     


    BA757, on 27 May 2013 - 12:55 AM, said:

    I want to set a joystick button to "Spot View" and the closest I've come in FSUIPC is using it to assign a joystick button to the cycle view option, which means I have to cycle through cockpit, spot, tower etc.

    I'm sure there's a way to set a button to Spot View specifically, could someone please give me a nudge in the right direction?

    Thanks


    I created a lengthy reply detailing the process but when I hit "add reply" this $^&**()( forum
    software decided NOT to add the reply. I am guessing it didn't like the fact I was trying nto
    insert two images although it never indicated a problem!!

    So, below is a link that MAY help. I don't have the patience to deal with this forum
    software and attempt to re-create my original reply!!!

    In the Aircraft.cfg file add the statement "HotKeySelect=x" to the end of the "CameraDefinition.y" entry for the view you want to assign a button to. Then find the "View Select" command in the FSUIPC4 buttons & switches assignment menu and set the parameter to "x"...the HotKeySelect number you chose above.

    See the link below for doing thisd in the FSX Controls menu as well.

    Paul

    A Link here

  21. Posted

    Doing as the above poster mentioned, changing the name of the panel folder in each of

    the aircraft folders will remove those aircraft from the selection menu but still allow them

    to be used as AI, I do believe.

     

    FSX treats any aircraft without a "panel" folder as AI.

     

    I use "panel.x". You can use a similar method to disable individual repaints, temporarily,

    by going into the aircraft.cfg file and for each paint you wish to disable change the

    "panel=" statement to "panel=off".  Then, should you chose to re-enable that paint

    you can do a search & replace function to remove the "off".

     

       Paul

  23. Posted

    Download, run the installer and enter your personal license code (if running the full version) when prompted, otherwise simply fly and be happy.

     

    No need to re-enter the key.  FSUIPC4 will find it (the .key file). I just hit "Cancel" when the license pop-up

    appears, as per instructions from Pete on his forum. In the past I have selected "use existing license" or something

    like that, when doing update 'full installs'. I haven't needed to enter the registration code since 'day one', several years ago.

     

      Paul

  25. Posted

    I have an i5-2500K which easily over-clocked to 4 Ghz and an older nVidea GTX260 video

    card running under both XpPro x32 and Win7 Pro x64 (dual boot).

     

    All my sliders are pretty much all the way to the right and frame rate locked at 30 fps.

    In mulitplayer with several other aircraft in close formation (mostly A2A Accu-Sim B-17G's)

    I have no issues at all.

     

    For the purposes of running FSX, an i7 is wasted money, IMO. AIR the selling point

    there was something to do with multi-threaded environments or some such that did

    not come into play with FSX.

     

    As was stated, you can save yourself $100 or so and get excellent performance in FSX.

     

    Paul

×
×
  • Create New...