So yes, the single correction I have created accounts for all angles if the screens are centered around a general viewpoint. 

 

 

 

Ok, I understand that.

 

 

My solution is not completed. This is a hobby for me, not a commercial venture at this time. One of the reasons why I've kept the current work out of view is because I don't wish to have to deal with the support issues. But I realize there is growing demand for the solution, and a group working together around the idea can be helpful.

 

 

Please count me in if you need help. Implementation/test/anything.

 

 

The portion I am working on now is to remove the need for the over-sizing software, which Is the source of a support nightmare because it is confusing. 

 

 

Yes, that would be the killer solution.

 

And you are going to use a post-process shader applied to the camera? And hence user interface remains untouched? (I am not much conversant with graphics/shader programming, please excuse me if something does not sound right)

And you are going to use a post-process shader applied to the camera?

 

Yes, ideally only a simple post process shader, just as the first iteration.  I switched to Reshade to experiment with antialiasing methods, was a little easier in there.  I really made progress there, just a matter of porting back to LMs brand of post processing (I think some minor language difference, I'm not an HLSL programmer, I just play one on your monitor) and applying a little more trig to cut out the over-sizing program.  I will still have a nice easy install method, everything I can do so everyone leaves me alone, heh.  

 

Using injection, as Reshade and Nikola's methods use, breaks P3d's menu system, distorts them to be unreadable.

Anything can be done with math, including angles and bezel adjustments. 

Yes, ideally only a simple post process shader, just as the first iteration.  I switched to Reshade to experiment with antialiasing methods, was a little easier in there.  I really made progress there, just a matter of porting back to LMs brand of post processing (I think some minor language difference, I'm not an HLSL programmer, I just play one on your monitor) and applying a little more trig to cut out the over-sizing program.  I will still have a nice easy install method, everything I can do so everyone leaves me alone, heh.  

 

Using injection, as Reshade and Nikola's methods use, breaks P3d's menu system, distorts them to be unreadable.

Anything can be done with math, including angles and bezel adjustments.

 

I just tried the built in fisheye post process, and because of the distortion the mouse click locations in VC are all offset. Do you account for that?

 

 

I just tried the built in fisheye post process, and because of the distortion the mouse click locations in VC are all offset. Do you account for that?

  No!  Very good point!   I am not sure how to go about that, other than to suggest that the user toggle to another readily available view, such as the default virtual cockpit, to click.  I have looked into it, maybe doing something such as intercepting the mouse click with the same mapping from another program.  But I haven't investigated too far yet.

If you could implement it as some kind of display mode that included your post process  would be the only way to fix that. Your changes come in after the screen stuff is calculated and all the VC clickspots are figured out.

 

By that I mean regardless of what screen setting or aspect ratio we use in P3D the clickspots always work.  SO maybe it's possible to setup a the resolution you need for your post process beforehand as a display mode then apply your corrections...could be it's not possible or too much work. They do something similar with SoftTH 

Does anyone have a link to Denali's fix?

There's a really old version but I don't think he made a new one available yet.

There's a really old version but I don't think he made a new one available yet.

Where's that located. I can't find a link that works!

Denali.

 

Sir, I'd like to thank you in advance for all your work.

 

I've gone through the threads, and I have a few questions.

 

1. Do you have a link to the latest version?

 

2. Does this make any permanent changes to P3D files?  If not, is it as simple as not loading the AHK script to run normally?

 

 

Thank you so very much in advance.

View Groups in P3D. Well worth a read.

 

http://www.prepar3d.com/forum/viewtopic.php?f=6306&t=119668

View Groups in P3D. Well worth a read.

 

http://www.prepar3d.com/forum/viewtopic.php?f=6306&t=119668

 

Does this new groups feature fix the fish eye distortion, I'm assuming?

Does this new groups feature fix the fish eye distortion, I'm assuming?

 

Unfortunately not.

 

gb.

The 1080 GTX does it ...

The 1080 GTX does it ...

 

Do you or anyone have one to confirm this or is this just speculation based on specs?  How does it achieve it.. i'm guessing its surround mode somehow compensates?  (i dont use surround mode on my 980 ti, i basically maximize the window to full screen over all 3, which was identical in surround mode as well)  Does it achieve it by using Groups in P3D or strictly hardware?

 

I'd be willing to sell off my 980ti for a 1080 if this were the case.. avoids the need to goto say a 48" screen from my three 24s.  Wondering also if only certain 1080's have the ability.. i'm guessing the baseline 1080 GTX would have it and be just as good or better than the 980 ti.  EDIT:  a quick glance at nvidia FOV correction (is this it?) seems to indicate 1070 and up.. so i guess the quest for me is to find the comparible 1070/1080 card in performance to the 980 ti.  This one review seems to indicate the 1070 would beat out the 980ti and be good for VR?

http://www.tested.com/tech/pcs/570381-tested-nvidia-geforce-gtx-1080-video-card/