suavi

Hello Jacob, The following sequence is the one I found the most convenient and keeps me away from frustrating surprises : 1. Create a flightplan including STAR using vroute and aivlasoft. I don't have sid included in the plan because sometimes sid waypoints create troubles with radar contact 2. Load the plan in as2012 and load weather textures. I use windlock feature of as2012 to avoid tailwind landings and conflicting ai traffic. 3. Start topcat, arrange the load balance 4. Calculate the fuel in vroute using the payload in topcat and altitude in the plan. 5. Start radar contact, load the plan, choose altitude restriction in parameters so that rc leave me alone while flying sid as i wish. But if i will fly a long sid which i will still not be heading to my first route waypoint after 80 miles from the runway another preperation is necesssary. 6. Start fsx and load ngx of the day 7. Connect radar contact and verify the active runway 8. Calculate take off data in topcat 9. If i want to fly star, i simply request a full ils or vor approach after the approach controller tells me to expect vectors then it leaves me alone until the final approach. Hope you find this flow useful, the key points are not including sid in the plan and use windlock in as2012. Best regards, Suavi Akar

Guenther,Thank you. I didn't imagine that it will work in that way. So, it is not an issue any more for me. I noticed your posts about the failure model while searching for the random failure thing. Let's hope that someone has noted it for future releases. Best regards,Suavi

Hello,I have started to use random failures as a new challenge and noticed that random failure setting resets itself at every session start. I set it to "yes" and frequency to 2, i get a minor or major failure during the flight beginning right after the setting change, however, i found it reverted to "no" at the next FSX startup.I am aware that this setting is livery specific, i checked several times and sure about this is how it works at the moment at SP1b. I reviewed the introduction manual and couldn't find any information why it is programmed it this way. So, I will be delighted if somebody give an explanation.And I have a future development request about failure settings: Moving service based failures parameter from livery specific category to sim options category or at least let the user decide to select the category according to his/her preference. Because I think some of us use different liveries and choose one among them regarding the route selection for the session. This makes hard to reach 250 hours service time even for a frequent simmer like me (approximately 25 hours a month). Although the current application is more compliant with the reality as failures specific to aircraft in reality, my suggestion will improve the challenge and enjoyment of simulation.Best regards,Suavi Akar

Hi, Do you still see brakes warnings on your screen? If you see, check the dead zone and sensitiviy of the brake axis. It was happened to me as well after a system reinstall and found the clue in forums. I am away from my system, so, i can't tell the correct settings at the moment. But of this is the problem, then you may found them in the forum searching for brake release.Hope this helps,Suavi Akar

IT IS SOLVED. Almost simultaneously with our discussion about Turkish settings, Chris and Damian found the reason by questioning the same detail and fixed it. Thanks to the development team for the fix and Doruk for speaking out our common point.Best regards and İyi uçuşlar,Suavi Akar

Good point. I have noticed too. Most probably all of us use Turkish locale settings. I remember that I had to switch to En-US to be able to create a new voice pack in the past. So, locale settings may cause some unpredictable results, however, with my very limited knowledge about fsx internals, it is hard to imagine a relation between locale setting and texture graphics creation. It might be a good idea to update my open support ticket with this detail. Perhaps Chris and Damian could find one.Regards,Suavi

Hello,I reinstalled AS2012 and beta fix, also overwrite Cirrus folder with the files Chris sent me in response to my support ticket, unfortunately nothing changed. Revert to my work around and continue to wait.Best regards,Suavi

Hi Chris,I didn't reinstall. I am going to reinstall and let you know the result.Suavi

Hello,The beta fix didn't work for me. I always test the textures at the same place and same time i noticed them. They are still there. I decided to use fsx default cirrus textures instead of as2012 cirrus textures until hifi team develop the final fix. I restored the default textures, then uncheck the box in graphics/install options/ cirrus and installed the wx influenced textures. Everything seems quite impressive and no surprising grey foils around.Best regards,Suavi

Hello,Don't rush to reinstall FSX. Damian and Chris are working on it. I think they are going to find a less painfull solution.Best regards,Suavi

Hello,I tried again, this time I added STAR procedure at the gate and see the same curly STAR path again. I corrected it by creating a direct link from RTT to OEV21 as Leffe proposed above.Regards,Suavi Akar

Thank you guys. I have done what you have told, I have edited the altitude and speed restrictions of TULSI waypoint which is the initial fix of STAR. I thought this would not cause any problem as I have already been flying at lower altitude and slower speed than the planned values for it. I imagined that it would provide better slow down performance between TULSI and OEV21. But you are saying that it complicates everything and FMS somehow needs a longer path than physically exists, to descend and decelarete between these two fixes. I don't know how it could be possible in my particular case, normally I would expect to see a DES PATH UNACHIEVABLE message in CDU and VNAV disconnect instead of nice round curves in ND. I have been persuaded in another long discussion in another forum that FMS sometimes does strange things in 737. This could be another example among them. I will try it again and update.Best regards,Suavi Akar

