Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Some problems I have after 10 flights or so. - I really really dont like that I cant ask for a different runway or different aproach . I thought that wont be a problem but it really is. And I dont understant why, even the default ATC let you chose those if you really want. - If I try to request engine start and only engine start I`m getting a cleared to align or backtrack the runway, I have no idea why. -When its asking you to call when ready to descent and you confirm will call when ready to descent the AI will interpret that you are ready to descent and give you a lower altitude. On the same note, if you asked by mistake (like me pressing first option when in climb) for descent the whole flight is bricked. I was 500 miles away of my destination in climb and asked for descent. From there all I was getting was a heading and a lower altitude. Had to fly offline rest of the way. -you ask for descent once and thats it. You cant ask again even if you are at the asigned altitude, you need to wait until you get further descent even if that is way late. -I got a visual approach and because I couldnt find the airport fast the ATC activated missed approach and even if by then I had runway in sight and was ready to land I couldnt tell that and had to go around. -Some of the time is a really good idea to omit saying your callsign. If I`m getting a new frequency just saying my callsign at the end lower the chance of being understood by 50%. If I readback only the frequency no problem almost every time. I`m kinda dissapointed because I feel that the state of the program now is in no way ready to launch. And I`m only speaking about the IFR part not traffic. IFR aproach has maybe a 50% chance of going okey and they said that part is mostly done and in 2-4 months will have traffic. Yeah, not gonna happen. Maybe in a year will have traffic if they will fix the current problems with approach and vectoring. I`m almost certain that they run out of money and they need to lauch something asap whatever the state. The poll was only to have an excuse when people will complain about the multiple bugs and missing features.
  3. Thank you for the well laid out suggestion For Twenty6. I mistyped I meant to type version 0.9.28+patch1...Thank you for pointing that out
  4. Minor Update 1.0.26.EA - Added Upgrade to Supporter's Pack option for anyone that has the base product and wishes to upgrade for only half the price. - Added ability to call established on an ILS approach. - Added the active runway as a UI info box to IFR clearances, even if it is procedure not to speak the active departure runway in the clearance. - Continued fixes for speech regcognition with a focus on "Runway Niner Right" and "Niner". - Many voice tweaks; added more Premium Voices. - Added new auto-Respond Character AUS Male. - Fix for a crash entering the options menu. - More fixes for crashes when binding buttons from a non-US keyboard.
  5. Nice. Thanks Mark. That was extremely easy with the included documentation.
  6. Since OP mentioned TTools, there is also AI Flight Planner, you can download it from fsdeveloper
  7. Today
  8. But where does it sit in the scheme of A340-300 FS addons? Black box / PSS Feelthere / wilco xworks Is it good enough to switch to MSFS now for A343 flights? (The bar is low, though at least Xworks is free!)
  9. Yes, TLOD controls far too many different elements in MSFS, including tree draw distance, on one slider. There is a chart that demonstrates the effect of different TLOD values on trees and a tweak to get tress to display further in the distance. I'll share those tomorrow evening once I'm back at my desktop PC.
  10. I was going to mention this. Btw, does TOOD affect tree draw distance? I get a fair bit of trees popping in on final approach. When TLOD is low (since I’m using AutoFPS. Sorry if it has already been answered in this thread. It’s a menace. I really hope it will be better in ‘24. At the moment it’s either crash damage off… or going missed…
  11. Whenever MSFS is not in focus, both FG (fps halved) and g-sync (tearing) are inactive. I sometimes notice terrible stutters as if something is stealing the focus from the sim. Alt-Enter has solved it every time. Also, with AutoFPS’ “on top” feature, FG will be active, but g-sync not. According to my experience.
  12. I didn’t intend to install it, as I saw nothing in the release notes that would possibly benefit the sim. But I installed anyway 🤷🏻‍♂️ I’ve not noticed any changes. Also checked both nvidia github and techpowerup for any DLSS updates. 3.7 still seems to be most recent.
  13. Don't need to I've run DLSS FG many times w/ the rate capped at 60 or 70 or 80 and there is no subjective latency so all of your or anyone's theory doesn't mean squat when there is no subjective latency experience. There is NO MOUSE SLUGGISHNESS. Get it yet? Nope? You're stuck in theory and not reality. You might see it on an overlay, but if it's under the radar it's irrelevant. Those worthless CFX captures completely corroborate subjectively exquisitely smooth animation. I first witnessed the animation well before I ever knew about CFX, and learned no other locking device matched either the subjective experience nor the CFX capture. You can believe whatever you wish but I guarantee you this does not apply to all users.
  14. Yesterday
  15. Guys, just to let everyone know that a few hours ago new official simbrief profiles have been added, for all the dukes they are named BE60, BE6G and B60T https://forum.navigraph.com/t/b60t-simbrief-profile-request/15662/12
  16. No, it's simply you and the others who can't feel the additional latency added. I was incorrect in one thing, it's not frame latency RTSS adds, also why your CapFrameX results are completely worthless in this discussion. It's overall PC render latency that is increased when you use RTSS with FG. For the casual user, it may feel smooth and the frame delivery is still smooth but there's absolutely a bigger overhead, ranging between 20 and almost 60ms! Exact reason why the mouse movement feels so sluggish. (Off-screen because nothing will capture the Nvidia overlay) FPS capped with Nvidia Control Panel; Capped with RTSS Front Edge Sync; And that will be sailing all over the place. And again, I will state this in bold; THE VERY DEVELOPERS of the program you keep peddling on this forum have said RTSS is not compatible, exactly because of the above; it adds a lot of latency and in other games, a lot of stutters; https://twitter.com/CapFrameX/status/1620511329416265728 They also suggest using Nvidia's control panel to cap; https://twitter.com/CapFrameX/status/1620514721534476288 A simple Google search will confirm RTSS is not compatible and is generally suggested NOT to be used with FG because it adds a lot of latency or in some cases, completely kills performance. It's universally known at this point. So before you post another worthless CapFrameX graph or quotes from your converts, install the Nvidia overlay and confirm it for yourself.
  17. Beautiful set, always nice to see a 747-8 in Action. cheers 😉
  18. Open Microsoft Store and go into your Library. "Get Updates." See if that solves your problem.
  19. Then something else is amiss on both of your systems as there is no subjective latency whatsoever. RTSS async is wretched, and no other locking schemes produced the subjective impression w/ edge sync does and that's not just my take. This 'as just moving the mouse feels like it's moving through molasses' is just flat out laughable. Not sure what's different for you and the OP, but none of that happens here, with or without FG. Here's another anecdote from someone who tried Edge Sync for the first time and there are others, using FG. I wonder what's different for you and the OP... >>Hey Noel, Hope all is well and that you are enjoying your new 4090.... RTSS FPS - 80 Front Edge Sync I just departed Liverpool airport in the Fenix with FSLTL and ran CapFrameX for 15 minutes, Overall I am pretty pleased. The smoothness is beyond exceptional locked at 80FPS. One thing I did stumble on is that when I enabled the NVIDIA filters it messed with my FTV so I turned them back off Quote
  20. Cant seem to find a fix that will let me set my HOTAS throttle all the way down without it going into the reversers in the sim. That would be fine if I had a detent, but I don't. Is there something silly I'm missing?
  21. Thank you John! 🙂 Thanks! 🙂 Thanks buddy! 😉 Thank you Bernd! 😉 Many thanks Andy! 🙂 Yeah, it's SimFX. Excellent addon!
  22. No this was meant only as a OP question to monitor CPU temps during the events of stutters. Michael Moe
  23. Well, it would be the easiest thing to confirm with an overlay that captures the direct frame latency, Nvidia's own works, whilst also showing something confirming FG to be active. OP just confirmed exactly what I was saying mere 4 minutes before I posted it.
  1. Load more activity
×
×
  • Create New...