We got a new video from World of Aircraft: Glider Simulator and are asking for some alpha/beta testers! Check this post.

 

Jump to content

mwa05

members
  • Content Count

    35
  • Joined

  • Last visited

Community Reputation

7 Neutral

About mwa05

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

1644 profile views
  1. Thank you for this livery. If you want to update the flight deck registration decal with the SELCAL, the SELCAL for this actual aircraft is CE-FS. Regards, Mark
  2. Thanks Hanse, that makes sense to me. Long gone is the day the Purser would enter the flight deck and turn over a card on the centre console that said “Cabin Ready”. 😀
  3. Thank you for the tremendous response and pointing me in the right direction. I appreciate it. And thanks for taking the time to move the question to another area! After googling and searching hundreds of old threads, I was able to find the sound.xml in the AB_Systems folder and I could “read” what was required and I have now been able to get the announcement to play (RWY Turn Off On, even though we would not use that light at that time in my airline). I have not been able to work out what is required for the “Captain, the Cabin is Secure” announcement after doors closed, if I could impose on you and ask what are the conditions for that? I seem to meet what is required in the .xml but no joy.
  4. Gents, What are the conditions to get the safety demonstration to play in the A330? I am on the latest version and can only ever recall it playing once, and I have had the airplane since the day you released it. I get all other cabin announcements, but for the safety demonstration. I must not be following a strict procedure to kick off the script (I use the checklists and prep procedure we use at work). What are the conditions to set it off? Thanks, Mark
  5. Just to report back in, I got a PM from another member who had the same issue. He said he resolved it by uninstalling the aircraft, downloading a fresh installer from their account (he said that the original as released may have had an issue not completing the installation) but before installing, uninstall the Microsoft 2015 x64 distributable. A new one will be loaded by the installer. Reboot the computer then go ahead and install. So I did all of that and viola, the issue is fixed. I will still get the ‘make a video’ lesson though 😎
  6. Hi Dave, I am not sure; I have never done so and don't even know where to start. I will ask one of my 8 year old daughters (if I can get their head out of You Tube watching Ninja Kidz TV). I'll see what I can sort out when I am back home. Kind regards, Mark
  7. Hi Dave, I have no FPS issues, my system maintains 30FPS locked. The lowest recorded on the last flight I did (WSSS-WADD) was 26.4, average 30.0 as per the FSUIPC log, so it is not the FBW <18FPs issue. I already eliminated that from my enquiries. I should have mentioned FPS in my opening remarks. Kind regards, Mark
  8. I have an issue which I have not been able to solve yet, which is as soon as the aircraft is airborne it oscillates in pitch and roll and this continues even once LNAV/VNAV A/P is engaged and really only stops at cruise (but still is slightly there). It then repeats all the way on descent until landing. If I go to an outside view, the ailerons and elevators are going up and down by themselves creating the ongoing pitch and roll movement. It is not weather settings (I use HiFi ASP4) as I have tried with no weather (default P3D) and it is still the same. I have version 1.0.0.3. It is not controller spikes nor is it FSUIPC (as I removed the .DLL to test). The aircraft is pre-flighted and prepared properly; I am very conversant (away from the FS World) on how to fly an A330. The aircraft is in the default location (your Documents\Aerosoft folder). It was installed properly (anti-virus off, ran installer as admin, re-boot after install, keeping anti-virus off, launched P3D, loaded A330, waited for it to initialise, closed P3D, waited for P3D to fully close, then ran the updater and then re-booted the PC again). I fully uninstalled and then re-installed - still the same behaviour. The product is literally as "out of the box" - I have not even installed a livery yet. Windows 10 Pro, i7-6770K @ 4.5ghz, GTX1080ti, 32GB RAM latest P3Dv4 HF2 (clean install), Logitech Extreme 3D Pro, A330 settings as per Documentation Folder Vol.1. I have another developers Airbus product (no issues), and a variety of Boeing products (no issues) - I mention this only because I bought the A330 on 09DEC19 (so I have had it for 8 days) and I have spent those 8 days attempting to the solve the issue myself but have eventually done everything I can think of in so far as it may be an issue on my PC, thus why I am now reaching out for further ideas. I do note that there is no specific report that I can find that sets out this issue. Kind regards, Mark
  9. Thanks Mathijs, if that is “normal” then no issue, there is nothing for me to hunt down and solve.
  10. Hi Mathijs, Fair enough, except in doing so, I don’t know whether I have a problem or not as he is basically Chief Beta Tester on the Forum and his screenshots are different to what I (and other users) see “out of the box”. So in trying to ascertain if I have an issue to report or not becomes inherently difficult. BTW, I love the product and what you have achieved but it is hard to baseline and report issues if “staff” are showcasing other than “out of the box”. Kind regards, Mark
  11. Gents, I have my A330 in Turn Around State and every time I load the aircraft I get the engine shutdown sounds twice... about 45 seconds apart. I have not done anything except launch the scenario and wait (9V-SSB at Gate F30 WSSS). Regards, Mark
  12. Hello, Has anyone picked up on the fact that there seems to be two different external views? There is the view as posted by Josu in post #8 and there is the view as posted by DaveCT2003 in post #5. They are completely different. I get the view as posted by Josu and cannot by any means get the view as posted by DaveCT2003 even if I turn off all views by MCDU3 re boot and turn back on. There is an issue here which has not been clearly and succinctly identified. Regards, Mark
  13. Just to update. I have been on version 1.21 with the last hotfix. I upgraded to 1.30 with hotfix E yesterday. Today, I spent hours doing a complete reinstall of the Buses and stopped at v1.30 ( no hot fixes). The issue remains. I then applied Hotfix E and the issue remains, across all 4 variants. I consistently get LVR CLB flashing during the take off roll, regardless of whether it is a TO/GA or FLX detent setting. I get an ECAM message "Throttle not set" and the FMA does not update to either TO/GA or FLEX, rather it displays MAN THR. The ATHR does not seem to engage with the displays until it is put into the CL detent passing the acceleration height. However, looking at the engine displays, it seems as if the aircraft is conducting a full or FLEX take off, depending on which one I have selected but the FMA's are out of sync until you pass acceleration height and move the throttle to CL. After that, the aircraft operates normally to shutdown. Regards, Mark PS - this is FSX Deluxe, departure 22R Helsinki Vantaa, with or without FSGRW weather.
  14. I follow IFRIP from Vol 6, I am sure it is not that.
  15. Hi Team, I have a good FSX install, quite clean, and have the A318/19/20/21 download bundle version 1.30 with hotfix "E". With all models, I get LVR CLB with either a TOGA or FLEX take off as soon as I move the throttle to the FLX or TOGA gate during the take off roll - I do not get the correct FMA annunciations - I get MAN THR FMA with a T.O inhibit message with LVR CLB flashing. I have properly removed and reinstalled the product, and then reapplied the hot fix to the latest version and it does not fix the issue. I am usually able to sort issues out myself however on this occasion, after 3 days trying to correct it, I can't. I am following the correct set up procedure and I have not had this issue before - 1.21 worked well for me. I purposely did not download 1.30 until the hotfixes became stable and I am at a loss what to do other than to reinstall 1.21 (which I kept), which was quite flawless for me. Can anyone verify that this is a common problem? I am reasonably comfortable that I know what I am doing - but cannot solve it on this occasion, as the issue is consistently repeatable across all 4 variants. Thanks, Mark
×
×
  • Create New...