Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. parsec71

    Check you audio files guys

    Well, perhaps the OP will enlighten us... ...I most certainly could not find any major, show-stopping errors in the files I checked. And I've never had any sound issues with this great little bird.
  3. JGregory

    Check you audio files guys

    @parsec71 Nothing you stated seems to align with the comment from the OP about these files causing "major problems". And, since we have not had ANY reports of audio problems, I'm still curious just what the OP meant by that.
  4. parsec71

    Check you audio files guys

    This post made be curious, because (amongst many things) I'm also an audio professional with my own home studio. So I just had to take a look at the files... I will give one, friendly advice: Keep the files standardized. There's a lot of different bit rates and sampling rates in use, in addition to mono/stereo files. Depending on the audio engine, that will mean a resampling must be performed before the audio can be mixed and generated by a system's sound driver. This will take up processing time. I guess the difference in files is done with space saving in mind, but all these files are so short in time that they can all be created in CD quality (16-bit, 44.1 kHz).
  5. mjrhealth

    Problems with MU-2 v1.8 on xp11

    Thanks cant wait
  6. XPJavelin

    Speedy Copilot

    I am looking for something simple in my code. It was very convenient to read the FCOM and just translate in a few command lines, in a very straighforward way. I am not sure I am ready to sacrifice simplicity for human delay of actions. I like that way of doing however. I will think about it. In the mean time, I was thinking of implementing a GUI menu to set options (F30 of F40, with or without APU...)
  7. XPJavelin

    Speedy Copilot

  8. Goran_M

    Check you audio files guys

    I'm not really sure what the point of this post is. Normally, when speculation is involved, it's common practise to send a private message asking for clarification on what we did and why we did it. Not come into our forums, throwing your weight around with something about having 30 years sound experience, claiming we MIGHT have problems. The Saab has been out for 5 years, and no one has had any issues with sound. You haven't listed your experience. What company/companies you have worked with. Your qualifications. What software you used. Anything that would corroborate your claims of experience. Seeing as you have already made it public, how about itemizing everything you see that WILL cause problems, (not MIGHT), and listing exactly what problems they will cause. Apologies if I seem rather blunt, but I'm not used to people telling me I MIGHT have problems with my product, after 5 years in the community, because of something you might have found. We're very receptive to feedback and criticism, but we need specific, factual details. We can't follow up on "maybe".
  9. Ben Russell

    Check you audio files guys

    Like what? I have no open bugs against this issue. Genuinely curious. Share your wisdom.
  10. RWY36R

    Check you audio files guys

    You really need to check and test all the audio files for the Saab 340. They could cause major issues. Make sure they are in the proper wav format and test them. Not sure what you are using to create or test them. But they have issues. I've edited and produced audio for over 30 years. So I do know a little bit of which I speak. I own the Saab 340 and just don't fly much anymore. But I thought I would let you know in my latest scan of wav files to check for errors in the X-Plane directory your's are the only ones that spit out errors. And that's not a good sign.
  11. Yesterday
  12. jfjoubert

    Speedy Copilot

    No, I don't drink and code...
  13. korkiley

    P.180 Avanti II - Support

    Hi Marcin, I haven't flown SusiAir for quite some time. This new update will be a good excuse for me to spend some more time flying for them! Hope you are doing well! Kor
  14. blocks_off

    Speedy Copilot

    Hi @jfjoubert You are correct with what you say and it is great fun testing when you move a switch to a different position, then it moves it back but i digress..... I do not hear repeated clicks, there are a few steps where I check for the state and then only set if it is not in the correct position for that routine such as gear handle, start switches. I've had a quick look at your code, and as much as I like the randomness idea, I will park it for now Well done though with that achievement... did you drink a lot of your favorite drink whilst writing it ? Thanks for your reply and interest -Carl
  15. jfjoubert

    Speedy Copilot

    @blocks_off Correct me if I'm wrong but won't your code execute the same steps multiple times until the 22 seconds have passed and r_trigger_shooting_approaches is set to false? It should work if you conditionally check each item and only set it once like this: if os.clock() > r_trigger_start_time +1 then if w_acft_flap ~= 0.5 then w_acft_flap = 0.5 end end Otherwise you might end up hearing all the click sounds in the cockpit when switches are set to a specific position, even though they might already be in that position from a previous loop through the function. Anyway, it could work. I just felt like typing a lot of code...
  16. blocks_off

    Speedy Copilot

    Yes that is true of the code I posted earlier, but not if taking this into account i.e. it's part of a function as described here. As above
  17. XPJavelin

    Speedy Copilot

    The first thing I can say reviewing your code,you're not lazy !
  18. jfjoubert

    Speedy Copilot

    You're welcome @XPJavelin
  19. XPJavelin

    Speedy Copilot

    thanks @jfjoubert,I will investigate your work, in the mean time, I was working on a revision of my script to include after landing flow with and without APU. I also added altitude constraint for flaps retraction, compatible with the go around triggers, and runway Entry procedure is triggered by left inboard landing light instead of left outboard. Both as suggested by @blocks_off
  20. jfjoubert

    Speedy Copilot

    As promised... IMPORTANT NOTE TO ALL: This file is not a complete replacement for the original code from @XPJavelin. It simply shows a way of applying some randomness in the procedure steps. Please also note: The code was only modified for the PREFLIGHT Procedure (start with OXYGEN test switch) You can easily change the min and max time (in seconds) for the random delay in the code I re-enabled some of the datarefs and made some "readonly" to be able to do some conditional checks If you don't know FlyWithLUA or LUA or you don't care about the underlying code then wait for an official update from @XPJavelin This will only happen if @XPJavelin wants to incorporate this into his code @XPJavelin I did add comments as far as possible to the code so hopefully it will make sense. Shout if anything is unclear. IXEG_proc.lua
  21. Neftali

    Weight & Balance - CoG

    NIIIIIICEEEEEE ¡¡¡¡ Thanks ¡¡
  22. jfjoubert

    Speedy Copilot

    Soon it will be released... I'm just busy testing to avoid a red face.
  23. XPJavelin

    Speedy Copilot

    Mmm Well said.
  24. jfjoubert

    Speedy Copilot

    The problem with the above code is that you cannot have it in a function which is only executed once... you will never get to most of the steps. The current code has a conditional check for PREFLIGHT to see that preflightproc_trigger == 0 and beforestartproc_trigger == 0 and OXYTEST == 1 Now this means that the actual code inside the function will only execute once. On the second pass all the above variables will not meet the condition again. So you will never get to os.clock() > r_trigger_start_time + 4 and further. So one possible solution is to change the conditional check to make sure that the code inside the function is repeated until all steps have been completed. This is what is adding to the clutter because now you have to make sure that you don't repeat a previously executed step and and that all steps are still done in the right order. Anyhow, I will upload my lua file (once done) with my modified code for the PREFLIGHT procedure and you guys can then have a look to see if it's not too much clutter in the code.
  25. marpilot

    P.180 Avanti II - Support

    We both fly this in Indonesia for SusiAir VA
  26. blocks_off

    Speedy Copilot

    Thanks - and with all the thinking my brain can do, I do not know why i've done it as per my original note. Just putting some more lines together in my lunch (for my shutdown routine) looks much neater per your suggestion :- (I've intentionally put the same time on some actions - I want my first officer using all fingers when he can! if r_includeIRS then if os.clock() > r_trigger_start_time + 1 then w_acft_irsL = 0 end if os.clock() > r_trigger_start_time + 2 then w_acft_irsR = 0 end end if os.clock() > r_trigger_start_time + 4 then w_acft_fuelLfwd = 0 end if os.clock() > r_trigger_start_time + 4 then w_acft_fuelLaft = 1 end -- leave on for apu if os.clock() > r_trigger_start_time + 5 then w_acft_fuelRfwd = 0 end if os.clock() > r_trigger_start_time + 5 then w_acft_fuelRaft = 0 end if os.clock() > r_trigger_start_time + 6 then w_acft_winheat_l_side = 0 end if os.clock() > r_trigger_start_time + 6 then w_acft_winheat_l_fwd = 0 end if os.clock() > r_trigger_start_time + 7 then w_acft_winheat_r_side = 0 end if os.clock() > r_trigger_start_time + 7 then w_acft_winheat_r_fwd = 0 end if os.clock() > r_trigger_start_time + 8 then w_acft_pitot_a = 0 end if os.clock() > r_trigger_start_time + 9 then w_acft_pitot_b = 0 end if os.clock() > r_trigger_start_time + 10 then w_acft_hydELEC2 = 0 end if os.clock() > r_trigger_start_time + 11 then w_acft_hydELEC1 = 0 end if os.clock() > r_trigger_start_time + 14 then w_acft_seatbelt = 0 if os.clock() > r_trigger_start_time + 15 then w_acft_beaconLIGHT = 1
  27. korkiley

    P.180 Avanti II - Support

    Ilias, Thank you for your great work. I'm really looking forward to this update. I also just discovered your blog. I haven't had a chance to read it yet but it looks very helpful and interesting! Kor
  1. Load more activity
×