Leaderboard
Popular Content
Showing content with the highest reputation on 01/22/2021 in all areas
-
An update on the situation... We have made contact with the developer of XPRealistic, and we feel we have a handle on why this is occurring. XPRealistic is writing to some required view monitoring datarefs every frame which SkyMaxx Pro also monitors. This is causing numerous allocations of depth buffers until things eventually explode. We are discussing how to deal with this. There are talks of us creating a workaround, and XPRealistic coming out with an update. As we get more information we will let you know.4 points
-
ADMIN NOTE: SkyMaxx Pro v5.0.1 has been released and supersedes this post for the time being: ------------------------------------------------------- We have received numerous reports of insanely high RAM usage up to the point X-Plane eventually crashes and/or FPS are simply unsustainable. In every one of these instances, XPRealistic has been in use and the culprit of the issue. Our best guess at the moment would be that they are somehow changing the format of the depth buffer, which would mess up our attempts to copy it for our shadow and soft particle effects, and ultimately causing terrible memory leaks. The fix on this is potentially going to need to come from their side. As of this writing I have reached out to the main developer to offer him a copy of SMP v5 so we can work together. In the meantime, you have a couple of options: 1. Remove XPRealistic entirely. or try... 2. Unticking "Natural movements" and "Ground Shakings" in XP realistic v2. We have received a report that #2 does work, but in all cases option #1 does for sure resolve the insane memory leak. I will do my best to keep everyone updated here on how the XPRealistic developer works with us.3 points
-
I unticked "Natural movements" and "Ground Shakings" in XP realistic v2, and now both plugins work correctly together3 points
-
After having both V4 and V5. I am getting much better frame rates (after disabling XPR2) and the clouds look soooooo much better. Thank you. Only downfall is XPR2 is a must for my airliners. I hope it gets solved. Thank you again.2 points
-
2 points
-
I found a way to use the volumetric clouds now, going to FXAA creates some flickering but then the 1070 seems to do a good job and I'm CPU bound again. Seems as if I really have to do some time traveling stuff and come back with a proper machine...1 point
-
Sorry, but this post as a whole is pretty ridiculous. We are not responsible for things out of our control. We absolutely will own and find ways about things we CAN control (and this thread is evidence of that). You having unrealistic expectations, however, is not fair on any developer. I don't care if they're associated to me, or a can of worms. It's just about being real.1 point
-
1 point
-
1 point
-
I have no issues, FSGRW, RWC, SkyMaxx v5, XPR is active as well as other plugins, attaching my log if it helps. So far tested with FF767 at KIAD and pretty stable 45FPS +/- 10 depending on views, no god rays, cloud draw 80000. Tested at EGNS with the Islander with Orbx scenery, god rays on and cloud draw 60000 in heavy cloud and no less than 35FPS. Very happy so far, thanks for the work. Paul1 point
-
With RWC and slider maxed out the clouds seem to reach the horizon indeed, also it seems the visibility range increases with altitude.1 point
-
Alone in the trenches but a beautiful sky.................................with SMP41 point
-
Can confirm XPR2 is the problem. although turning off the above does not help me. Disabling it completely works.1 point
-
1 point
-
I installed with "fear" when I have read here, but I have no issue at the moment I don't have XPRealistic1 point
-
I also can confirm too as I am also with ASXP + RWC1.2 + V5. Only if I disable the XPR2 plugin, V5 works well with charm!1 point
-
1 point
-
@Cameron I'm bugging out of this as mine has been stable since XPR2 remove. I will use V4 till patch. Let me know if you need anything on my side and thanks for you help!1 point
-
1 point
-
1 point
-
Can confirm. XPR2 is the issue Going back to V4 for now. I was very happy with that till a patch comes out1 point
-
1 point
-
Okay, seems stable. I do not have AS running. I've tried with and without beta settings in SMP1 point
-
1 point
-
1 point
-
SkyMaxx Pro v5 has been released! That brings this thread to a close. Enjoy!1 point
-
I appreciate your information, however, I have done prior research on the X plane.org site for some help. There is no Saitek configuration for the X Aviation M20 aircraft. My current Logiteck/Saitek drivers work on all my installed aircraft except for the M20 group. I find it frustrating that I have to use my mouse to click the multiple switches in the cockpit when I have most of them on my switch panel. I have decided to uninstall the X Aviation/AFM Mooney aircraft and purchase the proper ones from Carenado. This was my first and last time purchasing products from this site. I have been an X Plane user since version 9 and have never had this type of situation.1 point
-
I'll be buying this upgrade in a few hours. Over the years I've bought every single cloud and weather add-on for X-Plane that's been released I think. I just installed an update for another popular cloud add-on and it looks like something out of a cartoon! I keep getting drawn to these other add-ons promising better FPS and better visuals but they rarely deliver. I keep coming back to SkyMaxx Pro. Recent v4.9x updates have really improved the performance. Flying VFR using SMP is so good. It's only been IFR flights where the performance has been an issue for me, and only when I try to stretch out the clouds further than machine really wants to draw them. If this really has been fixed in v5 then it will be the perfect cloud plugin. Thanks for the work you've obviously put into this new version. I'm very happy to pay the $19.95 upgrade fee.1 point
-
oh, awesome! I didn't expect that. Looking forward to it. That would really be the last thing this plane needs overall it's almost perfect.1 point
-
Happy New Year all. Great plane, but the ILS issue is a real frustration. I use this plane to help me with real world currency, so having ILS capability is a must. And Like many of us we have extremely busy lives. So the idea of spending precious free time trying to fix things is doubly frustrating. To the developers: understand that my frustration, and probably some others, is that you’ve developed a great plane that people want to fly, but is currently incapable of flying one of the staple approaches in the IFR world (without an investment of time from your clients to fix). I totally agree with jrw4 above; issue the ILS fix now, and the minor rain / ice fixes at your own timeframe. To be quite honest, I could care less about the rain / ice. I need an ILS capable TBM 900 now. So please, give us the fix that really means something to us right now. Thanks.1 point
-
Hello, I am one of those users, Tbm purchased 10 days ago, didn’t know was broken, let’s say it’s my bad. Total guessed usage (gps only ofc)..8 to 10 hours until new airacs. I totally rely on ssalis and jrw4’s tought, as I am also fully understanding X-Avi point of view and efforts, even if the lack of info still gives me thoughts. Btw..everyone I speak with, I only get the best reviews for you. I absolutely don’t wanna be polemic but since the long time needed to develop this tricky fix, may i suggest to at least write the issue on the selling page? Wait wait..I know, this is totally counterproductive, but trust me, I would still have bought from you, and for knowledge probably’d have turned to 737 classic, not my main priority but surely a must have in the future. I hope this will resolve soon, I’m a bit disappointed but really still hyped to fly that boy. Just a question: by downgrading airacs, will I be able to fly networks like Vatsim/Ivao or everything will be compromised? Happy new year everyone, also from Italy!!! Peace1 point
-
Please try to understand this from the perspective of users who paid $65 for what well may be the most expensive add-on GA aircraft in X-Plane, doubly so for those who paid for it during the last seven months without having been told that the most basic ILS technology (which works in every default XP aircraft) is nonfunctional in the Hot Start TBM900. This is a customer relations issue, not a technical one. It's X-Aviation's reputation that's on the line, not that of the customers. If you wish to censor and scold us, then have at it. I'm not so sure that works well in the social media-rich world of 2021, but give it a try. The developers had over half a year to fix this problem and, indeed, claim to have done so, but do not want to bear the expense of releasing that fix. That's a business decision over which the customers have no control, but it may come at a significant reputational cost. Happy New Year everyone. Be safe.1 point
-
Any further update on this? Cameron? Goran? Is this workaround really working, or not? I'd rather know it for sure before doing any change... Navigraph just released their 2014 AIRAC Cycle, which they reaffirmed is going to be the last one with the double version for X Plane, 11.50 AND 11.41. From the next cycle (2101, I suppose) only the 10.50 version will be available. At this moment, this means that the ILS LOCs will be out of service for those of us using the (in any other sense fabulous) X-Aviation TBM 900 on X Plane 11.50. I guess Navigraph shouldn't be blamed for deciding to discontinue publishing data in a format which is now some months old. It is becoming increasingly urgent to have a patch which reliably solves this issue. Do you at least have an expected date for the release of the new patch? Thank you very much, and Happy New Year from Milan.... Stefano1 point
-
1 point