Rob Ainscough

Member
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

4 Neutral

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Two 2080Ti's here so not sure what I can trade up to? I feel the issue can be fixed at the code level ... some good developer information from nVidia here: https://developer.nvidia.com/pc-gpu-performance-hot-spots and (scroll down to section on "AFR considerations") ... quote from the article that I feel might be relevant to the issue: http://developer.download.nvidia.com/assets/events/GDC15/GEFORCE/SLI_GDC15.pdf SLI works for others like PMDG, FSLabs who work the DX flow ... I know they are competitors but it might be worth asking for input as I think the solution is perhaps not as complex as one might think. Cheers, Rob. On a side note: this is a common SLI problem not just here but with many other sim/game titles, some solutions can come from driver updates and/or tweaks via nVidia Inspector (i.e. SLI compatibility bits = 0x@A0117F1 and predefined number of GPUs = 0x0000002 (assume 2 GPUs) and predefined SLI mode on DX10 = 0x00000002) ... I try to avoid nVidia Inspector but it can be useful with SLI problems, experiment. P3D is AFR.
  2. Is there any solution yet for us SLI users, unfortunately I have several aircraft that use RealLight (Milviz, Quality Wings) and they all exhibit the flickering problem. I'd rather not use Reallight than disable SLI, so that's not really something I'm willing to compromise. LM suggested you folks are working on an update to support SLI? Fortunately QualityWings allows me to disable RealLight but that's not really a "solution", just a work around. Since this is almost April and 4 months past, thought I'd check in to see if any progress on this? If I enable Triple Buffer the problem is less noticeable which indicates it's a sync problem. Oddly, some button lights are not impacted while others are flickering? Cheers, Rob.
  3. I'll toss in my 2 cents, having major performance issues with TrueGlass and TrueLight when in SLI (oddly no flickering as has been reported). Specifically the MV 310R. If I disable SLI, then no issues. I did bring this up with LM and they seem to feel it's a driver issue and not much they can do their side. Thoughts? Cheers, Rob.
  4. I'm not using FSUIPC for any controller changes. Also not using GIT in this case. However, I was able to solve the problem. I went thru ALL my controllers in P3D and removed ALL button assignments in NORMAL mode and removed all SLEW assignments both button and axis for all my controllers. This seems to have resolved the problem. However, I'm still not able to assign the Tiller to Steering axis, nor am I able to assign Reversers to Reversers Axis in P3D V4.3 ... perhaps this is by design to retain compatibility with FSX?? Cheers, Rob.
  5. Not a big deal, I can work around the thrust reversers, just wondering why they aren't working with P3D V4.x axis assignments dedicated for that purpose? I do have FSUIPC installed but I don't use it for any axis/button assignments, only used when testing something out for Pete and that's on my other Test PC not my primary flight PC. I've cycled thru ALL my other controllers to check for assignments and nothing is conflicting. I did have a similar issue with FSL A320 earlier versions that was later fixed in updated release ... prior to that FSL A320 fix my work-around was remove any brake "button" (not axis) assignments ... is it possible the 717 is somehow responding to button assignments even though no buttons are being pressed? On the performance front, 717 seems to be performing very well with great FPS with V1.1 Cheers, Rob.
  6. Running the latest v1.1 (no issue in prior versions). When I get enough thrust to move forward the tiller wheel immediately goes left, I can counter it somewhat with rudder input to the right. Here is an unlisted video of the issue (note I've tested with and without ChasePlane, also tested with AutoRudder enabled and that didn't allow any rudder correct at all, just full left): In addition if I assign P3D V4.3 Steering Axis Set to a controller axis, nothing happens? Another issue I ran into is the assignment of Reverse Thruster axis to a controller axis also doesn't seem to engage the reverse thrusters? Any ideas? Cheers, Rob.
  7. Fantastic job with the rain and weather effects via TrueGlass. I really hope to see more of this in other aircraft but it makes me want to fly the 717 much more. Cheers, Rob.
  8. Take a look at how the default Carenado A36 have implemented their lights. Dynamic Lights Enable/Disable option does not prevent lights from showing it only changes the rendering of the light. In the SDK under "New Aircraft Procedures" take a look at "Landing Lights" - I believe you set the Visibility Objects to "general_light" and then in the FX file you specify will have the light type (Type=19). Unless of course you're doing custom lights via the PDK which is entirely different process. You actually don't want to specify Type=27 or 28 as those will ONLY show when DL is enabled (typically reserved for airport stationary lights). At least that's my understanding. Here as an unlisted video of how DL On/Off should work relative the aircraft lights, in both cases you'll see that the lights do work, just render differently: As far as cockpit textures, P3D V4 now supports (actually I think late in V3 this support was introduced) 4096 VC textures (default is 1024) ... this should help the visuals with dome lights but again I think you need to be careful what light type you're using for dome. Cheers, Rob.
  9. Some issues I've noted: 1. With the latest 1.0.9.3 build I"m not seeing any taxi or landing lights illuminate the ground when DL is disabled. 2. Cockpit dome light exposes severe gradients from what I think is overly compressed or low quality resolution cockpit textures? Changing MAX_VC_TEXTURE_RESOLUTION=4096 (from 1024) doesn't improve the problem. Here is a video (unlisted) demonstrating the issue: Cheers, Rob.
  10. I solved the performance issues by turning OFF (uncheck) "Allow Hardware Rendering" and turn OFF Landing lights (DL is enabled) taxi light is fine but landing lights cause about a 35% FPS drop. I'm able to use landing lights with DL on PMDG, iFly, others without as much an FPS drop as I get in the 717. Perhaps the landing lights FX needs to be tuned a little bit for better performance? So far no CTD. I don't have Chase Plane (a few items in CP need to be fixed before I'll install). On a side note, the default livery seems to have some excessive specular, perhaps tone down the white? Cheers, Rob.
  11. Thanks for the responses, glad this issue is not specific to my setup and will be resolved. The more worrying aspect is the strange performance I'm experiencing ... it has me puzzled, it's almost as if the gauge update rate is defining the FPS? Not seeing the issue in P3D V3 (very fluid), just in V4 which is odd because V4 operates about 15-20% better (in terms of FPS and less long frames) than P3D V3. Cheers, Rob.
  12. I just entered the TFDi Beta today for the 717 and took it for a test in P3D V4 (21686). Installation went well. I had a issue with the iPAD and setting aircraft state, when I select Ready to Fly I got some pathing error that was pointing to A2A products? Please see attached error pic. Performance seems odd, my FPS counter is solid at 30 FPS (Vsynch 30Hz monitor) but actual FPS is not 30, feels more like 15. I've never seen this issue before ... does the 717 operate outside of the stand physics modeling similar to the MJC Q400? If so, it looks like it's not synching up with P3D V4 correctly. Cheers, Rob.