Jump to content
The simFlight Network Forums

Lifenbaucher

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Lifenbaucher

  1. On 4/18/2017 at 4:45 PM, Pete Dowson said:

    I'm not sure it works on the process in which it is running, but even if it does I don't think it will if P3D is running in full screen mode. Are you using it in Windowed mode so that Max/Min operate?

    Pete

     

    Yeah I run it on windowed mode all the time

    Have I coded the script correctly though?

  2. Hey, I was hoping to get some further help with lua. Since ive discovered this functionality I have found myself setting up scripts for all sorts of useful things...

    I wanted to create script whereby, when the simulator pauses (particularly when PMDG auto pauses at TOD), the P3D window minimizes to taskbar. This way the GPU can power down to 0% usage, saving heat and electricity. This is what I have written so far:

    function minimize(event, param)
    
    	ipc.display("Pause was toggled", 1, 15 )
    	ext.state("prepar3d.exe", EXT_MIN)	
    	
    end
    
    event.control(65794, "minimize") --pause on

    I have a feeling that I'm not use the ext.state() function correctly. Could someone clarify I'm doing it the right way, please?

    Thanks

  3. Thanks guys you've certainly helped. I've got it all working now

    @Baron - I put the purposely put the 'delay' parameter at zero so it wouldn't disappear. But i needed the text to be white, hence the 'colour' param = 1

    This is my cleared up code, in case anyone needs an example

    function runMessage(event, param)
    
    	local gnd = ipc.readSW(0x366)
    	
    	if (gnd == 0) then
    		ipc.display("Landing Lights Toggled:\n message here xxxxxxxxxxxxxxx...", 1, 0 )
    		return
    	else
    		return
    	end
    	
    end
    
    event.control(66059, "runMessage") -- lights on

     

  4. Hey guys, I need some help with my lua script which reads a FSUIPC offset. Its not working as intended and I'm not sure why

    Essential I need a message to be displayed when I switch the Landing Lights ON. But I only want this to happen when I am airborne, not on the ground. To check this I read the FSUIPC offset 0366 to see if the plane is airborne. However I must have coded the ipc.readSW(offset) incorrectly, because the wrong message is being displayed even when I am on the ground.

    Here is the code:

    function runMessage(event, param)
    
    	local gnd = ipc.readSW(0366)
    	
    	if (gnd == 1) then
    		ipc.display("you are on the ground and the offset was read correctly", 1, 0 )
    		return
    	end
    
    	if (gnd == 0) then
    		ipc.display("Landing Lights ON: .. message here", 1, 0 )		
    		return
    	end
    end
    
    event.control(66059, "runMessage") -- lights on

     

    Thanks

  5. On 2/21/2017 at 0:25 AM, Pete Dowson said:

    There is a slight preference for keeping traffic nearer the aircraft, to avoid aircraft suddenly disappearing in view. But the preference for NOT deleting aircraft at your planned airports is much stronger. Just manipulate the numbers more.

    There's no actual comparison of distance between the ground candidates once more than 0.5nm away and up to 5nm away. Over 5nm the chances are a bit higher again for deletion, So between 0.5 and 5 nm the deletion should be pretty random.

    Well, with settings much less extreme than that (I have the last one set to 20 not 5), I still get a decent spread of aircraft throughout EGLL, which is my standard test airport.

    I'm wondering if that limit of 130 isn't rather too low for somewhere like EGLL? I set mine to 200 at least. with the FS slider to to 50% using Mytraffic6.  If a full EGLL would use up almost all of that 130 and the mechanism runs out of candidates to remove when new aircraft are added, it will be just deleting the furthest ones no matter what your preferences.

    Take a look at the traffic list in the Traffic Explorer next time to see if there is a reasonably distribution of traffic elsewhere, not just all at the airport.

    Pete

     

     

     

    Yeah you are right EGLL alone saturates the 130 limit so there are no aircraft anywhere else, though EGLL does look quite full. I will try and increase the upper limit and try...

    I only use MT6 as UT2 is not compatible with P3D v3.x, and have the slider set at 35% (which I read represent true world flights, and not include artificially injected flights)

    The only reason I champion such a great traffic deleting tool as yours is the impact AI traffic has on framerate, particularly at large airports and large cities. Without the limiter there would be near 350 AI traffic in the London area which has an recognizable affect on fps.  

    But can I make a suggestion - maybe put a bias to favour deleting aircraft at "Parking" spots instead of "Gates". Especially at EGLL - in the eastern corner of the airport there are lots of "Parking" spots for aircraft undergoing maintenance. An area which during normal simming we would never come near?

    Thanks

     

  6. It works well, I have the total set to 130

    However I have noticed that the deletion of traffic at the preferred airports tends not to be randomly spread, but by distance...

    If I am at the Queens terminal @ EGLL (gate 200's) then the furthest reaches of Terminal 5 are usually empty whilst the rest of the airport is well populated

    Conversely if I am at Terminal 5/ or landing into 09L/R then the furthest reaches of Queens Terminal and T4 are quite empty...

    Just what I have noticed, my settings are:

    [Traffic Limiter]
    TrafficLimit=130
    AirportPreference=60
    GroundPreference=60
    NearerPreference=50
    PlannedAirportsPreference=5

    Maybe its something to do with the NearerPreference? I do not quite get what and how the AirportPref / NearerPref link into the PlannedAirportPref

    Thanks for introducing this tool

  7. On 2/12/2017 at 0:23 PM, Pete Dowson said:

    Sorry, I don't have any PMDG aircraft, even for FSX, let alone P3D. Ask in the PMDG and P3D forums.

    Pete

     

    Ah okay, well further testing shows the lights can be sporadic at times, and they come back after a while

    But regarding the traffic limiter:

    Is there any plans to add the option to preserve airport traffic departure and destination airports? It would be incredibly useful... Landing at EGLL isn't the same as departing from there...

    Maybe users can input the ICAOs manually or extract from the flight.pln file??

    Cheers

  8. 10 hours ago, Pete Dowson said:

    I'm sorry, but there is no way simply deleting AI aircraft will affect anything else. It is merely a simple call to a built-in P3D (and FSX) function. If P3D messes other things up when other objects are deleted then you need to report it to L-M.

    The same option is used by the FSUIPC Traffic Zapper and by all of the several AI traffic management utilities around. There's no magic and nothing special, it is just faster at doing it because it is built into the process, not an external process.

    BTW 4.962a is available in the Download Links subforum. But there's nothing changed regarding aircraft deletion.

    Pete

    Thanks for the prompt reply, and clarification...

    Just to check - are you able to reproduce the problem, or is it just my system?

  9. I want to report a bug with FSUIPC version 4.962 on Prepar3D v3.4 + HF3

    The traffic limiter option interferes with the external lights of the new PMDG 747 v3

    How to reproduce:

    • Make sure setting are set to display air traffic and the traffic limiter is set to off (i.e 0)
    • Load up 747 sitting on a runway at any airport at night (I tested at EGLL)
    • Turn on the landing lights
    • Now open FSUIPC and set the traffic limit to a number instead of zero (I set it at 100)
    • After clicking okay the landing-lights of the PMDG no longer illuminate the ground, even though the switch is 'on' ??
    • Toggle the switch several times eventually restores the external lights, but sometimes it never comes back on?

    I'm sure this is a FSUIPC bug and not a PMDG one, because disabling FSUIPC from the dll.xml file fixes the problem completely....

    I noticed some people on the PMDG forum were complaining of poor external lighting on the 747, maybe this is linked?

    Thanks

  10. Okay, it is done. Version 4.908 of FSUIPC4 includes full support for Lua plug-ins to see mouse events and act upon them.

     

    Please download and install 4.908, and also get the latest Lua plug-ins package. You'll find them in the Download Links subforum.

     

    The example I've done is especially aimed at your requirement. It is the plug-in called 'mrudder.lua' inside the Examples zip file. Just put that into your FS Modules folder then edit your FSUIPC4.INI file adding:

     

    [Auto]

    1=Lua mrudder

     

    (or a later number if you already have this section with entries).

     

    Then load up FS. When everything is up and ready, go into FSUIPC options and assign a button or keypress to "LuaToggle mrudder" in the dropdown. This button or key will switch the whole action on or off. With it off you can use all facilities of the mouse as usual.

     

    When it is on, the right mouse button will turn the mouse into a rudder control. It will move the mouse pointer to the current rudder position (left/right position on screen -- centre screen = centred rudder), and movement of the mouse left and right will move the rudder and the mouse pointer to match. The up/own movement isn't relevant.

     

    When you release the right button, the mouse pointer will go back to its position before you pressed it.

     

    If you look at the mrudder.lua file in a text ditor you will see how it works and can change it to more suit your needs if you like.

     

    Have fun!

     

    Regards

    Pete

     

     

    Hi Pete.

     

    I was trolling around the web looking for something that the OP was asking for, just to try out.  I found this post, and wanted to say thank you for adding the function.

    I know it's been a couple of years or so (very close actually), and the OP I think got busy when he got your gift.

    Thank you for all that you've done for us through the years.

     

    Dear Pete

     

    Thanks for adding this functionality. Im sorry this has been almost 2 years late. I had actually found a neat program that can make your keyboard into a joystick. This allowed me to use the left and right arrow keys as an "axis" that auto-centered if I released the keys. Therefore I got caught on this and never checked my original post. I appreciate your work however to implementing this. 

     

    Ironically that "neat program" is no longer compatible with Win 10 and P3D v3, and unfortunately that brings me back to square one. This is probably the first time I've been back to this support thread!

     

    Thanks

  11. Hi, I was wondering whether this was possible:

     

    Basically I wanted to know if I could assign my mouse yoke (X-axis) to control the rudder (and hence the steering) whilst holding down/pressing a specific key, much like the "space-bar" mouse look option.

     

    The reason being is that whilst the "auto-rudder" option does this to some extent, when taking off and travelling at speeds above 100 knots, the plane starts to bank when trying to keep it centre on the runway, because the inputs still go to the ailerons.

     

    I wanted to ask this here because I hope your FSUIPC module can offer this funtionality that obviously FSX alone cannot.  

     

    Thanks

×
×
  • 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.