ejwells409

No one? I guess I'll just push on and start doing some conversions and see how that goes.

I am trying to find any recent information on this prolific aircraft designer. It seems that around 2007 his offerings ceased and his email address is no longer active. I know he had health problems (failing eyesight) and it's a good guess that by now his health has not gotten any better. Has anyone heard anything about him or has any idea how to contact him? Many of his newer designs would be great to convert to Native FSX and extend their life even further however his readme expressly prohibits any conversion of his models. It's for that reason that I would like to contact him. The urge to do it is great but I respect his desire to maintain the simplicity they were designed with. Just would be great to maybe change his mind a bit, lol Thanks

I was hoping someone here could answer the question I raised, but apparently not. I got the information I needed from the helpful folks at Sim-Outhouse. I big thank you to the developers of RC for this generous gift. I wish them well.

Can someone explain exactly how the key generator is supposed to work. Apparently what I'm doing isn't correct. After I generate a key I place it into the space for it on the registration screen, click next. . .it sits there for a few seconds, gives me a "No Response" message and closes. Open Radar Contact and the process begins again, and it becomes a loop of failed attempts.

If Tesselation off causes the problem and then you check "Tesselation" and it goes away. . .doesn't that tell you that you need tesselation turned on? Tesselation "on" moves the job of texture loading over to the GPU, freeing up the CPU for other tasks. If you're running tesselation off you're defeating one of the primary changes LM made to improve performance. It should always be on, otherwise your CPU is doing everything. If your sim boggs down with tesselation on then look to your PC for shortcomings in either the GPU (at least a 600Series Card with at least 2gig of Ram but preferably 4gig), the CPU (at least 3.5 ghz or better) or your PC (should have at least 8gig of Ram or more). If those match or are at least close then look at your settings. There's no reason with a decent PC setup that V2.3 should lag at all. . .on the contrary, it should be far more fluid that the previous version. If it's not, as someone else just mentioned. . .don't blame the software.

There are always going to be detractors. Those who it seems are almost insulted that there could possibly be anything better than FSX/DX10. Well, enjoy your experience. If that's what you feel is as close to perfection as is possible then nothing anyone says will convionce you otherwise. If you have P3D_V2.3 and are having problems with settings and low framerates and autogen that looks like rubbish, then it's your settings and not the sim. Nuff said. On the r6025 error. . .I don't know what you've tried but here's what fixed it for me. I had been told to uncheck "Tesselation" by someone who was far more experienced than I. . .Don't do that. Leave that box checked, and if you have it unchecked right now and are getting that error, check it and see if that helps. Tesselation move the bulk of the texture loading to the GPU rather than the CPU, it's the biggest advancement as far as performance goes over earlier versions and FSX for sure. Just something to look at.

I posed the question about the 64bit possibility on the LM/P3D Forum and this was one individuals reply. . ."What? So did you just wake up one morning and make that up?". 64-bit "has never" been on the table as a possibility for this release or in the near future.

I have a question that hasn't been asked yet. What if I already have the "False" setting in place and still don't have any click-spots?

Jose,I'm getting a "Error 404" Page not found when I click on the FPSLimiter.zip link.

Does anyone happen to have the workarounds that were posted on the Flightscenery forum for making this scenery work in FSX? The website is gone now, so all that great work of tweaking that a few folks did is gone.