• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
fdm79

Localizer not aligned and some other issues (Nevertheless, a magnificent add-on)

Recommended Posts

Hi,

Since July, I abandoned FSX for good after 11 years and now I'm a happy P3D V4 user...

Since I bought this incredible add-on (3 days ago), I've been testing it and so far, I'm loving this Bird a lot ! 

It has an enormous potential ! Since I had some experience with the PMDG MD-11, it's been quite an easy task and joy to get familiarized with the 717 !

So far, I haven't encountered most of the bugs reported except the abrupt yoke movement when flying over fixes and also, when intercepting a route using LNAV, the plane goes almost 90 degrees to interception (feels almost like a default FSX/P3D) unrealistic interception. I found it also, a bit heavy on the system (A bit more than PMDG 737/777/ 747, which are considerably more complex, for example). I've had some CTD with the 717 as well, but hopefully, it will be more stable in the future since it's still BETA for P3D V4.

The real show stopper for me so far, is the ILS and Autoland... NONE of the ILS landings I've performed so far, the plane landed on the center of the RWY.... I don't mean by a small margin but a quite substantial margin !!! (I forgot to hit PRTSCN all the times to show here). 

I remember I found a post somewhere here regarding this issue, where someone says that we should have AFCAD updated but this is pure non sense since EVERY other add on (and I own almost all of the airliners like PMDG 737,777,747, AS CRJ, and waiting for AS Airbus) land perfectly centered using P3D V4 or the FSX as they are !! 

Except for this issues, I'm really loving this plane and believe TFDI has a great potential ! I hope this company becomes a parallel company with PMDG ! 

 

 

Fabio Darolt

 

My system specs:

i7 6700K @4.5GHz 1.25V - Corsair H80i GT 

AsRock Z170 OC Formula 

32 GB Kingston HyperX Savage DDR4 2800MHz XMP1

ASUS RoG Strix Nvidia GTX 1080Ti OC

SSD Corsair Force LE - 500Gb

SSD Corsair Force LE - 1Tb (P3DV4 Installed)

SSD Samsung EVO 850 - 2Tb 

1 HD Segate 2Tb

Corsair HX1000i PSU

Monitor ASUS PG348Q Ultrawide

Saitek X52 Pro

Windows 10 64Bits

 

 

 

 

Edited by fdm79
Rephrase

Share this post


Link to post
Share on other sites

Crazy thing is : 

After I had this last misaligned ILS land, I parked the plane, turned everything off, then, set panel state as "ready to fly", inserted on FMC as Flight Plan "KSLC/KSLC" and chose again I16R for ILS... Then, I Slewed the plane with the RWY to check the Localizer indication and it was perfectly aligned with the center of the RWY... 

Then, I even went further and dropped the plane using Slew mode to intercept LOC and GS... And.... It landed perfectly aligned.........

Very confused here ! :S

Share this post


Link to post
Share on other sites

Another non related "ILS misalignment" feedback.

After I turned on the Hardware Rendering option, my CTD are gone (at least, so far, testing at the same conditions that I had CTD when the option was "off"). Performance has also increased a little bit.

Share this post


Link to post
Share on other sites

Excellent! The hardware rendering seems to have a varied effect for everyone. Regarding ILS deviation, I'm going to be looking at this over the next few days to see if I can figure it out.

Share this post


Link to post
Share on other sites

Thank you, guys ! 

Regarding HW Rendering, I found it by coincidence, reading a topic here where someone asked about it ! I believe many people will have the same issue not finding it because most people won't try to scroll the screen :D and I also think that what helps me with this is the 1080Ti ... It would be a waste not using it even further. 

And, the LOC thing, I've been reading what I wrote and maybe I haven't expressed my issue quite precisely... It's not about the Localizer being misaligned but it's actually, the Loc not following the magenta line very accurately. You can see on my pics that it's a fraction of a dot off the center ! 

However, I must say, this plane has been intriguing me a LOT.... last time I flew with it, (2 days ago) from Dublin EIDW to Lisbon LPPT, strangely, I had no yoke violent movement at any point flying over waypoints and............... performing a full ILS on RWY 3R (LPPT) was perfect and it followed the magenta line totally centered !!! 

I think this plane is alive and it's moody LOL :D

 

PS - To answer Joshua, 

Nope, no add on at all in KSLC itself but I have ORBX FTX Global, North America LC, NA Central Rockies, NA Northern Rockies, NA Pacific Fjords, NA Pacific Northwest (Actually,I own all ORBX LC and Areas in Europe, Australia and South America. I don't have VECTOR). I have both California and Alaska as well but ended up uninstalling these last 3 because it's too heavy on large airports like Los Angeles and Anchorage. 

Edited by fdm79
Correction

Share this post


Link to post
Share on other sites

I'm glad I asked about HW rendering. Appears there's more than a few of us who are incompetent. 😂

I also have a 1080ti and experiencd very nice performance with it set. I also have not (so far with only limited testing) been unable to reproduce a crash on view switch. 

Edited by odourboy

Share this post


Link to post
Share on other sites

Indeed... Many people still don't know about the "hidden miracle" lol. Jokes apart, I don't think that setup is very intuitive to find since many people only found out due to the topics here and maybe not everyone will really benefit from it except the ones with very powerful vídeo cards. I don't believe that the 1080Ti uses it's full potential for P3D. 

As for the Localizer issue, it still remains for me but it happens in different ocasions and in different ways, which makes me more confused and without an idea of what could be the cause.

One thing I DID notice is: As I use P3D default ATC, I always approach using the default vectoring system. And, if by some coincidence, the APP throws me far way from the runway for an ILS, the plane has more time to "correct and adjust" the localizer path and hence, more chances for a good aligned land. If the ATC throws me too close, there will be no time for the "adjustment" and the plane will surely land off the center. By my so far experience, it's weird how the LNAV is very sensitive to follow the track but the Localizer has been not.

Share this post


Link to post
Share on other sites

Trying to capture the localizer too close (Less than 1000ft AGL) will always cause issues for approach. The AP LOC algorithm is completely different from LNAV algorithm. WIth LOC, you get a triangle beam that is way less sensitive 5 miles out when compared to being 1 mile out.  With LNAV, its a cross track error that is does not vary in sensitivity.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now