Cam

I also confirm again that no amount of jiggling the RH hardware CL will allow a start on the RH engine. LH engine starts fine with the LH hardware CL, which demonstrates I know how to set them up, but no go with the RH engine. I can do it with the mouse, but that's not what I want to use.

The last entry in the log seems to indicate a smp issue when changing clouds - it crashed because of smp pro. Yes, no obvious reason but caused by smp pro. I ran the same scenery and plug-ins with V4 without any problems with crashing.

I don’t seem to be able to map the flaps to an axis, as I had with v1.5.1. I have been trying with the Xplane Flaps binding under joysticks. Haven’t tried the LG yet as I can’t get off the ground.

I am able to map both CLs to individual axis, but moving it to the Start position does not properly find the Start detent, no mater how I jiggle it to try and find the detent. The mouse will not move the tiller either and I have Hyd pressure - both engines started via the automatic starter.

Are you saying I can't use my expensive Honeycomb quadrant as seperate CLs as I did on the previous version? The tiller is unlocked (I depressed the tiller to activate the NWS) and I have it mapped it to NW Tiller using the mapping in XPlane - as per the previous version (I also tried using the custom feature, to the map new les NWS Left and NWS right, with no success. Also, the rudder pedals won't turn the NW either.

Cameron, It works fine with the auto-start. I have traced it to the actual CL mapping - if I move the CL with the mouse/manipulator, it seems to find the Start detent and it starts, but if I use my Honeycomb CL and the Torque box to view where my hardware CL and Aircraft CL are at, it won't start (green box and CL are at the Start position according to the Torque box). No amount of jiggling will find the Start position. Also, I cannot map my Extreme 3D Pro joystick to the nose wheel steering anymore - it worked ok on 1.5.1, but the mapping doesn't appear to work - my Logitech rudder pedals move the rudder ok, but they wont move the NW steering (and I have the NW steering selected). I'm busting to get this into the air but can't steer off the parking spot. Cheers

I'll try that - what would you like me to send to help troubleshoot?

Cameron, Just downloaded V1.6 with but I can't seem to get the RH engine started. LH engine starts beautifully. Using Plane 11.52. Tried it with ground power and just with batteries, but no luck. Any clues? Cheers

Guys, Another CTD with V5.0.6, seemingly caused by SMP V5.0.6. Log attached. I was flying the Laminar C90B in relatively clear sky (some clouds) without any volumetric clouds; and getting 56FPS with my i7900K @ 5Ghz and a RTX 2070. Yes, I did have my screen res set at 2560 x 1440 and AA at 4X, but I was getting 56FPS. A fix really soon would be really really good. Cheers Log.txt

Ok. Thanks for the feedback Sundog. Cheers.

Me too. I get them in Vulcan on 5.0.6. This one was previously reported so I didn’t bother.

Yes, I am very aware of the permutations. What I am saying is to warn people that they will likely require a reduction in graphics settings to use volumetric clouds, and to advise that they are still a beta release (as noted next to the settings checkbox). If the person above with an overclocked 10th generation I9900K and a RTX3090 has to reduce his settings, that appears to warrant a warning to potential and upgrading customers. Not a very good commercial approach to marketing, but reasonable for a beta release. The volumetric cloud performance issue does not appear to be a bug, but an issue with the capability of current computer sim technology - as noted by Sundog in many of his responses , not me.

I’m old and retired too. I don’t have a problem with software having bugs per se, but I do have a problem with a lack of disclosure and beta testing by paying customers.

I get that it is a new thing (I was a software developer and fully understanding the development process). What I expected was some disclosure of the issues and the fact that it is still in Beta release - maybe some advice that a reduction in settings is required. I’m not sure that a suitable solution can be developed by Sundog, given his responses to date - not a criticism, just an observation from reading all the various comments. I am hoping that a solution is found as I love the product and continue to use it without volumetric clouds.

There are many people complaining about the performance drop they are experiencing with volumetric clouds. And whilst it appears that even one of the fastest systems around can’t even handle it without dropping the settings normally used, Sundog’s responses regarding a likely software update to address performance don’t sound promising. Ifikratis’ point appears to be that it is not clear in the advertising of this product that you will need to reduce your settings significantly to use this product effectively even with a top-notch system (or that it is still a Beta release). I suspect that he would not have bought this product had he known. We all appear to be experiencing CTDs and poor performance using V5, but would love to hear from anyone who is having success with volumetric clouds without reducing settings.

Hmmmm. There seem to be a lot of others with the same problem - who may not be running Traffic Global.

Changed the settings and CTD. Hope the log helps as this is becoming tiresome. Cheers and Good Luck, Cam Log.txt

Hi Sundog, Your solution to reduce the AA to 2 appears to have worked so far, and that’s ok when your flying high, but you have to come down and that’s when things don’t look so good when your use to 8 AA. I’ve turned off the beta volumetric clouds and will wait and hope you can give us something we can use without backing off the AA settings we used in V4. Good luck, Cam

Hi again and thanks for the feedback. I used the ticketing system on the x-aviation website 4 times with 3 log files but received no responses. I’m not sure that my settings should be considered impractical if they were working ok with V4; is it unreasonable to expect them to work on V5? Also, why is the volumetric function in beta for a paid release? thanks Cam

Thanks Sundog, I’ll give it a go. Its a bit disappointing that the upgrade appears to require a reduction in settings compared to V4, and that one of the major features is still a Beta. Cam

Sundog, Here is another crash log - V5.0.5 and just flying along with cloud - no changes being made and only half my VRAM being used. Cam Log.txt

Hi sundog, My screen res is running at a native 2560 x 1440. visual effects- Medium texture - max antialiasing - 8x anistropic - 16x cheers Cam

Thank you.

No, but he asked for them so would appreciate you providing them as I don’t have them any more. I will certainly provide the other data.