Jump to content
The simFlight Network Forums

Leaderboard


Popular Content

Showing content with the highest reputation since 08/21/2020 in Posts

  1. 4 points
    Update v1.0 SCHEDULE BUILDER REACHES VERSION 1.0 Retro fuse option: Seven randomly selected airlines from the Real Color Retro Pack can be merged into a regular schedule New pages: Support, Updates, Airport List Minor code changes and backend optimizations Enjoy! Schedule Builder Website
  2. 3 points
    I think the electronic flight strips are flexible and can be customized by each facility so I don't think you'll see just one FAA/European version. If you do a search, you'll see several companies offering EFS solutions. Hopefully, @FeelThere will implement a configuration that is sensibly feature rich after researching the technology available today. Additionally, one of the challenges for @FeelThere in this version is the battle between screen real estate and functionality. From the videos, the EFS displays are a full screen themselves. Not an issue for those of us who have multiple monitors. Hopefully, @FeelThere will provide appropriate functionality based on available screen real estate (versus designing everything with the single screen user in mind).
  3. 3 points
    Like this then Craig. http://letmegooglethat.com/?q=ltfm 🤣
  4. 3 points
    Seriously? www.google.com
  5. 2 points
    I've got WebSockets working. Here's a quick video of real time updates every 100ms. https://youtu.be/E6RR94O8nfs This is the JavaScript for this page: var fsuipcURL = "ws://127.0.0.1:2048/fsuipc"; var ws; function btnConnectClick(e) { if (!ws) { // create a new WebSocket using the URL with the 'fsuipc' protocol. ws = new WebSocket(fsuipcURL, "fsuipc"); ws.onopen = function () { alert("Socket Open..."); }; ws.onmessage = function (evt) { // Find out which request was responded to and process it var response = JSON.parse(evt.data); switch (response.name) { case 'info': showInfo(response); break; case 'offsetsTest': showOffsetData(response); break; } }; ws.onclose = function () { // websocket is closed. alert("Connection is closed..."); ws = null; }; } } function btnInfoClick(e) { // make a request to the sever for info. request = { request: 'info', name: 'info' }; if (ws) { ws.send(JSON.stringify(request)); } } function btnReadOffsetsClick(e) { // make a request to the sever to read offset data // First setup a data structure containing the offset requests // This contains an array of ofset objects. Each object contains: // name: used to identify the value when the response comes back (can be anything) // address: Hexadecimal address of the offset // type: the type of data in the offset. Must be: // 'int' (signed integer) // 'uint' (unsigned integer) // 'string' // 'float' // size: The size of the offset in bytes request = { request: 'offsets.read', // Tell the server to read offsets name: 'offsetsTest', // An ID so we can match the response interval: 100, // Send every 100ms - specfiy 0 for read once (no repeat). offsets: [ { name: 'altitude', address: '0570', type: 'int', size: 8 }, { name: 'avionicsMaster', address: '2E80', type: 'uint', size: 4 }, { name: 'heading', address: '0580', type: 'uint', size: 4 }, { name: 'aircraftName', address: '3D00', type: 'string', size: 256 }, ] }; if (ws) { ws.send(JSON.stringify(request)); } } function showInfo(response) { if (response.success) { var data = response.data; // Create a table to display the data displayHTML = '<table>'; // enumerate each returned data item and add as a row to the table for (var propertyName in data) { displayHTML += '<tr>'; displayHTML += '<td>' + propertyName + '</td><td>' + data[propertyName] + '</td>'; displayHTML += '</tr>'; } displayHTML += "</table>"; } else { displayHTML = "Request failed with error code: " + response.errorCode + "&nbsp;" + response.errorMessage; } document.getElementById('fsuipcInfo').innerHTML = displayHTML; } function showOffsetData(response) { // clear error display document.getElementById('fsuipcReadOffsets').innerHTML = ''; var displayHTML = ""; if (response.success) { var data = response.data; // display each offset value on the page document.getElementById('aircraftName').innerText = data['aircraftName']; document.getElementById('avionicsMaster').innerText = data['avionicsMaster'] > 0 ? 'ON' : 'OFF'; // convert heading from FS units to degrees var headingDegrees = data['heading'] * 360 / (65536 * 65536); document.getElementById('headingTrue').innerText = headingDegrees.toFixed(0); // convert altitude metres to feet var altitudeFeet = data['altitude'] / (65535 * 65535) * 3.28084; document.getElementById('altitude').innerText = altitudeFeet.toFixed(0); } else { displayHTML = "Request failed with error code: " + response.errorCode + "&nbsp;" + response.errorMessage; } // set any error HTML into the div document.getElementById('fsuipcReadOffsets').innerHTML = displayHTML; } Is that more like what you had in mind? If so, I'll get it to a stable version with offset read and write so you can test it. Let me know if you have any other comments or suggestions. Paul
  6. 2 points
    Looks awesome! I got Tower3DPro only a few days ago and am really enjoying it. Can we expect different controlling positions (tower/ground/clearance) with AI to take over the positions we didn't choose?
  7. 2 points
    Just wanted to throw out some thoughts about the possibilities of bringing STB to MSFS 2020 and some of the things that may change along the way. Only just caught sight of the SDK, not seen until I received my release copy so not had a chance to consider the content. Lots of bad reports about SimConnect already, so it may not be in a fit state for apps like STB for some time. It will need to do more than FSX/P3D, particularly in providing information about airport facilities. The commercial arrangements for this simulator are different to what has gone before. I will not be able to included airline logos for example, because unlike Microsoft I do not have the means to reach out to every airline. However I will leave the infrastructure in place, so if you happen to have logos from somewhere else (don't overthink this!) you'll be OK. There will be no STB Data Server, so STB will only run on the same computer as the simulator. STB DS is the number one support issue and the effort to provide this is beyond what it returns. That's all I have for now, it will be a long journey. Feel free to comment. Thanks Simon
  8. 2 points
    Despite the system requirement and eye candy concerns, the view from the tower is the most important “equipment” - at least that is the sentiment I hear from real life tower controllers.
  9. 2 points
    Indeed it has an "actual ATC simulation" version however with a pricetag of an actual ATC simulator 🙂 However I see your point. We will try to make the new version scalable so lower end computers can hopefully run it. Vic
  10. 2 points
    Totally agree and vote for functionality over graphics “eye candy” especially since we don’t know yet what the minimum and recommended computer requirements are going to be for Tower XX. Some of us that are not gamers may not have the higher dollar computer equipment (processor, graphics card, etc.) that would be needed to support intense graphics at the possible cost of the simulation's functionality or slowing down the simulation. As an ex-military controller I love the game for its challenging game play therefore super graphics are not all that important to me. In fact, I usually don’t have much time to look at the graphics in detail since I’m normally concentrating on the ADIRS and DBRITE most of the time (normally I try to keep myself pushed to the limit of my controller abilities). I further believe the new game should be developed on the basis of it being an actual ATC simulation and not just another video game.
  11. 2 points
    I can't wait for Heathrow
  12. 2 points
    My glass is definitely half full, well more than half full when it comes to MSFS in general. It's no good for airliner flying but that I have P3D and my beloved QW757 for example, but for GA experiences and VFR it's a big step up for me. I've deleted anything VFR related from P3D now, said goodbye to a fair bit of pure photoscenery like the old Horizon UK VFR and recovered a fair bit of disk space. We'll see how the SimConnect story plays out from here. Rome wasn't built in a day, much to look forward to.
  13. 2 points
    Not related to this thread, but all FSUIPC7-beta users should update to the latest build. For details, please see I recommend all beta users to follow that thread, as that is where I will be posting updates on new build releases during the beta test period. Cheers, John
  14. 2 points
    no that is a common problem with the Game engine and it has been discussed before but they are not updating the game engine for tower 3D pro anymore as there is suppose to be a new version of towoer 3D as far as I know it being called Tower 3D XX
  15. 1 point
    Well finally after many attempts of making custom schedules I've managed to make one that actually works! Atlanta is still really busy and it can be quite tasking to make sure you don't forget an aircraft sometimes, but there are more quiet periods than usual. Should be a bit more playable for those playing alone who found a normal day overwhelming (me!). The days schedule can be played throughout the whole day though some aircraft may not show due to limited gate space, however, hour files have been included in 3 hour blocks for those who do want it busy! Most Real Color's will be needed to get some of the latest liveries but it should still hopefully work fine if it does not. Let me know if anyone has any problems I will try get to them as quick as I can. Any feedback Positive and Constructive are welcome! KATL - Champs8507 - Autumn - 2020.zip
  16. 1 point
    Hi Paul , was just reading up on your offset.GetValue example in your advanced tutorial section , but it did not compute , until now... ! I got the swithces to work with datatables , but this is more elegant ! Great ! best regard , Peter
  17. 1 point
    It seems to be more of a rumour than anything. https://onemileatatime.com/boeing-737-8/ Boeing website still has max all over it.
  18. 1 point
    That's a good idea. I'll put that in. Yes, you can set up multiple read requests each with their own interval. I think this is useful as not all information would need to be read at the same rate. It also makes sense to split the offsets up into logical groups, e.g. lights, engines etc. especially if the request only sends data if one of the offsets has changed. I'll be adding an 'offset.stop' so you can stop the request if you don't need it anymore. Paul
  19. 1 point
    A beta version of FSUIPC7 (for MSFS only) is now available for download at the following locations: http://fsuipc.simflight.com/beta/FSUIPC7.zip http://www.fsuipc.com/download/FSUIPC7.zip FSUIPC7 is being released as a beta-version. It is currently not possible to purchase a license, but a time-limited license, valid until the end of October 2020, is included in the download. We hope to have a release version ready by then, if not I will extend the beta license. We are initially releasing FSUIPC for MSFS as a beta due to the state of the MSFS SDK, and in particular that of the SimConnect API. There is still a lack of documentation on what is actually working in this SDK, especially in relation to key events/control, upon which FSUIPC heavily relies. There are several SimConnect updates planned in the months following the official MSFS release. We will continue to update and test FSUIPC7 as these updates are released. Installation Currently no installer is provided. To install FSUIPC7, simply create a folder (e.g. FSUIPC7) and copy the FSUIPC7.exe and FSUIPC7.key files to this folder (or simply move the FSUIPC7 folder created when you unzip to the required location). If you have previously used FSUIPC, you can also copy and rename your FSUIPC4/5/6.ini file to the FSUIPC7 installation folder as FSUIPC7.ini, and also remember to copy any other auxiliary files or folders you may use (.mcro, .lua, .dll, Profiles, etc). Note that the SimConnect.dll is no longer required. If you have copied this to your FSUIPC7 installation folder for an earlier release, this can now be removed. Usage Instructions FSUIPC7 as now a standalone executable, and no longer an embedded dll. Simply run the FSUIPC7.exe to start. FSUIPC7 will then sit in the system tray. To open, double-click the tray icon or use the provided context menu. A default windows hot key (currently Alt-F) is also acquired when you start FSUIPC7 which will display/open the FSUIPC7 main window. If this hot key cannot be acquired (e.g. as its already in use) then a message will be logged. You can change the key assigned by manually editing the following ini parameter: InvokeFSUIPCOptionsKey=70,12 where, in the above example, 70 is the F key (0x46) and 12 is the modifier (which is actually a hex value, 0x12 which is VK_MENU, i.e. the Alt key). For no hot key, use InvokeFSUIPCOptionsKey=No Using WideFS If you have a license for WideFS7 that you would also like to use, you can do this by adding the following lines to the included FSUIPC7.key file: NameForWideFS=<your WideFS registration name> WideFSaddress=<your WideFS registration email/address> WideFS=<your 12 character WideFS key> You will need to restart FSUIPC7 for the license to take effect. Missing Functionality The following functionality is not currently available in FSUIPC7. We may look at re-instating some of these items at a later date, if and when such facilites are provided by the MSFS SDK: 1. Mouse Macros (and other mouse functionality, e.g “mouse look”, etc): pending facilities to be provided 2. lVar access: pending facilities to be provided (if lVars still exist!) 3. AI Traffic management (Traffic Limiter and Zapper): pending facilities to be provided. Note that the offsets for AI traffic are populated. 4. Text display facilities: pending SimConnect functionality (some basic functionality may work) 5. Menu facilities: pending SimConnect functionality 6. Weather: apart from a few variables concerning ambient conditions at the aircraft, no other weather information is currently availablefor reading or updating Limitations Currently no documentation on what key events/controls from the SimConnect API are actually working. Many do not currently work. These include: - events for view control - events for slew control - events for weather For view and slew control, it is recommended to assign these functions directly in MSFS for the time being, as the corresponding events are working when assigned in the sim itself. SimVar status: it looks like some simulator variables that were previously read/write are now read-only. For such variables, it will no longer be possible to write/update them. Text/message/menu display facilities: may not work correctly due to issues with SimConnect_Text API function Keyboard input is not masked, and so any key assigned in FSUIPC (via any mechanism) will also be seen by the sim. Keyboard input is also recognised when either MSFS or FSUIPC7 have the window focus. The colon key (’:’) cannot currently be assigned (as MSFS is continually sending notifications for this key if requested). Issues 1. If you receive the following error when running FSUIPC7: The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem. Please see https://answers.microsoft.com/en-us/windows/forum/all/vcruntime140dll/8fe4965d-2013-49cb-816e-17cc2bb0c077?auth=1 Documentation Currently no User documentation is provided. Documentation for FSUIPC4/5/6 should generally be applicable. The UI for FSUIPC7 is slightly different, as its now an executable rather than an embedded DLL, but it should be relatively easy to navigate the UI if you are familiar with previous versions of FSUIPC. Attached is a spreadsheet (for OpenOffice or Excel)) containing details of the current state, as far as we know, of the FSUIPC offsets. This is a work-in-progress, and eventually will be used to provide an updated FSUIPC Offset Status document. I am relying on feedback from FSUIPC7 Beta users/testers to make this as complete as possible. I will provide further documentation as and when available, and all existing documentation will be updated for use with FSUIPC7 by the official release date. Functionality to be Added (ToDo list) The following is a short list of some of the main work still to be done in FSUIPC7 (in no particular order): 1. Allow a 'button screen' facility to be added to the main window of FSUIPC7, similar to the functions provided by WideClient. 2. Enable FSUIPC7 to work on a client PC (using a networked SimConnect). Note that this would be different from using WideClient, as the offset area maintained by FSUIPC7 on a client PC would be distinct from the offset area used by FSUIPC7 on the FS PC (although of course the data received from the sim to populate the offsets would be the same). 3. Add registration facilities. 4. Re-instate aileron/rudder trim control axes: either when/if axes added back to SDK, or switch to using simulator variables 5. Re-instate functionality in offset 0x2FE0 ('Add-on' menu entries) but allow menu entries to be added to FSUIPC7 menu bar. 6. Add [Programs] section to profiles 7. Provide an installer Feedback Please use the following sub-forum for all FSUIPC7-Beta / MSFS related issues: https://forum.simflight.com/forum/183-fsuipc7-beta-for-msfs/ Where possible, please provide feedback on which offsets are working for both read/write access, together with any issues found. Any problems with events/controls will for the time being be collated, and be addressed as and when we have further documentation in this area. Attached is a spreadsheet (for OpenOffice or Excel) containing the status of each offset. I will update this on a regular basis from feedback, internal testing and MSFS SDK updates. John Dowson, 17th August 2020 offsetStatus-v0.1.ods
  20. 1 point
    Johannesburg, O. R. Tambo International Airport is available! Note! Due to COVID-19, the air traffic has suffered a major setback. The schedules may not reflect actual flight data. Please consider this situation. Thank you nyergesdesign Gabor
  21. 1 point
    While wholly true what I will say is some of the definition updates and changes to how the real time scanners handle certain applications or comm's it can still break things. I don't disable AV entirely but there are times when I have to stop the real time scanners or add an application as an exception that never had issues previously because of an update or change to what they are looking for which that app is now in violation of for whatever reason.
  22. 1 point
    @FeelThere You should really consider adding these lighting effects onto the Ejets it will completely transform this great aircraft to an even greater aircraft, like @atav757said it only took him 10 mins to change the lights. Thanks so much!
  23. 1 point
    Effects, lighting visuals and the model resolution is better by far from current version. If there will be some improvements to handling of stuff it will be fantastic.
  24. 1 point
    I use process.start in VB.NET and it does start MSFS, however for some reason it does not close MSFS via the process ID. Don't know if this helps but here ya go: Dim ClientProcess as process Dim MSFS_Path as string = "shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App" Dim myStartInfo As ProcessStartInfo = New ProcessStartInfo With { .FileName = MSFS_Path, .WorkingDirectory = System.IO.Path.GetDirectoryName(MSFS_Path), .Arguments = "-FastLaunch" } Try ClientProcess = Process.Start(myStartInfo) Catch ex As Exception Logger.Log(ex.Message) End Try
  25. 1 point
    No need for calling cmd.exe, calling start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch is sufficient. Also when you have spaces you need to quote and then the start command needs an extra quoted parameter, like start "" "G:\Flight Simulator\FSUIPC7\FSUIPC7.exe".
  26. 1 point
    Maybe this will help. A few points - - 0x2E80 is 4 bytes = 32 bit = Double Word. Therefore the Offset designator should be a "D" - According to the docs the "0x" for the offset isn't shown in the examples. - Your second entry, 415, is on the release "U", therefore when you press the button it will turn off, if on. Once you will release the button it will turn on again. Avionics already on - Press = 413 turn off, 415 is skipped , Release = 413 is skipped, 415 turn on Avionics already off - Press = 413 is skipped, 415 is skipped , Release = 413 is skipped, 415 turn on This may do it for you - 413=D2E80=1 PF,24,C66701,0 -{AVIONICS_MASTER_SET}- 415=D2E80=0 PF,24,C66701,1 -{AVIONICS_MASTER_SET}- Avionics already on - Press = 413 turn off, 415 is skipped, Release = nothing Avionics already off - Press = 413 is skipped, 415 turn on, Release = nothing Roman
  27. 1 point
    Everything seemed to perform normally. HDG Mode seems OK now. I changed back and forth between HDG and LNAV as a test throughout the flight as well. I am concluding for myself that the previous install may have been corrupted somehow. Regards TS
  28. 1 point
    I've now read that the premium aircraft actually do have the aircraft.cfg (and other) files DRM protected and stored in "cgf.fsarchive". I assume that they are extracted at runtime in some manner, but effectively reading or changing aircraft.cfg for these aircraft is outside our control.
  29. 1 point
    to my knowledge there's never been any built-in facilities for transponders in any version of FS for any aircraft apart from setting the transponder code. Any on/off and mode settings have always been local to the specific gauges in the models, and possibly controllable via Local Panel Variables ("L:Vars") if anything. Currently there's no chance of accessing anything specific and local to gauges like L:Vars from an external program like FSUIPC. We have requested such facilities from MS/Asobo, but, even then, whether they are applied to such switches is unpredictable. Pete
  30. 1 point
    @borgfan & @IanAbel I have now added the ICAO designator, manufacturer and model (read directly from the aircraft.cfg file) to the following offsets: icao_type_designator: 0x0618, 16 bytes (including string terminator) icao_manufacturer: 0x09D2, 16 bytes (including string terminator) icao_model: 0x0B26, 32 bytes (including string terminator) However, not that these will only be available if the full path name of the aircraft.cfg file is received AND if it exists! I say this as, during testing this, I noticed that when loading the C172 classic (without G1000), I receive the aircraft.cfg file as D:\MSFS2020\Official\Steam\asobo-aircraft-c172sp-classic\SimObjects\Airplanes\Asobo_C172sp_classic\aircraft.CFG However, this file does not exist....! There does not seem to be an aircraft.cfg file for this aircraft model. Also, it seems that the path to this file is relative if/when you start FSUIPC7 AFTER the plane has been loaded in MSFS, but the full path is given if you load or change the plane when FSUIPC7 is already running. I will post to Asobo about these various issues. I will release the build containing this update later this evening (or perhaps tomorrow morning). John
  31. 1 point
    No, the livery doesn't matter. I've checked this and you are correct, the total weight is not updated after the initial value is set for the A320Neo. I'll report this to Asobo. John
  32. 1 point
    Ah, sorry, was getting confused - I was in MSFS/FSUIPC7 mode for some reason.....!
  33. 1 point
    Here's a quick & dirty lua. Maybe someone could put another set of eyes on it or even test it with the Bus. It is far as I can go for the weekend. It has been tested for syntax errors, proper RA conversion to feet & the arm/disarm. Roman -- Special FSL Airbus LL toggle controller, 05SEP20, Roman Stoviak (spokes2112) -- USER ADJUSTMENTS samples = 4000 -- The time between RAlt samples. In milliseconds. wait = 1000 -- The wait time between LLs turning off, then back on. In milliseconds. arm_alt = 2500 -- the altitude (at or above), in feet, where the system will arm. trigger_alt = 1000 -- the altitude (at or below), in feet, where the system will trigger the LL toggle, if armed. -- END USER ADJUSTMENTS armed = 0 -- convert the user RAlt adjustments in feet to the "raw" FSUIPC read RAlt value in meters arm_alt = arm_alt * 19975.3728 trigger_alt = trigger_alt * 19975.3728 function do_it() local alt = ipc.readUD(0x31E4) -- get the current RAlt if (armed == 1 and alt > trigger_alt) or (armed == 0 and alt < arm_alt) then -- bypass most of code, nothing valid return elseif armed == 0 and alt > arm_alt then -- arm it armed = 1 elseif armed == 1 and alt < 998768.64 then -- disarm it if the trigger was never met. IE on, or very close (50 ft.) to the ground armed = 0 elseif armed == 1 and alt < trigger_alt then -- trigger it local l_llit = ipc.readLvar("L:VC_OVHD_EXTLT_Land_L_Switch") local r_llit = ipc.readLvar("L:VC_OVHD_EXTLT_Land_R_Switch") if l_llit == 20 and r_llit == 20 then -- !!! BOTH left and right LLs MUST be ON to trigger !!! ipc.control(66587, 72496) -- turn off left LL ipc.control(66587, 72506) -- turn off right LL ipc.sleep(wait) -- delay between turning off lights, then turning back on ipc.control(66587, 72497) -- turn back on the left LL ipc.control(66587, 72507) -- turn back on the right LL armed = 0 -- disarm the system until next take off / climb end end end event.timer(samples, "do_it") --[[ Notes.. (L:VC_OVHD_EXTLT_Land_L_Switch, number) (L:VC_OVHD_EXTLT_Land_R_Switch, number) LVAR ON = 20 LVAR OFF = 10 LVAR RETRACT = 0 FSL COMMAND = 66587 LEFT LL INC = 72497 LEFT LL DEC = 72496 RIGHT LL INC = 72507 RIGHT LL DEC = 72506 31E4 4 Radio altitude in metres * 65536 ]]
  34. 1 point
    James, Believe it or not I pondered what needed to be done for this with the morning coffee! I also read the thread over at Avsim. I believe it could be done - yes... The problem is, I do not own the FSL Airbus. * If a SDK is somehow available I may be able to help.* With that being said - 1) if the landing light control can be done with L:Vars or stock landing light commands then a XML gauge would be the way to go for sure - if not... 2) then lua would do it, a bit more work in coding, but doable. A hypothesis on operation - Arming - once the aircraft gets above, say, 2500 ft RA the system would arm. ( a cushion for varying terrain ) Trigger - If armed and the aircraft gets below 1000 ft RA then : If the lights are on - turn off the lights and wait for about 1 second or less, turn them back on, then disarm the system. If the lights are off - just wait until they are turned on then do the above. The arm / disarm system is there so the turn off/on procedure is only done once. ( IE not repeating < 1000 ft RA ) * Found the LINDA kit for A3xx-X 1.5 and was able to see what is needed. It can be done in LUA. Won't be able to get into it fully until Tuesday, it is Labor day weekend in the US.. Testing will be tough not owning the aircraft, but again, doable. Roman
  35. 1 point
    Could this thread be stickied?
  36. 1 point
    For your FSUIPC4 issue, try running the FSUIPC4 installer again (no need to uninstall first). That may repair any problems and won't do any harm - worth a shot. No problem. Take it easy, John
  37. 1 point
    Here is my solution to map all toggle switches on the Honeycomb Alpha via FSUIPC to prevent the bugs that happen when always-on switches are bound in the game itself. Landing lights and strobes can be mapped directly to on/off, all other toggles require special handling in the lua script. Some notes on the special handling: State of a single battery can not be read. Only the master state which is 1 when at least one battery is on. This means if the switch is in the off position and at least one battery is on, switching the switch on will not switch the remaining batteries on. But after one on/off cycle the switches should be synced. Alternator should work correctly, toggling only those which are not already in the new state. For avionics 1+2 there are no separate controls, so 4 keyboard keys must be mapped in the sim itself for 1&2 and on&off and then the lua script will send those buttons when the switch is pressed. The lights beside landing & strobes need to be set via offset. Setting them via the FS controls leads to a race condition between reading the offsets and executing the controls when switching the toggle switch very fast. As half of the magneto states are out of the standard 32-button range the remaining states have to be polled via the lua script. But putting those and virtual buttons and then just mapping those and the real buttons to the controls does not work correctly. There will be a race condition where, when quickly switching from the virtual button part to the real button part the virtual button will be registered later putting it in the wrong position (e.g. quickly turn from "BOTH" to "R", the dial will in some cases jump back to "L", because the virtual button of "L" is registered or handled after the real button of "R"), even when polling every 1ms. Because of that instead of mapping directly to the pressed button I only register a magneto change and then determine which button is currently in the pressed state, starting with the real buttons to avoid the race condition. FSUIPC7.ini (partial) AlphaToggles.lua
  38. 1 point
    It has been inspiring to watch this site/app grow over the last several months. Your contribution is a wonderful addition to Tower 3D, benefiting both the end users, and the developers as well (I am sure that quite a few of us will purchase the Retro Pack because you gave us an easy way to use it with every airport). Thank you for this generous gift, and congratulations on reaching 1.0! Andrew Jones
  39. 1 point
    Thanks for you fast response (as always!) but I think I may have solved my issue anyway. Im trying the new Linda Beta instead of using the old VriSIM program. Kind regards, Chris
  40. 1 point
    @earthdog/ @Firefly if you are interested in using LUA then LINDA 4.0.0 provides an easy interface for creating LUA functions and linking to MSFS 2020 via FSUIPC7. The issue at the moment is that functionality is limited to the use of legacy controls and offset. LINDA provides functions for the majority of these.
  41. 1 point
    Hi John/Pete With the latest MSFS 2020 update, I have a new beta version of LINDA (v4.0.0) working well with FSUIPC7 beta. No drop in FPS being experienced and I am able to run with ultra settings. Using the default functions based on available offsets and controls, LINDA provides control of VRi Combo MCPs and Logitech/Saitek flight panels as before. Congratulations on a great job.
  42. 1 point
    Hi, there is no FSUIPC update special for the MSFS 1.7.14.0 update needed as the SDK has no update. The SimConnect interface within MSFS has been updated/ fixed internally. This doesn't mean there is more functionality available via SimConnect but at least the stutter/ FPS drop is fixed. It has to be checked now if there has been done more work already to SimConnect or just the FPS drop problem fix. Hopefully a new SDK will be available soon as well! Thomas
  43. 1 point
  44. 1 point
    i wonder if the reason there hasn't been a new airport since june 19th if that they are solely going to the next version of Tower 3D XX
  45. 1 point
    @szeliga90 On the G36 the Aux Fuel Pump switch moves from off to high via low. This is the same when using the mouse or the control 66237. The offset 0x3125 goes from 0 to 1 (bit 1). If you look under Options/Controls, filter ALL and search for Fuel you will see those controls I mentioned before. We are limited to these at the moment.
  46. 1 point
    Ah yes, forgot to enable that, sorry. Will do that shortly (probably tomorrow now). John
  47. 1 point
    For the FSlabs A3xx, they do indeed use the ROTOR BRAKE event/control as a custom control, with the parameter specifying the action. There is a tutorial on how to use these with FSUIPC over on the FSLabs forums: https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/ There was also a recent support question on these that may be of interest: John
  48. 1 point
    @RainerM if I might chip in here. I do not use SerialFP2 with my VRI MCP panels except to install the FTDI serial to USB drivers. As the support developer I would recommend you investigate LINDA 3.2.6 which works with all VRI combo MCP panels and P3Dv5. There is a 30s delay on P3D closing before the MCP is released. This was added to FSUIPC6 to ensure that the P3D background task correctly terminated. This should solve your issue.
  49. 1 point
  50. 1 point
    Hello, I just reset my computer and i can not find my download link, I am sorry to disturb but can i have a refund of the money because i have spent alot of money an dwould like a refund. Thanks again
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • 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.