Hi Leffe,Thanks for the reply and suggestion to manage the situation. I uploaded higher resolution versions (1280x960 when you click) of the same shots. You may see the legs page on the captain's CDU at the first picture. As you will see it looks pretty normal. However the path drawn in ND has the interesting curly shape. There is something wrong in this STAR causing a mis-calculation of the interception. This has never happened at LOWI before and hasn't been appearing in other STARs or routes, I have flown so far. Therefore I consider either SP1b or AIRAC 1113 cause it. By the way I tried to delete and redefine the arrival procedure but it doesn't work. The way I followed is to switch to HDG mode until LOC capture. If you mean defining direct legs between TULSI - RTT and OEV21, I will give it a try next time, it may work as well.However, my purpose in starting this topic is to understand if other LOWI fans have experienced the same with other versions (mine was 600, how about 700, 800, 900) and bring the detail to the attention of PMDG team.Best regards,Suavi Akar

Hello,I have seen this weird STAR path in my last two approaches (yesterday and today) to LOWI. As you will see in the attached pictures FMS calculates the leg transitions with turns at the opposite side in well known TULS3A STAR with RTT transition on LLZ 26 approach. If you leave the plane at LNAV mode it actually tries to follow it. I checked my log and noticed that I haven't flown that approach since Nov. 5th. Since then, I applied SP1b and Navigraph cycle 1113. Where do you think it comes from?Regards,Suavi Akar

As I have written in "black sky" topic, have the same issue. I think i sorted out Shader3. Because, i uninstalled it experienced again with 2k textures. Also checked my system performance during the incident, there were no memory shortage. My graphics card (gtx460) was using 420MB of memory, ie 42%.I am going to contact support department with the details. Regards,Suavi Akar

Hello,I think I have the same issue here. I am using Shader3. I have screenshots but couldn't attach. In may case I see gray shaded (semi transparent) horizontal (parallel to the earth) rectangular patches tangent to the cloud layes, these are four patches overlaying slightly on each other.Regards,Suavi Akar

Hello,I did my first flight after SP1 installation on LFMN - LOWI with Austrian OE-LNO livery. As all LOWI NGX fans know this is a place to experience an IAN approach. I noticed that something has changed in Arrival selection and Approach reference pages in the aspect of IAN. After SP1, G/S ON/OFF options in Arrival and Approach reference pages are only available when an ILS approach is selected. However this option was always available in both pages regardless of the approach method and it was like a magic switch of creating a G/P on every approach. I even remember a topic about using FMC drawn G/P on a visual approach by the help of this option. Now, I understand that it is replaced by a semi-automatic procedure which initiates IAN when an where applicable. Because my approach turned into IAN after establishing on LOC course and pushing APP. So, I just would like to be enlightened about which case is complying with the real life.Suavi Akar

I have the same, sometimes i get a fully black screen on CDU1 but there is a bypass. Click on the screen of CDU1 (showing the message or blank) to get the magnified CDU view, and click again on the same clickspot to revert it back. Everything will be OK.Suavi Akar

Hello Tim,If i remember correctly, even you turn off the fuel pumps, engines can be fed by suction feed in NGX. Therefore, you should turn crossfeed valve on while turning off the low side pumps to overcome the fuel imbalance. This might be the explanation of fuel level decrease after turning fuel pumps off.EDIT : Sorry i missed that you still have fuel in the center tank and center pumps are on. In this case my scenario is not valid of course.Regards,Suavi

Hello,I suggest to put uiautomation.core (not the default one in system32) in fsx main folder. I have upgraded my system from Vista 32 to Windows 7 64 due to get rid of OOM errors. I applied only officially supported tweaks and recommendations including Bojote fsx.cfg tuning and nvidia parameters in general forum. After upgrade the only issue i have was the well known ctd due appears after several right click menu selections and it has immediately been solved after putting the old uiautomation.core in fsx main folder. If your issue is different than right click thing, all i can tell you just change your set up complying with introduction manual.Hope this helps, regards,Suavi Akar

Hello,I am quite new in 747 simulation. Because of that I made a thorough search in the forum when I first hit this problem, and found that many of us are complaining about this strange behaviour, and only remedy is to tweak the weather by FSUIPC. Indeed after installing FSUIPC registered copy and supressing the weather changes as advised I partially solved the problem. However I noticed another dimension which I haven't seen in the forum, of the same problem. I noticed that if the crosswind exceeds 80 knots (steady in terms of speed and direction) the problem still occurs. The plane starts to make excessive banks to either side and never comes to a wings leveled situation therefore flies on an S pattern instead of keeping the track. Worse than this, if the windspeed exceeds 90 knots it makes 180 degree or more heading changes like a cat trying to catch its own tail. At the same time it also exceeds the banking limit as known already and becomes totally unstable. While trying different ways to recover, I found that the quickest and safest method is to:1. Select HDG HOLD mode to come to wing level situation whatever the heading it is.2. Set the bank limit to 5 - 15 degrees.3. Switch to HDG SEL mode and take the plane on the track by commanding slow heading changes 4. Keep the plane on the track by the help of HDG SEL knob until the wind slows ie. make a semi-automated flight.The interesting point and question here is Why LNAV cannot cope with high crosswinds while HDG HOLD and HDG SEL can?I appreciate any comments.Suavi AKAR