Jump to content
The simFlight Network Forums

TheGreyGoose

Members
  • Posts

    6
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    San Diego CA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TheGreyGoose's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Ok, I think we may both be getting a little confused. Or at least I am lol. So let me clarify everything a final time just to be sure. 1 - The issue we're having is when opening FSUIPC from the P3D v5.3 Add-Ons menu. It appears black, meaning only the actual ~10cm x 20cm box or window of the FSUIPC control assignment interface but it's all blacked out. (and the background behind it is too, but that's normal if I remember correctly.) If we grab it (the box only) and move it to another monitor, it then appears. 2 - When installing FSUIPC, and also summarily re-installing it, it appears that it is indeed installing to C / documents / Prepar3D v5 Add-ons as that is apparently where FSUIPC wants to install by default. (and you said it would do so by default due to any older installs so that makes sense if so). Regardless, I didn't see any information during install (i.e.; in the installer itself that it should be located anywhere else but it sounds like, yes, you are telling me to just make sure it installs to C:FSUIPC instead. (and I assume you mean a folder of FSUIPC6 not 7 as 7 is for MSFS2020, no?) And if I may, ...my main tip here would be that you guys might want to add a note/words of install location to the installer itself as I assume most people re-run the installer over a previous one as that has always been the normal operation for FSUIPC.. as it uninstalls the old one itself for you and re-installs the new. And therefore why would anyone think there's a need to install it anywhere other than where it defaults to. I hope you see the point here. 3 - Lastly, also in C / Documents is an FSUIPC6 folder but it appears to only contain ~15 PDFs for the User Manual, History, Lua stuff, Offset Mapping, etc. I assume it will maybe reinstall that data there again even if I point the new main install to just C /FSUIPC6 correct? 4 - My last question is with the .INI and backing it up to save control assignments. Can I copy/paste the entire old file to fully overwrite the new one or do I need to carefully cut and splice in only the old control assignment data I wish to keep into the new .INI ? Thank you for all your help and prompt attention this week. It's been very helpful.
  2. John, I'm going to take another look at it tomorrow. I'm going to first update P3D 5.3 to the new Hotfix 2 which does require a new Client install anyway so we'll do that first and see how it works out. And then if the Client Hotfix has no effect we will look at that latest Windows redistributable x64/x86 package you linked and check if the Windows Documents folder is protected. However, isn't Documents/Prepar3D Add-ons where it is supposed to be installed? That's where it defaults to normally. And it actually works if dragged over to another display, it's just not showing in the primary. To be more specific this is in a large multi-monitor / multi-PC simulator. We're running several touchscreens on a Host PC for instruments and 2 networked PC Clients for visuals. Again, all instruments are on the Host PC only though and FSUIPC is only installed on the Host (this is via P3D ProPlus Multi-Channel, not WideView). I saw in some other thread where someone else was having this same or very similar issue and it came down to adjusting something in a config file to tell FSUIPC where to show up. Does that ring a bell? Maybe that could be the issue?
  3. As of last week (Jan 20th 2022) we upgraded to Prepar3D v5.3 and then installed the latest FSUIPC (registered) v6.1.7 for assigning and calibrating our control devices. Whenever FSUIPC is selected from the Add-Ons menu in P3D the utility box appears but is completely blacked out (save for the windows grey band at the top which lets you X out of it). If you let it sit there for ~30 seconds sometimes the utility will appear and can be used and sometimes not (or I just haven't waited long enough after a few minutes or so to let it appear). I did try reinstalling FSUIPC again but the same exact thing is happening. I'm at a loss for what to do now. Please help!
  4. Ok thanks. In addition to exploring the A:value options do you maybe have any other suggestions or options I might try to go about making those two common keystrokes of Alt+Enter and Alt into gauges which effect their functions of toggling the sim from window mode to fullscreen and toggling off and on the main menu? I assume if this could be done via FSUIPC or via keystroke then there has to be some way to do it via mouse-click too. I'm also wondering if there's a way to make a mouse-click follow a keystroke command rather than the event. Maybe that's a potential workaround? Also, any suggestions on the engine start question? I wasn't sure what exactly you meant by "Try putting the number as the parameter for the control. "
  5. Pete, that was indeed the list I was referring to (List of FSX and P3D Controls) I was calling events as controls or vice versa I guess. I call them events because that is what they are called in the code, i.e. "Click Event = " for example. I assume your list are the same exact ones that are built into FSX and Prepar3D by default except of course where noted with an asterisk which are the Prepar3D v2.0 and higher additions. Again, I've used many of these controls / events to create some gauges operable via mouse-click rather than just a key press. As one example below, I made a parking brake toggle and similarly a pause toggle each with two bitmaps. One indicates when its off and one indicates when it's toggled on. It works perfectly. I've made many in the same fashion. So again, I'm just trying to nail down a few final events and am mainly stuck with the Alt+Enter / Alt functions. Surely they have to correspond to something in the list. The Alt+Enter is a keystroke toggle which takes the sim from windowed mode to full screen and pressing Alt makes the top menu bar appear or disappear so they are both obviously making a single internal command, control, or event in the simulator and therefore should have a corresponding event name in the list. Regardless, these two are easily some of the most common and most basic functions of the simulator, just like pressing the "P" key on your keyboard toggles the pause function. I've successfully made over 50 gauges so far using this list and am just stuck on these last few because the naming scheme is not obvious for the Alt+Enter / Alt commands. I've tried FULL_WINDOW_TOGGLE which is in the list and I assumed should be the corresponding event for the Alt+Enter key combo but it's not working so far. I have no idea which one is the Alt (menu toggle) but SIMUI_WINDOW_HIDESHOW is the one I tried for that as it seems to be the most likely one. (and is it SIMU-eye or SIMU-el ? I assume eye as in User Interface) Below is an example of my Parking Brake toggle. <Gauge Name="ParkingBrake" Version="1.0"> <Element> <Select> <Value>(A:Brake parking position, percent) 50 &gt; </Value> <Case Value="0"> <Image Name="PBRAKEoff_Icon.bmp" ImageSizes="50,50"/> </Case> <Case Value="1"> <Image Name="PBRAKEon_Icon.bmp" ImageSizes="50,50"/> </Case> </Select> </Element> <Mouse> <Tooltip ID="TOOLTIPTEXT_PARKING_BRAKE"/> <Cursor Type="Hand"/> <Click Event="PARKING_BRAKES"/> </Mouse> </Gauge>
  6. Pete, I'm hoping you can help me. I've been making some new XML gauges and have looked at many different event lists including the big one provided in the Modules folder for FSUIPC offsets. I'm stuck on finding the events for the common Alt+Enter (toggle full screen off /on) and for Alt (toggle main menu off / on) keyboard commands. Secondly, I'm trying to create gauges for a second instance of "opening doors / exits" (TOGGLE_AIRCRAFT_EXIT) as some large aircraft have a secondary exits function as well several engine starts too. There is obvioulsy the default engine start (ENGINE_AUTO_START) event for any single engine but I'm wanting to code start ups for the number 2, 3, and 4 engines. As is, I think they are all "shift +" types of commands so I'm wondering how I might create a workaround to make each of these into a single mouse click gauge. I've also posted in FSDeveloper but have not gotten a firm answer from anyone yet. With all of the toggle types the end goal is to use two bitmaps so you can tell when the toggle is active (on) or inactive (off). I've also noticed many events are toggles even though they do not actually say toggle like the pause and parking brake events. I've made gauges for those successfully using FS9 XML and they work great but with others I've gleaned that I need to have a different <value> parameter so any added help or advice on this would also be appreciated. Thanks for the help and support. Jeff.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.