chasbruce

Hi, I have the Parking brake release threshold at the default 70 in the .ini and both toe brakes configured in fsuipc, but pressing the toe brakes full down does not register any change to offset 0BC8, which stays on 32767, as do both left and right brakes (0BC4 and 0BC6) Can you provide any pointers as to what I am missing? I thought that 0BC8 would return to zero EDIT - so when I apply the parking brake, all 3 offsets get fixed on 32767, so if I then try moving the pedals, as all 3 offsets are fixed, no pedal movement is detected to release the parking brake. It would probably work if only the parking brake offset was on 32767, but the 2 pedal offsets returned to zero and registered movement, ie if the pedals were independent, as then I could program pedal movement to make the parking brake motor release the parking brake Thanks Charles

Hi, I am running MSFS 2020 but using older sw, namely Project Magenta logics/systems which runs almost entirely off fsuipc. I have latest Navigraph data installed. I have tried a few ILS approaches and the Flight Director guidance is way off the ILS pointers, the latter are correct. I couldn't think why (magnetic variation?) then I remembered Makerwys - would that be the likely reason and should I run it or do you have another clue? Thanks! Charles

I think I have found a way, but if it doesn't work I'll try your LUA route I just discovered that sioc has a sound module, so rather than use project magenta, I'll rund the sound from there as there is already a variable there for the action of the speedbrake Huge thanks in the meantime, I'll revert if these 2 options don't work

Thx, that would be perfect if I could specify the trigger of the sound when this offset has a value of 16383, but the PM Sound config just has the following and PLayType is just 0, 1, 2 or CYC, there doesn't seem to be somewhere where I can put in 16383:

Thanks John, and maybe a stupid question, but will that offset be altered if I am flying a non-PMDG aircraft, I am using Project Magenta?

Hi, MSFS 2020 - I have the wav file for the spoiler deployment when the 737 touches down and the spoiler moves from its Armed position to full up. Within project magenta, I can trigger this sound by the change in value of an offset. The problem is that there is no offset I can find for speedbrake deploy. I have a sioc script from Opencockpits that controls the movement of the speedbrake, for example it states that "If speedbrake is armed, aircraft is on the ground and speed is greater than 65 knots then move the speedbrake motor" . I was thinking I could add in here to send a value to, for example, a user-definable offset or something similar, but I couldn't find sucha thing Or maybe you could point me in a better direction? Thanks! Charles

I can't find in the offset list the button and light when you do the captain side or FO side test of the oxygen mask Pls can you point me in the right direction Thx

Thanks very much for the fast reply, John, I'll keep waiting and hoping that something happens soon

With the latest ASFS release B9019 does the following mean we can now get the wxr radar? If so what is the next step? [quote] Added new API function for getting comprehensive area weather and updated API docs[/quote] Thanks

Thanks John for this, it will be something very much sought after by prosim users I believe that what is needed (like with P3D) is the creation of a radar.bin file which prosim then reads

I can't find makerwys under control panel/programs and there isn't anything in the readme about how to uninstall, so I thought I had better check. I have it on my root c drive. I presume I can just delete the folder? Pls confirm, thx

Hi, I as well cannot find the details of this 0505 offset - in the project magenta list the offsets go up to 0504 and then jump to 0506 Can anyone shed some light on this?

MSFS + FSUIPC v7.3.17B I seem to be getting quite a lot of the following application errors recently, log attached FSUIPC7.log

All sorted, thx, with update of the VC++ redistributables, sorry I should have seen this in the manual Re licence, that's great and very happy to have paid twice for all the help over the last 13 years!

I bought a 2nd FSUIPC licnence for a client pc from the same place as I bought the 1st (simmarket) but it won't accept the registration. Is it because my username and email are the same as the 1st licence? Log attached Charles InstallFSUIPC7.log

Thx John, yes I'm staying clear of the MS Store, it doesn't even seem to work, I tried to buy something several times and it said "another transaction is being completed". This fact and your comment above, it's so much easier to buy something separately and just place it in the community folder

The beta worked like a dream, all lvars picked up on all clients, many thx!

Hi, just to be sure I have this right: if I am in MSFS and I go into the content shop and buy/install an add-on (eg Origani's EGKK), I can then run Makerwys (with MSFS still open) so that my 3rd party programs will have the updated data. Is that correct or does MSFS have to be closed when you run makerwys? Thx

I just ran a test with the fsuipc beta and it all seemed to work fine. Many thx! Before, when I had this problem, I had to press reload and list lvars and everything worked. Looks like the beta has solved this to happen automatically Excuse my ignorance, I can't find those ids - attached is part of the list of lvars - the ones I have been talking about are the doors ones "B738_door"

I have resolved it! Something must have changed with the voicemeter program, because for it to work you have to focus another voicemeter program. Thx

I was using P3d v5 with Widefs7, I have widefs on a client where I also have vpilot. I was sending a keysend to this client, but it was not working because vpilot "steals" focus. Thx to your guidance some time ago, John, I resolved this with the following focus and run command in widefs (voicemeter is the program that receives the keypress). This worked perfectly and I have just moved to MSFS and fsuipc 7 (widefs stayed the same) and the focus is not working again. Any ideas as to what could have changed? I have attached my widefs and fsuipc ini files [User] Log=Errors+ KeySend1=123,16 KeySend2=123,24 KeySend3=84,10,Focus,Run1 KeySend4=66,10,Focus,Run1 Run1=C:\Program Files (x86)\VB\Voicemeeter\VoicemeeterMacroButtons.exe UseSendInput=Yes FSUIPC7.ini WideClient.ini

Thx, I'll try the beta. It happened again on my next flight, I had to do the same thing (press reload lvars) and then it worked. I'll report back after trying the beta Just in case, here is my log attached, I started the flight around 1430 local time (1730 zulu) FSUIPC7.log

Oh, I got it working, it appeared that the lvars had just stopped, I went into fsuipc/wasm/reload lvars and all is working, on both main pc and client pc

Doors are difficult in MSFS but I have got them working by using the prosim CDU for doors and an Lvars within fsuipc. I did the following on my main FS PC: 1/ Put this into my fsuipc.ini :- [LvarOffsets] 1=B738_door_0=UB66C0 2=B738_door_1=UB66C1 3=B738_door_2=UB66C2 4=B738_door_3=UB66C3 5=B738_door_4=UB66C4 6=B738_door_5=UB66C5 2/ Opened the main no 1 door in my CDU 3/ Went into FSUIPC and under add-ons/WASM selected to reload and list LVARS, there I saw a value for the number one door in open position (mine was 199) - I use this value to trigger simsounds on my main pc On my separate client PC (which has wideclient and a 2nd instance of simsounds) it is not seeing this door position (and therefore not being picked up by my simsounds program which is on that pc). Is there something I have to enter into wideclient? (In both instances of simsounds I have the same config for doors as follows)

Sorry, John, I didn't realise that, your support is equally excellent, please pass on my best regards, Pete has helped me since 2009 for which I am extremely grateful. I did the changes in the link you sent re sticky keys, but that has not got rid of it. I think it's because vpilot, in having its cursor flashing, is awaiting a key input and, as it does not recognize CTRL+T as an acceptable thing to type, the ding occurs Re the ALT key, I tried just typing ALT+T and, for sure, no beep, but what about the following in the manual?