Jump to content

Ubbi

Members
  • Posts

    80
  • Joined

  • Last visited

Everything posted by Ubbi

  1. 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
  2. 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!
  3. Ubbi

    How to brake.

    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)
  4. 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...
  5. Now will try again with updated (new) drivers...
  6. 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
  7. 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
  8. 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...
  9. 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)
  10. But you can assign all the numpad numbers for this views and "cycle" through your numpad keys...
  11. 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...
  12. Do you mean the LOC or the GS? If it does not capture the LOC: maybe you did not turn in the right course?
  13. 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...)
  14. Ich glaub, er meint einfach "Erbsenzähler"...
  15. However a tipp for all guys/girls: you can safe you old preferences and copy and paste all your assignments with a editor like notepad++. When resetting the prefs i do keep the X-Plane Calibration.prf and X-Plane.prf in a separate folder. After deleting the prefs and rebooting X-Plane i replace the X-Plane Calibration.prf file with my old one. Then i open the new X-Plane.prf in notepad++ and replace all the _joy... lines with the lines from my old pref file. So i don't have to assign them all again. If you do want to keep your keypad buttons too you have to keep the X-Plane Keys.prf file too and replace the key assignment inside the new file...
  16. Hi and thanks for the Tipps! Regarding the TAKEOFF REF page: that's really weird... i did reset my preferences only a few days ago... but doing this again was a success. I did a before/after test. Before deleting the prefs the page did not show up, after deleting the prefs the page did work as desired! However a tipp for all guys/girls: you can safe you old preferences and copy and paste all your assignments with a editor like notepad++. When resetting the prefs i do keep the X-Plane Calibration.prf and X-Plane.prf in a separate folder. After deleting the prefs and rebooting X-Plane i replace the X-Plane Calibration.prf file with my old one. Then i open the new X-Plane.prf in notepad++ and replace all the _joy... lines with the lines from my old pref file. So i don't have to assign them all again. If you do want to keep your keypad buttons too you have to keep the X-Plane Keys.prf file too and replace the key assignment inside the new file... After doing this the B733 is working still as it should (TAKEOFF REF is showing up) and i kept my assignments. Regarding the Lights: i don't have any plugins like RTH running. I did use alternate sky colour textures. I reverted back to the original sky-colours via the X-Plane installer. I will report back if i ever see this lights again with the original files. Thank you for your help! Regards, Philip
  17. It seems you have no fuel! Get some fuel into the wing tanks and the APU will start fine.
  18. Hi again, now i managed to recreate this without the Weather-Plugin. It seems some of the B733 lights are using some of the sky-colors? I did change the skycolors (Aerosoft-Skytools) so mabey it is the fault of the new skycolors... Here is another Video now without any weather-plugins: Weather and Light2.mp4
  19. Hi, using great 1.0.3 today and all is fine (cant open the Takeoff page in FMS but i thing this is already on your list). But now i am going through the night and there is a strange behaviour. If i use "FS Global Real Weather" to inject the weather to X-Plane some of the B733 lights are turning dark to around 30 %. I was not able to reproduce this by changing the weather by myself or by using XPs own realweather... If the lights are dark i am able to change the brightness via the turning knobs but only within 0% to 30 % of the normal brightness. Here is a Video about that. The lights are going dark when "FS Global Real Weather" kicks in and are going bright again when XP itself creates the weather file... Weather and Light.mp4
  20. And you operate the Transponder with the standby-auto-off switch on the right side of the transponder. If it is set to AUTO like in your shot, the transponder will only start working if airborne...
  21. For me too. I did have some soft crashes with v1.0.0 but never a crashing X-Plane or a CTD. Since 1.0.2 i had no issues! Flying a lot in Switzerland, the Northsea (EDDW, EDDH, EDXW) without problems. Philip
  22. Hi Jan, this one was a hard one (at least for me) but i "think" i have found the issue! After a while of using X-Plane i noticed the following: these little stops (not the heartbeat every 2 secondes but the ones with more time in between) are not only with the IXEG B733 but also with all other planes. But i did only noticed them annoying with the B733 because of the sound "cracks". Other aircraft with these little "pauses" do play the sound through so i don't noticed them. Now the searching begun! After a lot of trying i did found this for me. If i do enable the "send data to laminar" i get the stutters with "soundcracks" but if i don't enable this, the sim runs smooth without any stutter for me!! @Litjan you said you also have these stutters on your laptop but not on the other machine. Could you check if you do have the following button enabled on the laptop and disabled on the other one? Than we would have proof of my finding!
  23. Ok. First one is very easy. Your Altimeter ist set to 1013/29.92 Air-pressure. You have to turn in the real (sealevel) Airpressure according to the real Weather at Hamburg to set the altitude right. As long as you are on the ground, it is very easy. The elevation of EDDH (Hamburg) is 53 ft. So you have to turn the black BARO knob until the altimeter reads 53 ft. Now you also know the outside air-pressure by reading the to baro setting numbers. (if you are in the air you have to ask ATC about the pressure setting or listen to the ATIS of a airport nearby) The second is a lot more to do. You need to fill some informations into the FMC so it can calculate some informations for the rout and also takeoffpower and so on. (thats why the N1 numbers at your second picture are missing). The FMC needs to know the weight of the airplane (without fuel but with passengers and other loading). It is called the "zero fuel weight" -> ZFW. You can see the numbers in the ground-service-menu and have to put it into the FMC where ZFW is written. Now the FMC will write the GW itself. Now you can put in a number at RESERVES. This is how many fuel you want to keep minimum at the end of the route (to go to the alternate or something). CRZ ALT means the crusing altitude you want to fly at. And then you can switch to the N1 Limit and leave all as it is. Now you should get the missing numbers... Philip
  24. No! I did Never User Skymaxx or Soundmaxx nor Fly with lua or other enhancements. I do use the Aerosoft Skytools which do change the Cloud shaders, Coudtextures and Skytextures. But this grafical issue did come with the new B733 from IXEG. Regards, Philip
×
×
  • Create New...