Ubbi

Hello, i have been working intensively in fmod in the last few days and so far i have achieved results that are actually very satisfying. However, I have now encountered a first minor problem. I try to implement rain sounds. See here: Unfortunately the weather changes in X-Plane immediately without a smooth transition. Do you know a possibility in fmod that the parameters are taken over with a longer time delay? When the weather changes from precipitation to no precipitation I want the rain to stop slowly. I have written my own little "rain script" over xlua, which creates a new dataref and "follows" the actual precipitation with a delay. ----------------------------------- LOCATE AND/OR CREATE DATAREFS ----------------------------------- precipitation_on_aircraft_ratio = find_dataref("sim/weather/precipitation_on_aircraft_ratio") delay_precipitation = create_dataref("sim/weather/delay_precipitation", "number") precipitation = create_dataref("sim/weather/precipitation", "number") precipitation_direction = create_dataref("sim/weather/precipitation_direction", "number") ----------------------------------- RUNTIME CODE ----------------------------------- function before_physics() if precipitation_on_aircraft_ratio <= precipitation then precipitation_direction = -1 else precipitation_direction = 1 end if precipitation_on_aircraft_ratio > 0 then delay_precipitation = precipitation + (precipitation_direction * ((SIM_PERIOD / 6) * precipitation_on_aircraft_ratio)) elseif precipitation >= 0.01 then delay_precipitation = precipitation - (SIM_PERIOD / 3) * 0.1 else delay_precipitation = 0 end end function after_physics() precipitation = delay_precipitation end Now I could achieve the following result: But I feel it is a waste of resources to run extra xlua scripts for such small things like smoothing the change of the intensity of the precipitation. Does anyone of you have a good idea how to do this in fmod without external scripts? Thank you very much and best regards Philip

Please not! I see this as a great feature! The switches remember their position! As in reality the switches are in the position as you left them last flight. This is very cool! Please don't change this!

if you use a button for "hold brakes regular" and push this button while engage the parking brake via the normal X-Plane command it should work! You need to hold the brakes (with rudder pedals or with button) while engaging the parking brake (with button or with knob in VC)

Thanks for your hard work! After installing my GPU completely new with the newest driver (uninstalled completely with DDU before) i can't reproduce the crash at the moment... If the crash happens again, i will try without my plugins to see which one is causing the problem...

Now will try again with updated (new) drivers...

Hi, just ran into the same problem... first flight on XP 11.34. Otherwise nothing changed... i do have only one monitor. Log.txt TBM900_Log.txt

Hi, i changed my pedals lately. And coudn't use the breaks also! First i had some saitek rudder-pedals with breaks on each pedal. But i was switching to new helicopter-pedals without any break on them. I guess X-Plane keeps the old settings for each controller (once plugged) stored into the preference files. This is something good because if you want to change some controllers (i do have an Saitek Cessna Yoke for Planes and an Komodosim Stick for Helicopters) you can just plug one out and the other in. X-Plane just remembers all buttons and axis per controller. It may be true that your custom code tries to reads the X-Plane controller input but only looks at the axis x-plane did first bind to the brakes (even if this controller is unplugged)? In my conclusion X-Plane can assign many axis to breaks and does not delete this bindings if you unplug this controller. This may be the problem with the breaks. Some workaround for your custom code could be to watch all axis with breaks assigned and only uses the highest value... After deleting all joystick preferences and all custom per plane preferences i did recalibrate inside X-Plane and set up all my buttons again and now the TBM behaves as it should! Regards and a big thank for this great plane!! Philip

You have the "show clickspots" in X-Plane enabled! Sometimes this options are changed after an X-Plane update. You have to uncheck this option in the X-Plane settings...

+1

XPUIPC is working fine with the IXEG for a long time now... (as Jan stated right above your post! We are at version 1.0.7 now and there was a XPUIPC update to work with IXEG 1.0.0 (!!) and then the IXEG update since version 1.0.1 to work with the new and old XPUIPC version)

But you can assign all the numpad numbers for this views and "cycle" through your numpad keys...

As far as i can see: All right in you picture. Where is the problem for you? It seems you are not close enough to the NDB1... so you are not receiving it...

Do you mean the LOC or the GS? If it does not capture the LOC: maybe you did not turn in the right course?

Or do you just have some chanced Skytextures (Skycolours)? I did use the Aerosoft Skytools and had some problems with changing lights in Cockpit if the Weather changes. After going back to the default X-Plane Skycolours all went fine. (I did keep the Skytools-Clouds.. they do make no troubles for me at this time...)

Ich glaub, er meint einfach "Erbsenzähler"...