Hello Denali -

 

Will any of this post processing interfere with screen warping products like Immersive Display, Immersivaview, etc?  I think they load their own separate post-processing but no sure how is all works together.

 

Very cool stuff you are doing.  I hope to give it a try once I know it will peacefully co-exist with my projection software.

 

Thanks.

Your projection software is probably just using an approximation.  If you are projecting on a sphere shaped surface, that is essentially what I am doing in virtual space.  In other words, we are doing the same thing, only they are letting the projection screen do the math, and then some approximation / correction done by some compression/expansion algorithm.  As near as I can tell that's what they do.  If you are projecting on to a flat surface then my shader will be good for that.

 

 

So perhaps the issue is that it want center. The program seems to think that my left monitor is the center. 
 
And i cant get the shortcuts to function in full screen mode. 

 I am looking at these issues.  

 

 

So, what I did was place a new camara definition at the end of the Cameras.cfg file.

 

Hi Denali.

 

Ok got the "AS Virtual Cockpit" camera to show up in the camera menus.

My mistake was adding it to the cameras.cfg file in the main P3D folder rather than

the %APPDATA%\Lockheed Martin\Prepar3D v2 directory

which in my case was C:\Users\UserName\AppData\Roaming\Lockheed Martin\Prepar3D v2.

 

gb.

 

 

This is the script you'll want around to run with AutoHotKey:

 

I try to open the AS01 AutoHotKey script (AS01.ahk) with either version one or two and I get the following message:

 

Error at line 1.
Line Text: #NoEnv
Error: This line does not contain a recognized action

This program will close.

 

??

 

gb.

Try this instead of the script.  https://www.dropbox.com/s/x2oc926bvhqhgfy/Prepar3D%20Views.exe

another thought.  Use a button first.  The hotkey parameters don't load until a button is pushed.  

Try this instead of the script.  https://www.dropbox.com/s/x2oc926bvhqhgfy/Prepar3D%20Views.exe

 

Ok this worked so I've got a little bit further.

 

The image will resize with the buttons but none of the hot-key combinations work, i.e. nothing happens.

With the "Show Frame Rate" control/windows key/f I get this error message:

The Active Directory Domain Services is currently unavailable.

 

So I have the Expanded view across my thee 1920x1200s with the image centred on the middle one.

 

I'm running four monitors, three in a row and the forth under the centre one of the three.

I will have to disconnect the forth to give this a chance since when I

expand the view it comes down half way into that forth monitor.

If I drag the window back up the view reverts to the unexpanded view.

 

At the moment I'm seeing objects at the centre of the expanded view being bigger than when I position them at the edges.

Sort of reverse fish-eye effect. Also the centre area is very low resolution looking.

 

gb.

If there is distortion there, FOV is probably not set correctly somewhere.  The checkbox seems to uncheck in a Custom Camera.  View Edit Custom Camera to check for it.

 

I'm working on a better dialog for the sizing of the oversize view.  The fourth monitor below is something I wasn't expecting, (actually I have used a monitor there for a panel, but killed framerates)   I would think you can just put any other window over it to use it.

 

The low res in the center is because it gets expanded in the alrgorithm, but I have worked this out before, and plan to do so.  A first step for this is there are lower FOVs that can be used, the loss is not as noticeable at say 150x40.

I am also having the expanded middle of view problem in one of the views I set up.  I'm not sure what is causing the problem, yet.   It does have something to do with FOV settings in P3D2, but I'm not sure where it's missing in this case, whereas it works in others.  It may have something to do with scenario files.

 

 

The low res in the center is because it gets expanded in the alrgorithm, but I have worked this out before, and plan to do so. A first step for this is there are lower FOVs that can be used, the loss is not as noticeable at say 150x40.

 

The 150 horizontal might be a bit ambitious?

When I had NV Surround set up at 6040x1200 and a zoom ratio of .8,

I think the horizontal VOF was about 120 degrees from memory.

 

gb.

If you're getting an idea of what is going on,  you can set the FOV to be whatever you want it to be.  Experiment.  I might be making a table of sorts to go with this to work automatically.  My FOV is supposed to be around 125, but I want to see from door to door and out the right window a little bit, so I fudged it larger.  Actually, all of that is a matter of what your brain is able to adjust to.  

There are studies that show if you get used to wearing glasses that turn everything upside down, when you take them off you'll see everything upside down again.

 

 Also, the view gets a little too close, I've noticed not being able to see the enough of the panel and the runway to keep good track of instruments.  Many issues to be ironed out.

I'm just suprised I'm not getting more responses, because I'm having great fun with this.  I really like what I see, and I know I can make it better (I'm very stubborn German stock).  It is probably that many people are intimidated by the installation and are waiting it out?

 

 

It is probably that many people are intimidated by the installation and are waiting it out?

Yep

Cheers

Keith

Same here... watching this topic with interest, waiting for things to settle out and a less involved install procedure.

 

Keep up the good work!

Yep, also following

Also following. And trying

 

I had the same problem as one other above, my result image was centered around the left monitor, so the left third of the view was hidden.

 

Although not a clue as to what I'm doing, I changed the Autohotkey script where is says:

finalXPos := Round(((5760 - Width) / 2) - 1920)

to:

finalXPos := Round(((5760 - Width) / 2) - 0)

 

and voila!

 

The vertical FOV could be better, and the resulting image quality is not optimal, but as for the perspective this looks so much more like it should on my 5940x1080 setup.

Hopeful you can optimize the code to give a bit better quality - if so this is definitely a winner!

 

Btw. The compiled script in post #35 did not work on my W7 x64, probably only for x86 editions?