denali

Hi Maarten, Love your program. I use it often to move quickly from place to place just by dragging and dropping the user aircraft icon. But if I crash the icon does not update to the current location, the reset location. It stays at the crash site Was that intended? If I drag it from the crash site to somewhere it will then again track. Thanks for all your hard work and this masterpiece program.

any faster after subsequent loading?

Unfortunately, you'd probably have to add them one by one in the cfg file to figure out which one is causing a problem.

Sorry for the delay. Recovering from ... flu or something. Yes. I have eliminated the graininess that was present in my previous shaders I'm working on simplifying it.

Yes. And I have a fix for the distortion/stretching on the side monitors

Reshade works very well with P3D 3.1 and Windows 10. I recommend it. It installs easily, but as far as easy to use it's not quite there yet. I might caution against it for those that might not like a slight framerate hit, although I haven't confirmed if it's just bad placebo or not with my setup. They have a program that controls their shaders, but the gui is not intuitive and leads to confusion. I just might have to take an afternoon or two and rewrite the goofy thing. With enough demand/encouragement I'd do it. Also, many of the shader algorithms have been public domain and might be ported to Prepar3d. In other news, I have fixed my shader's "graininess" and hope to be able to release it for Prepar3d sometime within a month. This is for widescreen or multimonitor users, it removes the stretching distortion in the peripheries.

Roger Dodger

I will need these files as well configSet1=C:\\Users\\G. Salden\\My Documents\\Immersive Display PRO\\config\\P3D.dat configSet2=C:\\Users\\G. Salden\\My Documents\\Immersive Display PRO\\config\\config2.dat configSet3=C:\\Users\\G. Salden\\My Documents\\Immersive Display PRO\\config\\config3.dat configSet4=C:\\Users\\G. Salden\\My Documents\\Immersive Display PRO\\config\\config4.dat FYI, I am taking that time off that I mentioned. It's just going to take me a little bit of time to tie up ends. And another bit of time to chew away at DirectX and get that under my belt. I have put in the ability to change FOV in the view and shader, but it's not clean yet. I've also done a bit towards scenery.cfg management, but again, kinda messy, not ready for prime time. I'll be taking a bite at it every day, but it may take some time before I have something. I'll put up what I have when it's not too messy though. You would think they would have the math for our oh so common problem worked out in Idp too.

Thanks. I'll take a look. I'm not having much luck with some of my approaches. But I haven't completely finished working the ideas. If this works maybe I can use it for a model for p3d work. Still looking at d3d injection.

Ditto here. Thanks for carrying the flag guys. We'd be in a different place without you. Especially Rob, keeping LM in line . It's really been great, and I appreciate it.

Your link does not work

Update (about my windows 10 installation): Once installed on a PC, it won't need the key. Why didn't I pay attention when someone told me that before? http://www.pcworld.com/article/2970075/windows/why-you-cant-find-your-product-key-after-upgrading-to-windows-10.html Hopefully it works. I know that's a digression, but I think that goes to what I'm trying to say about these installation problems. There is a core issue, cause, that can be remedied, setting aside all the normal b2b constructs, to fix the problem once and for all. Just go for the fix, we tend to make our own problems by making up rules for why we're not supposed to fix them. And thus the games continue. Which reminds me, good thing I'm up. I forgot to take out the garbage last night.

