Jump to content

Denco

Members
  • Posts

    137
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Denco

  1. 1 hour ago, Iain said:

    Nothing wrong with the question, there are plenty times with LOC is used on it's own before press APP, it's pretty common way to do it, especially if you want to track the LOC while flying the descent profile in another mode like VS.

     

    I do have one more question. I like to fly my planes manually towards the runaway. The problem is when I disable the A/P the glideslope and localizer disappear from the PFD leaving me without a F/D. How can one disable the A/P while still regaining the F/D?

  2. Hi, 

     

    I'm not sure if I did anything wrong, but today when I was making my first flight with the IEXG I wasn't able to capture the localizer. I selected my approach to the runaway and later entered the ILS that was in the INIT REF page to the NAV 1 radio. When I was in the range of the localizer I pressed the VOR LOC button but it didn't work. Is there something I'm missing?

  3. On 12/3/2016 at 2:25 PM, Sethos said:

    Well, I can tell you, they aren't very experienced if they recommend those settings :P It's all snake oil, probably brought on by years of FSX / P3D use. And yes, the three settings I mentioned are the only ones working and they are all recommended. Threaded Optimisation 'off' makes a huge difference. You are better off resetting that profile. 

    Extended DSF means it loads additional tiles around you. Instead of 3x2 tiles, it now loads 4x3 tiles, which increases load times, decreases performance and worst of all, can add a lot of stuttering, especially when it draws new titles. In some cases I would see a 60-70% performance hit.

    Not sure if it's permanently removed from X-Plane 11 or it's one of those settings that will make its return, alongside more fine-grain control over scenery options etc. but it appears that X-Plane 11 handles distant scenery much better. Flying at high altitudes in X-Plane 10, without extended DSF, out of the box, would give you some big nasty brown splodges in the distant. X-Plane 11 seems to do a much better blend, so I don't think extended DSF will be necessary.

     

    Extended DSF is always enabled in XP11 and it doesn't cause any problems. I don't experience any fps issues with the pb1 like I did with DSF on in XP10 :)

  4. 17 hours ago, Pete said:

    Support for SLI and mutli-monitors (on one system) would really really help!!!

    1

    You can use multiple monitors on 1 system. I'm currently using my Ultrawide monitor with my old monitor and it works without problems.

    MtA4PfW.jpg

     

  5. 49 minutes ago, sundog said:

    Denco, I'm not sure but I think the stutters you're describing are a side effect of the NOAA plugin updating your METAR data too often. SMP4 will change how RWC interacts with things like NOAA in a way that should reduce this.

     

    Could be. If there are clear skies without any clouds there will be some occasional short stutter every now and then, but otherwise, I'll be at 60fps when cruising. Once there is some moderate to heavy cloudiness the problem I noticed starts appearing.  

     

    I'm going to do some test's tomorrow without NOAA plugin enabled. 

  6. I really like SkyMaxx and I use it on every flight and will upgrade to v4 considering a nice discount you guys are offering. The performance is very good if you keep the cloud distance at about 10000, but if you go higher you will start feeling the fps drops in a really bad weather situations.

    I'm not going to ask about the fps performance gain since others were already curious about this, but I do wonder about stutters. Even with RWC there are still quite heavy clouds redrawing going on just not as noticeable as without it and whenever RWC redraws stuff the CPU usage rises, for me to about 0.50 to .60, which lower's the performance and causes stutters until it's done. Sometimes it last's for a good few seconds and is especially noticeable if you have higher clouds draw distance set since redrawing are happening more often. Was/ Can anything be done about this? I can provide a video if it's unclear on what I'm talking about.

     

    Regards. 

    • Upvote 1
  7. Just now, sundog said:

    I don't use NOAA myself so I'm not real sure how it works. I can tell you that RWC in "always" mode will periodically check to see if either METAR.rwx or MAXX_METAR.rwx has been updated, and use the newer of the two if so.

    As crisk73 said, going back to NOAA 2.3 and deleting both of those files should get you back in business.

     

     

    Yup, I'll trust his word and yours. Also, I wouldn't mind being a guinea pig for that v4 of SkyMaxx ;)

     

  8. 4 minutes ago, sundog said:

    I think when you reverted back to 2.3, you still had a newer file modification date on METAR.rwx than was on MAXX_METAR.rwx, and so we kept using the most recent METAR.rwx that 2.4 had placed there.

     

     
     

    I just remembered that that NOAA has it's own METAR file, I think. Can RWC still access that one?

  9. I've been running the above combination for a few weeks now and I experienced no problems. RWC was set to "ALWAYS" as per manual. The last few days I noticed I'm not getting clouds in areas where bad weather is reported. The first thing I did was to check the METAR file if the upload failed, but the file was ok filled with proper information. Next thing I did was to disable the RWC by setting it to "NEVER" I get clouds immediately. I reenabled RWC by setting it to "ALWAYS" and disabled the NOAA plugin. To get the clouds showing I had to disable and reenable RWC using the above procedure because I have "Never change visible weather option" enabled.

     

    So any idea on what could be happening here? I first noticed this when I update NOAA to v2.4, but considering that reverting it back to 2.3 didn't fix anything makes me completely and utterly lost. I uploaded the latest METAR. The latest test was done today on the LJMB airport with the following report:

    2016/10/24 14:00
    LJMB 241400Z 20012KT 180V240 9999 SCT033 BKN150 18/12 Q1019

    MAXX_METAR.rwx

    • Upvote 1
  10. I was advice by a user on Reddit ( Sethos ) to disable the extended scenery. I immediately went from 30 fps at cruising altitude to 50 fps with no stutters. This one option was causing me so many problems for months and I never realized this could be the culprit of all my fps issues. Just thinking about all the time I've spent complaining that SkyMaxx lowers my fps and in the end, it wasn't even the culprit. To all the users who have low fps issues check if you have this option enabled and disable it. Couple it with Ventura Sky and you won't even notice much difference.

    I currently have the draw distance set to 20000 and my fps are above 40 :)

    • Upvote 2
  11. 57 minutes ago, PeterR said:

    I repeated my usual test flight after returning from vacation, this time already on X-Plane 10.50 and SMP 3.3.2. I think overall performance and experience has improved a bit. Unfortunately I still experienced one single digit FPS drop in the middle of the flight. Quick cycling of SMP settings (increased drawing distance) recovered FPS. The route was covered with quite high number of clouds. Rest of the flight (after cycling settings) was flawless. I hope to do some more flights over the weekend and eventually install Win 10 with fresh X-plane installation. Overall I remain impressed with SMP as the occasional FPS drop (easily recoverable) is not big deal for me.

     
     

    I still experience this, but the funny thing is I never experienced this before the 3.3.2 update and at this point I don't know if it's Skymaxx or windows updates.

×
×
  • Create New...