Hi wledzian will this tool work with Prepar3D v2 Fxml type files please if so
How
Printable View
Hi wledzian will this tool work with Prepar3D v2 Fxml type files please if so
How
YEs would be great to get your help on this one as I am as well in P3D, thank you in advance.
I have not tried it directly in Prepar3d, but it is my understanding that the view scaling is identical and the portion of the relevant file is similar. If you can locate the relevant portion of the file, feel free to paste the Windowmaker text in place and see what happens. Worst case - the file doesn't work.
Hi All
I wounder if you could help me?
after using windowmaker in P3d this is what I have joined up but I seem to have a blank bit at the bottom is that right? I dont think so.
Neil
Photo attached!
All, Please find attached a photo of the problem?
Can any one offer me any help in getting this working in a P3D fxml file? I have 3 x 23" monitors landscape.
I've created a new flight .fxml file in P3D and edited in notepad but the references/headings in the excel spreadsheet don't match the P3D file - for example..
The is only 1 window section 'window.1'.
There are 22 camera sections 'camera.1.xx'
I asume I make 3 x window.x sections?
Do I point these at the VC GUID or the 2D GUID? In the window maker spreadsheet Windows 1 points to 2D but Window 2, 3, 4 all point to the VC??
In my file window.1 = VC GUID but camera.1.1 = 2D and camera.1.2 = VC
Shouldn't they all = VC?
Hope I am making sense and you can help?
Mark
Mark,
I have not used Windowmaker (i tried but I cannot make it work for me and I really do not need it) but I can answer a few of your questions:
- You should have 4 window.x sections; window.1/.../window.4,
- Window.1 should be set to any camera view and set it to panel view or spot view or something that needs the least scenery,
- Windows.2/.3/.4 are your 3 views. They need to be VC views if you want to see landing and taxi lights and 2-D if not, I honestly do not know what the difference is and I am using VC,
- Camera.1.xx/camera.2.xx ...etc, all you need of those is camera.x.1/camera.x.2 and you can delete the rest, P3D and FSX will recreate them,
My FSX "flt" file has the following:
[Window.1]
Order=4
Active=False
Undocked=False
Maximized=True
ScreenUniCoords=4, 4, 1, 1
UndocCoords=0, 0, 0, 0
CurrentCamera={A2849229-938A-448F-8AC6-01EF2291C171}
[Camera.1.1]
Guid={B1386D92-4782-4682-A137-738E25D1BAB5}
Zoom=1
Translation=0, 0, 0
Rotation=0, 0, 0
[Camera.1.2]
Guid={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078}
Zoom=255
Translation=0, 0, 0
Rotation=0, 0, 0
[Window.2]
Order=2
Active=False
Undocked=False
Maximized=False
ScreenUniCoords=0, 0, 2731, 6144
UndocCoords=0, 0, 0, 0
CurrentCamera={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} <---- VC GUID
[Camera.2.1]
Guid={B1386D92-4782-4682-A137-738E25D1BAB5}
Zoom=1
Translation=0, 0, 0
Rotation=0, 0, 0
[Camera.2.2]
Guid={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} <---- VC GUID
Zoom=0.46500000357627869 <---- Calculated by my warping software
Translation=0, 0, -0
Rotation=1.3425000905990601, -72.6199951171875, 0.60000002384185791 <---- Calculated by my warping software w/minor tweaks
[Window.3]
Order=0
Active=False
Undocked=False
Maximized=False
ScreenUniCoords=2740, 0, 2726, 6144
UndocCoords=0, 0, 0, 0
CurrentCamera={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} <---- VC GUID
[Camera.3.1]
Guid={B1386D92-4782-4682-A137-738E25D1BAB5}
Zoom=1
Translation=0, 0, 0
Rotation=0, 0, 0
[Camera.3.2]
Guid={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} <---- VC GUID
Zoom=0.43924799561500549 <---- Calculated by my warping software
Translation=0, 0, -0
Rotation=0.90000003576278687, 1.7000000476837158, 0 <---- Calculated by my warping software w/minor tweaks
[Window.4]
Order=3
Active=False
Undocked=False
Maximized=False
ScreenUniCoords=5461, 0, 2731, 6144
UndocCoords=0, 0, 0, 0
CurrentCamera={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} <---- VC GUID
[Camera.4.1]
Guid={B1386D92-4782-4682-A137-738E25D1BAB5}
Zoom=1
Translation=0, 0, 0
Rotation=0, 0, 0
[Camera.4.2]
Guid={C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} <---- VC GUID
Zoom=0.45610100030899048 <---- Calculated by my warping software
Translation=0, 0, -0
Rotation=0.41999998688697815, 72.900001525878906, 0.15000000596046448 <---- Calculated by my warping software w/minor tweaks
P3D fxml files have different format but eventually same info.
Please note the rotation and zoom values will not work for you; these are specific for my cylindrical screen and 3-projector set up with warping software. Use Windowmaker to get similar results for your set up.
I hope this helps you.
Good luck,
Ammar120
Sorry for taking so long to reply to this question, I didn't see it when originally posted.
That blank bit at the bottom looks like a near clipping plane issue. With three views on one monitor, your vertical FOV is rather large, and with the plane on the ground, the near clipping plane extends through the ground. Does the problem persist when you're in the air?
Afraid I don't know how to adjust the clipping plane position.
Its pretty simple.
fill out the desired view angle and number of displys.
Than click calculate.
In P3d load a flight and add three additional views.
Save that flight and open the related file in an text editor.
The let the formating signs alone and just copy the calculated data to the correct positions.
You will need only Camara 1 in each window part.
You can delete all other cams beteeen the windows.
For me in germany the comma in the zoom part must changed to a dot. It depends on the country and excel language.
Save the file and open it in p3d. The correct view only appears if you make a full screen in window mode or a real full-screen.
You will need to select "show all file extensions' to save the flight file.
Thomas