Jump to content
The simFlight Network Forums

Leaderboard


Popular Content

Showing content with the highest reputation since 05/24/2019 in Posts

  1. 2 points
    Really enjoying the schedule so far! So neat to be able to play my home airport at the same time as I can watch the actual flights come in on FlightRadar. Thanks for the hard work!
  2. 2 points
    All, Version 7 now posted to include CYVR (Vancouver detail). Lots of new liveries and airlines (mainly in the Canadian pages) but also includes an updated version on the B738_ua, which now sports the recently introduced new United livery being rolled out the the fleet, starting with the B738, which Gabor has added. Not all the new liveries etc are in the standard RT but have been added to make the custom schedules created by the likes of @battlehawk77 , @hexzed and @ATControl -- Joemore rewarding when used. As always, if you spot any errors or have updates for me, PM me. The next version of this document, hopefully soon, will include the EDDM RC update asked for by the forum which @hexzed has been testing and we are nearly there with this. This will include the 15 or so new liveries requested by the forum, and updated Etihad Airlines liveried B77W and will also include the NEO's for the first time covering the A20N and A21N for the likes of easyJet, Iberia, Air Malta, Lufthansa, Pegasus, SAS and TAP Air Portugal.
  3. 1 point
    VERSION 2 FILES UPLOADED 24 MAY 2019 My schedule has 29 airlines that fly into La Guardia, including charter flights. I have split my schedule into hour groups (which I highly recommend) so all flights are more likely to arrive and depart correctly, or if you prefer you can load the entire day in one go. Please refer to the below graph for your preferred times  Installation Instructions 1 Please back up the existing KLGA folder, before doing anything else 2 Please download all of the files klga_airlines.txt, klga_airports.txt, klga_airplanes.txt and klga_terminal.txt, from the dropbox link below and over write the existing files in the "Extensions\Airfields\KLGA" folder. The schedules will not work correctly if the above is not done 3 Select the folder corresponding to the hours (or full day) you have selected, and download the “klga_schedule.txt” from the dropbox link below and over write the existing files in the "Extensions\Airfields\KLGA" folder. Any questions on install please ask Schedule Notes This custom schedule will only work properly with the latest Real Traffic version -------------------------------------- I have designed my schedules on the basis that all Real Colour packs have been installed If not all Real Colour packs have been installed, the schedule will work but you will not get liveries on all aircraft In addition to this some airlines in this schedule have no liveries associated with them at all and will appear white, this is a limitation of the game and not something i can change -------------------------------------- I have adjusted a lot of callsigns to reflect the correct pronunciation in real life, so will need to be pronounced differently to what you may be used to with the default real traffic -------------------------------------- Any questions in regards to these notes, please ask I have tested the files and are working, but of course any issues, comments or corrections, please tell me Apart from that, happy controlling! Ben DOWNLOAD FILES FROM HERE Other custom schedules EDDM, Munich Airport, Germany TIST, St. Thomas Airport, US Virgin Islands
  4. 1 point
    How ya doin'? It is my pleasure to introduce my fourth offering for week schedules - CYVR - Vancouver International! Like Gatwick, Barcelona and Orlando, you get to experience a typical week in southwest Canada, taken, as always, from actual traffic data. You will be seeing what the actual controllers saw. Vancouver is the second-busiest airport in Canada, which served over 25 million passengers in 2018. As one might expect, Vancouver is a hub for both Air Canada and WestJet. There is also plenty of international traffic to provide lots of heavies, and lots of small traffic for those that enjoy a more active GA experience, and cargo traffic is also quite plentiful. As always, every effort has been made to use existing Real Color aircraft and liveries. There may be a few white aircraft, but, by and large, you will find Vancouver is a colorful place! Like with my previous offerings, you will find, within the main CYVR-battlehawk77 folder, a folder for each day of the week, along with snippet file folders within each day to allow you a smoother and more robust traffic feel. Also included is a listing of the GA operators, a PDF taxi chart, graphic and text files of the traffic levels for each day, and a text file within each day folder of the hourly traffic breakdown. It is recommended to place the CYVR-battlehawk77 folder in your main CYVR folder, then copy and paste the files needed (after you back up the originals, of course). If you have any questions, comments, or notice any bugs, please feel free to message me here or on Discord. So, grab you some Timmy's and enjoy! Gavin (battlehawk77) CYVR-battlehawk77-v1.0.zip
  5. 1 point
    VANCOUVER INTERNATIONAL AIRPORT - CYVR - FOR TOWER3D/PRO IS OUT!!! Hello Folks, we are thrilled to announce our next great release for Tower!3DPro! A huge thanks to all the community for their support, suggestions, and patience! You can purchase CYVR right away in our webstores as usual! CYVR - ATCsuite CYVR - Feelthere.com The Real Color is already available, as is the Real Traffic update for CYVR. Remember to redownload RT to get the update! Vancouver tower wishes you a good flight!!!
  6. 1 point
    The simpler option is to use output_log.txt from your tower3d_Data folder. No need to run a bat file or anything.
  7. 1 point
    @amif2000 @bingus I somewhat hijacked your ideas in this thread because I really really liked them. I hope you don't feel cheated and like my attempt.
  8. 1 point
    The "Full day"-file only contains traffic from 0900-1159
  9. 1 point
    LOL! I've created three batch files, one each for TIST, KLAX and KPHL - and have changed the option commands to be specific to each airport. You have no idea how your scripting has increased my enjoyability of the game. I was about ready to give up, but I'm now able to cope much more thanks to you. BLB (Peter)
  10. 1 point
    But you do know that you can also use the batch file for any other airport? TIST was just the airport I tested with. Just change the pre-built commands to fit your needs. 😉
  11. 1 point
    I'm not sure an infinite loop is the best way to do this. You might have better performance using the event system. This monitors the LVar values in the background and fires an event when they change. Here's an example from another user... writeN1(varname, value) ipc.writeUB(0x66C0, value) end event.Lvar("B200CFuelCrossfeed", 100, "writeN1") writeN2(varname, value) ipc.writeUB(0x66C1, value) end event.Lvar("B200CRvsNotReady", 100, "writeN2") writeN3(varname, value) ipc.writeUB(0x66C2, value) end event.Lvar("B200CLBld", 100, "writeN3") writeN4(varname, value) ipc.writeUB(0x66C3, value) end event.Lvar("B200CRBld", 100, "writeN4") You declare a function that sets the value to the offset and then register this with the event system (event.Lvar). See the FSUIPC Lua docs for full details but in summary the call is: event.Lvar(lvarName, polling_interval_in_ms, function_to_run) If you prefer you can make only one function that is called by all the events. This would need to test the LVAR name (varname argument) and write to the correct offset. I don't know about the logging as I don't use lua at all. You'll need to ask Pete about that in the main support forum. Paul
  12. 1 point
    I just noticed that I forgot one r in Clipboarder... I hope this goes as "artistic freedom"! 🤔😉
  13. 1 point
    Very nice, thanks for the effort on this
  14. 1 point
    Good to hear that worked. These are the only official user offsets. However, if your application is only for your use you can try using the blocks marked as reserved. These are allocated to third-party software. For example 0x04E0 (88 Bytes) is for Project Magenta software. If you don't use that then you could try that block. Or there is a block from 0x6420 to 0x65EC (640 bytes) which is for PMDG aircraft if you don't have those. If your software is for general release (free or commercial) then you need to ask Pete (in the main support forum) for some offsets to be allocated for you so you don't clash with other software. Paul
  15. 1 point
    Hi Agoston, That's what the DLL does when you call ReadLVAR(). It's just a nicer way of using the offsets provided. Yes only one LVAR can be read or written for each process() call. That's just how FSUIPC works with LVARS. When you use ReadLVAR() in the DLL it does a process call. When you need to read a lot of LVARS then the time adds up. On my machine with FSX and default aircraft it takes about 20ms to get one LVAR. So reading 25 lvars will take half a second for me. No it won't make it faster. FSUIPC communicates on a single thread. The DLL is 'thread safe' which means if you use it from multiple threads and nothing bad will happen. But each thread will have to wait for the others to make Process calls. Only one thread can be talking to FSUIPC at a time. You could look into SimConnect. It's not very easy to use from .NET languages and the documentation is very poor for .NET. It might let you read LVARS faster, but I don't know. The LUA scripting in FSUIPC also allows you to read LVARS and also monitor them for changes (an LUA event is fired). You could write a LUA script to monitor your LVARs and send the values to user offsets where you can read them from your program. LUA scripts can only be run with a licensed copy of FSUIPC however. Documentation for the LUA library can be found in the Modules/FSUIPC Documents folder. Paul
  16. 1 point
    It would be so nice on next release, to inclose the posibility to select static cameras view, like in chinese supermarkets. They can be localized on troubled points, like runway heads. More powerful to put on the cameras, right-clicking on ADIRS location. Thanks in advance!
  17. 1 point
    :-) Reinstall of the newest RT and now it works thx :-)
  18. 1 point
    Well done. But in general, when you want to test one "bit" in a byte, you'd use: if (x & mask) ... where x is the value you've read, and "mask" is the value of the bit( you want to test for. So in your case: if (audioSelection & 128) for COM1, and if (audioSelection & 64) for COM2 There are other bits for the other audio switches. Bit values are derived from evaluation 2 to the power n, i.e. 2 times 2 'n' number of times, with the special-seeming case that 0 results always in the value 1. So: bit 0 = 1 bit 1 = 2 bit 2 = 4 bit 3 = 8 bit 4 = 16 bit 5 = 32 bit 6 = 64 bit 7 = 128 For more about bits, see the FAQ subforum help thread entitled About bits, numbers and hexadecimal Pete
  19. 1 point
    Updated date for @hexzed's TIST release Added @battlehawk77's KBOS weekly schedule
  20. 1 point
    Updated main list. You weren't joking were you? 😉
  21. 1 point
  22. 1 point
    @ Eligrim Thanks, It was turned on by default. On the old machine it used to come up and annoy me something chronic. This one does not give the sticky keys warning on the screen. I will try it and get back if any more problems. I checked the notification s part for sticky keys and it was turned off. The reason why I did not see the sticky keys message Why didn't I think of that?????? Kev M
  23. 1 point
    The airplanes_txt file is just a growing list copied over from airport to airport release. The NEO's were added ready for the EDDM RC and SP update which is due shortly and was used for the Vancouver airport release. Also, you never know in the future, a A20N and A21N for a Canadian or US based carrier will fly into Vancouver and the type added in a future US or Canadian new airport release. I am sure someone will create a new CYVR custom schedule with them in and therefore the airport is future proofed 👍
  24. 1 point
    Had fun playing a busy period on Thursday for my first taste of CYVR. Good fun and a good schedule, thank you!
  25. 1 point
    I do not use any PMDG aircraft and I don't know anything about the parameters other than what is in that PMDG SDK document. I expect that trhe parameters are all based on the equivalent mouse action which you would otherwise use on the cockpit on screen, i.e. these as listed in that document: #define MOUSE_FLAG_RIGHTSINGLE 0x80000000 #define MOUSE_FLAG_MIDDLESINGLE 0x40000000 #define MOUSE_FLAG_LEFTSINGLE 0x20000000 #define MOUSE_FLAG_RIGHTDOUBLE 0x10000000 #define MOUSE_FLAG_MIDDLEDOUBLE 0x08000000 #define MOUSE_FLAG_LEFTDOUBLE 0x04000000 #define MOUSE_FLAG_RIGHTDRAG 0x02000000 #define MOUSE_FLAG_MIDDLEDRAG 0x01000000 #define MOUSE_FLAG_LEFTDRAG 0x00800000 #define MOUSE_FLAG_MOVE 0x00400000 #define MOUSE_FLAG_DOWN_REPEAT 0x00200000 #define MOUSE_FLAG_RIGHTRELEASE 0x00080000 #define MOUSE_FLAG_MIDDLERELEASE 0x00040000 #define MOUSE_FLAG_LEFTRELEASE 0x00020000 #define MOUSE_FLAG_WHEEL_FLIP 0x00010000 // invert direction of mouse wheel #define MOUSE_FLAG_WHEEL_SKIP 0x00008000 // look at next 2 rect for mouse wheel commands #define MOUSE_FLAG_WHEEL_UP 0x00004000 #define MOUSE_FLAG_WHEEL_DOWN 0x00002000 Those are in hexadecimal. The value 536870912 is the same as hexadecimal 0x20000000, which means "MOUSE_FLAG_LEFTSINGLE" -- in other words a single click with the left mouse button. FSUIPC also accepts hexadecimal parameters. Just precede the value with an 'x', i.e. x20000000. Pete
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

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.