I want special treatment. I would be willing to bet there are only a handful of calls they're looking for. This is why you make them unpublished. This is one of those things where it's not LM's or 3PD's fault, because the rules weren't set down in a defunct FSX to begin with. Lots of work went into bringing that ghost back to life, and LM is really who put it on the table again. Now we have Frankensim. Just saying, there is a clean way. Cause in a way, some credit has to be given to the 3PD's that kept FSX going, maybe a way to do that is to give them a little bit moar, allow their DNA into the project. Up early this morning to grudgingly admit I probably should download MS latest windows 10 iso that will now take a windows 8 key to load clean (so I've read). I'm literally losing sleep over this.

LM can expose what Orbx and others need, but in-house to LM only via an in-house module, and create a module that exposes those objects to the addon developers only, unplublished. Addon devs then don't have to hunt, and the address becomes available to the inhouse module at compile time. No hunting. It doesn't guarantee obfuscation, but there are ways to make it pretty tight. I'm not sure obfuscation is the greater goal here for LM or Orbx anyways, just accessibility. People that really want your secrets to compete with you will have them no matter what you do. It's the fast that eat the slow. Sometimes it's just wiser to spend more money on developers instead of patent attorneys. But to me it is time to break it out since it does cause so much anxiety for early adapters. You don't want to blunt that first wave in any way if you can help it, what is said about first impressions is critical for software these days, because competition. I do believe the community of enthusiasts will grow soon as common hardware capabilities reaches the threshold level of performance where the dizzyness we tolerated all these years isn't experienced by the fresh eyes.

This makes me think that if anywhere in your aircraft or scenery you have two mirrored surfaces facing each other, whatever you do don't get in between them and look into the mirrors. It's almost too much to handle in real life!!! So yeah, thanks for the warning!

I think if one of the benefits is more of the water works taken off the cpu and pushed to the gpu (Cuda improvement) then that's probably worth it. I am wondering how two 780's in SLI will be with 3.1. My windows installation isn't taking very easily for some reason. I tend to keep my broken windows installation partitions, and move them from the front of the drive. I'm seeing if deleting their recovery and system partitions will fix the stubborn boot problems I'm having.

Reading through the what's new list, there are very very minor changes to the content and scenery, so little it's really not worth fretting about to install it if you're on 3.0. So ... don't install it. 3.1 should install over 3.1, and yes you may have to wait for vendors to get their dll's compliant. With ASN, in the past if you just ignore the error popup and push it aside, it seemed to work.

This makes my day/week, as my Windows 10 installation boot decided to perform hari kari. Took me a while struggling before I realized I have to do a new install (starting with an 8 disk, sigh). So v3.1 will be on a clean installation; this time I'm not going to slack on backups. I can't try it myself this time, but I am wondering if just renaming the Prepar3d v3 folder to v3.0, and just installing v3.1 back into the default folder would work for a v3.0/v3.1 switch. You could go back by simply renaming the new install to Prepar3d v3.1, and the old install back to Prepar3d v3. OK, so yes you have to extend this thinking to roaming/LM, local/LM, documents/P3d files, and ProgramData/LM, but put those renames in a bat file and it's no more sweat. This is some form of entertainment.

Just an FYI. I am not wanting to be a Negative Nellie. I just wish there was an easier pathway to upgrades.

I don't think their software is crap. It's middle of the road, unfortunately. It looks nice; they're artists that's for sure. Their concentration is obviously on scenery dev, which works for everyone with excellent results ... well ... mostly. I don't wanna paint a negative picture here, or seem like the grouch about them here. I just know that there is a different way.

As if that changes the consequences. So no, it doesn't depend ... Let me just say this. Orbx makes first rate scenery. They just don't make first rate software. The funny thing about all these versions of P3D and FSX, theyre not any different as far as scenery as far as Orbx is concerned. Their problem is they started off wrong from the beginning and kinda seem too stubbord and proud to admit the mistake and fix it. I'll say it this way: There are no incompatibility issues with Orbx products; there are incompatibility issues with Orbx Installations. The practice of having n00b developers spend time with the installers, either those who make them or making them themselves to a standard convention, establishes a core skill. Software is not just about your program's files. All good architecture respects the established neighborhood. Year and years ago, when I was hired to teach people to be comfortable with windows (sometimes with the threat of job loss for the students - older executives), every week there would be an assignment to explore some aspect of the file system and do things like guess what a file did, why it was in that place, what it was doing in Windows/System32 or Windows/INF. How the boot order worked. Another was to learn how to "walkaround" a program, that is to literally walk through each and every button that could be found on the menu or toolbars or clicks in a program. Many people live on their systems but don't really know that environment. But that file exploration has come back to me with "I learned so much from that and it's always helped me to understand what's going on with computers". Understanding the file system is the foundation of understanding software.

Thanks. Also, being someone who works with and for Microsoft, they don't give their blessing on anything. If you break the rules, they'll pretty much just tell you they warned you.

I am a developer. Orbx claim that it's so difficult to upgrade is kinda a sham. What is lacking is the focus for a half a day to fix the problems with their older products. I suspect because of the fear of not focusing on the money is going to lose them money. I could take a day or two and write a routine that would fix their scheme once and for all, but I don't work for them, and they probably would get mad at me.

For those that want to know exactly what an installation is going to do to files before they install it, you can install it to a "sandbox" first, see what happens, and then chose which files to move over, and where. The one I use is Sandboxie. For registry changes there is another method, but addons should not be doing any serious registry changes. If you're a developer, sandboxing is a great way to understand how many things are done in software by seeing how they are installed. Also, often when tailing software does not follow best practices as set down by a primary developer it can be used to correct those incompatibilities that emerge. When the 3.1 comes out, I will use Sandboxie to do a pre-install, and maybe do a few window clips or some kind of output to show what files are affected. LM shouldn't have to be worrying about their files causing problems, but certain inexperienced scenery developers think it's their place to over-write native P3D files, when there are other more conventional methods to integrate their products. Much of the bellyaching in this forum about upgrades is not because of LM. And those conventional best practices have been known since before FSX, but are usurped by the arrogant imposition of certain developers who think it's "their place" in the scheme of things to just do what they want even though they haven't figured out what they're doing.

Just thinking about this a little bit, to prerender would mean to take up memory space, as well as bandwidth. Each frame may mean adding 100% to the memory, and that much more to put through the pipes. It may be like framerate limiting, only limiting the number of frames per frame, if you can grock that.