Heff

Not tried the NGX on wideview yet. That is some time into the future yet. But I am running another sim on wideview, and that works pretty well. The one thing I am worried about with the NGX via wideview, is if the landing lights will work. I believe I have read it somewhere here, that NGX landing lights does not work same way as traditional addon lights.

My plan is to use the FSX computer as a server computer, so it will not show anything useful at all. The visuals will most likely be on another computer via Wideview. Then another computer or two, for displaying the instruments from the server computer.Got a bluescreen now after a while... with 8 images cut from one "base image". And then all the clients froze, and would not shut down for a while. Is there a datalogger or another place I can get details from to help you Johan?

Also a couple more ideas for functionality on the clients...If someone wants to use a HUD, the image must be "reversed" for it to be displayed correct.Maybe functionality for rotating clientwindow 90 degrees, + vertically, and horisontally mirroring of image on selected client.Ivar Hestnes

JohanThis is really good stuff.I have tested with 4 copies of the same window, with 4 different cuts, broadcasting it to laptop and it works great. I cant notice any fps drop at all when using same window many times to cut from, but my fps is up in the sky anyway in window mode. This is a brilliant tool. I love it.A couple things I notice. On my fsx computer, I use a tripplehead2go, and 3 monitors. So the window I see in FSXspy is very small. So it is hard to cut exactly what I want. maybe it is possible to make a simple zoom and pan function for easier to aim at the cutzone?I also discovered, that if I changed the fps on SPYserver, then I had to disconnect, and reconnect on clients for updating the fps shown there.Not a big issue.Below two screenshots from FSX, and laptop. FSX had approx 90 fps when screenshot taken,Laptop:FSX:Thank you so much for your efforts in making this tool. Ivar Hestnes

ArnaldoDid you type in the server Computer name in the highlighted field on the client?if not it wont connect for sure.Ivar Hestnes

Finally got a chance to test this software.And I really like it. It gives you a flexibility which has not been available before. The functionality for trimming what to broadcast is excellent. Excellent work Johan!!I put some ideas here: user selectable fps for each window to broadcast. Some windows are OK with low fps, some would defo benefit from higher fps. function for totally removing window border on client, or get the border down to 1 pixel. functionality for duplicating window to broadcast from. So you can cut out two or more images from one window if you want to. That way you can use one computer as a server computer. Cutting unlimited images from this window, and broadcast. Then there will be no fps loss. Function for autostart of clients when computer starts. Maybe a checkbox for this in client for user to select. Anyway, this software is by far the most interesting for me the last years. This has great potential.Best regardsIvar Hestnes

JohanThat is absolutely brilliant. I have been thinking about this idea for a very long time, but do not have programming skills.Unfortunately no possibility for testing your software yet, but really looking fwd to it.My idea from before was to use one computer for running the NGX with all the displays on one computer, and then a second computer via wideview for the visuals. But of course, when I am going to use 1 screen per DU, + 2x CDU, 2 clocks, a ISIS and a HUD on one computer... I might get into fps troubles, even with every slider set on low... This will really solve this possible problem.Thanks for sharing!!! Ivar Hestnes

Ned...If you are good at programming, I think you should look at the Arduino cards. If you are able to write a interface between NGX and the Arduino, those cards will give you total flexibility. I am looking at the Arduino cards myself, but has no clue of how to make the neccessary software interface to NGX. If you also have some electronic skills, you can connect a huge amount of in/outputs on each arduino using shiftin/shiftout IC`s.Regarding PFD/ND and the other screens, I dont think PMDG makes a network version (but I do hope), so you can have them on a different computer, however... My idea is to run all those displays + a FSX top down view in the background, and then running the visuals on a separate computer via the wideview application. This should work.I am looking at the NGX as a base for my next project, but also at the Prosim737. Cant make the decision befor the SDK is released, and hopefully someone has written a software interface for some hardware...Ivar Hestnes

I have successfully removed the CDU bezels also now. It was not so difficult, but some play with the numbers is neccessary.If you also want to have the DU`s moveable with a mouse without them going back to the "MIP", then make a new window for them, and play with the numbers as I did with the CDU.Here is my CDU modifications with a few comments.//// CDU (Left)//[Window02]BACKGROUND_COLOR=0,0,1 //R,G,B doesnt seem to do anything on the CDU or DU`s...size_mm=268,222 //From left, from top screen sizewindow_size= 0.20052, 0.50000position=8visible=0ident=402zorder=99gauge00=PMDG_737NGX!CDU, -60,-42,385,600,L #0 //By pulling numbers to minus, the bezel will be outside the "screen area". //From left, from top, total size from left, total size from top.

Here the "windows" I added...//// Ivars modification for HUD//[Window21]BACKGROUND_COLOR=0,0,1size_mm=800, 600position=1visible=1nomenu=0ident=HUDalpha_blend=1.0zorder=90gauge00=hud!hud, 0, 0, 900, 768//// Ivars modification for CPT chronometer//[Window22]BACKGROUND_COLOR=0,0,1size_mm=512, 256position=1visible=1nomenu=0ident=CPT chronozorder=90gauge00=PMDG_737NGX!Chrono_Screen, 0, 0, 256, 256//// Ivars modification for FO chronometer//[Window23]BACKGROUND_COLOR=0,0,1size_mm=512, 256position=1visible=1nomenu=0ident=FO chronozorder=90gauge01=PMDG_737NGX!Chrono_Screen, 256, 0, 256, 256//// Ivars modification for ISFD//[Window24]BACKGROUND_COLOR=0,0,1size_mm=512, 256position=2visible=1nomenu=0ident=ISISzorder=90gauge00=PMDG_737NGX!ISFD, 0, 0, 256, 256

I did some work on this yesterday, and got all the gauges working.[Window Titles]window00=Main Panelwindow01=Lower Mainwindow02=CDU (Left)window03=Aft Electronic Panelwindow04=Fire Protectionwindow05=Forward Overheadwindow06=Aft Overheadwindow07=Overhead Lightswindow08=Lower DUwindow09=MCP (full)window10=Radioswindow11=Zoomed Left Outboard DUwindow12=Zoomed Left Inboard DUwindow13=Zoomed Upper DUwindow14=Zoomed Lower DUwindow15=Zoomed Right Inboard DUwindow16=Zoomed Right Outboard DUwindow17=CDU (Right)window18=Minipanelwindow19=Light Sensorwindow20=Logicwindow21=HUD // added by IvarWindow22=CPT chrono // added by Ivarwindow23=FO chrono // added by Ivarwindow24=ISFD // added by Ivar Now I have also placed three undocked views angled to a total of 205 degrees FOV there. But the trick I used with the default -800 to remove the interior didnt seem to work for the NGX. I inserted "//" in front of "interior=PMDG_737_800_VC, and also in front of normal=PMDG_737_800, but it didnt do anything useful.I have also changed the background colour to 0,0,1 which means black. But for the DU`s, they still have the blue background colour. Not sure if they can be edited to be black, as I would rather add the blueish colour with proper anti-glare glass in front of the displays.For the HUD... if you set colour to 0,0,0 it will be no black around the HUD, and it can be overlayed on the visuals if neccessary.

Thank you for your kind comments Jason :-)It was a big decision to start building a second simulator. But... when I finished the "woodie", I needed a new project of course. And after learning to build simulators for 5 years, the desicion was not so hard to make. Now I can enjoy the one I have, and at the same time build a new one, and push the bar further up. The new project will be much more demanding. I dont want to be dependant on PnP stuff with the shortcuts they have. So its time for doing it properly. Looks like the Arduino prototypeboards is the way to go. Total flexibility.But there is lots of programming stuff to learn. And that will keep me busy for a while, hehe. We are a few guys out there that has been fortunate to get hold of real 737 HUD`s, and the NGX is of course the ultimate solution for utilizing this.But all this boils down to have the displays managable :-)There is a sneaky other way of doing it, but I would rather not. A imagewarping software would do the trick, but it is far from a good solution.

I am wondering about a couple of things.When I click on the 6 flight displays, they will appear so I can stretch and position them. But I cant do this with the ISIS, clocks and HUD. And the CDU`s will still have the bezel with buttons displayed. Is there any solution for this? So I can get all the displays resizeable and moveable without having buttons and bezels displayed.And...If all this can be done, can the positions be saved? Or is there any plans to integrate functionality like this to accomplish the SDK?I have already finished a complete 737 sim based on PM, but planning and collecting parts for a second sim which hopefully will be a NGX based sim. Very busy in Autocad inventor designing stuff at the moment.But this is dependant on ability to reposition and save all the displays, and the upcoming SDK of course :-)Best regardsIvar Hestnes

SDK sounds good to me. That is a starting point for integrating hardware. Just what we need. How about the screens... PFD, ND and so on. Any tool that allow for resizing of these? Or an application that can run the screens on a separate computer with some flexibility regarding positioning and size? Very hard to integrate this into a cockpit if the DU size is fixed. Also the HUD... Any chance it will be possible to undock or send this image out to a dedicated screen output? That would be awesome :( Watching the progress on facebook, and the work so far is nothing short of brilliant. Kudos to PMDG! :(