|
OpusFSI World Views |
Post Reply 
|
Page 12> |
| Author | |
Opus Software 
Senior Member 
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: OpusFSI World ViewsPosted: August-04-2015 at 3:23am |
|
OpusFSI Beta Version 4.60.4
World Views Introduction World Views are cameras that have been fixed at a specified latitude, longitude, and altitude. All World Views are defined within the simulator's Cameras.CFG file (in your AppData Roaming folder) and their Camera Definitions are read in by the simulator only on start up. Live Camera automatically modifies your simulator's Cameras.CFG AppData file based on your current World View camera configuration. After creating, cloning, or editing (making changes) to any of your World Views you must shutdown and restart both your simulator (FSX, FSX Steam Ed, or P3D) and the OpusFSI FSISERVER program. Limitations You can create up to 99 World Views on your system but will generally only need a few defined at your favourite airports, or multiple views defined at the same airport specifically for video making or plane spotting. Be warned there are limitations and plenty of unfinished features or bugs within the FSX code relating to fixed type cameras. These problems cannot be overcome in software due to the incomplete support for camera control within SimConnect and general lack of monitoring and view control within the FSX simulator code (the same limitations and problems are found in the FSX Steam Edition and Prepar3D simulators). WARNINGS ... 1. Camera Positioning Error The Lat/Lon coordinates for all World Views (Fixed Cameras) within the sim are stored with very limited accuracy hence the camera position may end up shifted N/S or E/W depending on the coordinates. You will have to use trial and error, shifting the view to compensate for this limited accuracy within the sim. 2. Change of Hemisphere Bug The sim does not like displaying World Views (Fixed Cameras) located in different N/S or E/W hemispheres. This is a bug that results in corrupting the stored data for all the World Views in the sim. The sim will continue functioning, however all World Views will be corrupted until the sim is restarted. Solution - don't display World Views in different hemispheres. These problems however can be overcome by adhering to the following simple rules, DOs ... 1. DO assign a 'unique' button or key sequence to your World Views (see below). 2. DO use the assigned World View button or key sequence to display a World View. When an assigned button or key sequence is detected the software selects or cycles to the configured World View that, a) has been assigned to that button or key sequence, and b) is currently within 48km (30 miles) of your present position. Under normal circumstances we therefore recommend you assign the same button or key sequence to ALL your World Views. Use of this 'unique' assigned button or key sequence will always select or cycle to the World View(s) local to your current position. If you have multiple World Views configured at the same location then you can either assign separate or common button/key sequences to each view at that location, or you can manually select the view you want via the simulator's Views->View Mode->Custom Menu. Warning - NEVER manually select a distant World View (see the DON'T section below). If you do not assign buttons or key sequences to World Views you can still select them manually via the simulator's Views->View Mode->Custom Menu provided you are very careful and never manually select a distant World View. DON'Ts ... 1. NEVER use the menu to select a World View that is not near to your present position. 2. NEVER use the 'A' key to cycle when any OpusFSI External or World View is displayed. 3. NEVER relocate the aircraft or 'Go to airport' when a World View is on display. 4. NEVER display World Views defined in opposite hemispheres. The only time you should use the 'A' key to cycle through World Views is when you know for certain that ALL the selected World Views will be nearby to your current position. Nearby in this case is assumed to be within 48km or 30 miles. If you do select a distant World View that is say on the other side of the globe or in a different hemisphere then it will most likely result in the faulty FSX code corrupting ALL World View configuration data held within its memory. The sim will most likely continue to function as normal but NONE of the configured World Views will work as expected. The effects in the sim may be unpredictable and the only recovery will be to restart the simulator ! If you NEVER display a distant World View the sim will be happy. Creating World Views Click on the Create option within the Camera Management dialog then select the World View camera type and click OK. The simulator's display will be initialised at your aircraft's current latitude, longitude, and altitude. Cloning World Views Highlight the World View camera you wish to clone within the Camera Management list then click on the Clone option. The simulator will automatically slew to the World View's configured latitude, longitude and altitude. The Confirm the scenery is fully loaded dialog will then be displayed. Click on the OK button ONLY after the scenery has finished loading and displaying on the simulator, normally indicated by all the runway markings appearing along with all airport infrastructure. Editing World Views Highlight the World View you wish to edit within the Camera Management list then click on the Edit option. The simulator will automatically slew to the World View's configured latitude, longitude and altitude. The Confirm the scenery is fully loaded dialog will then be displayed. Click on the OK button ONLY after the scenery has finished loading and displaying on the simulator, normally indicated by all the runway markings appearing along with all airport infrastructure. General Editing ... All camera editing should be carried out with the simulator operating in Windowed Mode (as opposed to Full Screen Mode where you will not be able to access the OpusFSI dialogs). All World View camera editing should be carried out with your aircraft stationary on the ground. World Views can be Created, Cloned, and Edited via the Camera Management dialog. When the World View Edit dialog is displayed the simulator will automatically be placed in 2D Cockpit and Slew mode. If the 2D panel is on display you can remove it by right clicking on the panel and using the Close Window option. The 2D panel can also be toggled on and off the display using the simulator's Views->Instrument Panel->Main Panel menu option. In edit mode you can use the simulator's normal Slew Commands to slew your aircraft to the desired World View (fixed) camera position. You can also use the World->Go to Airport menu option to relocate your aircraft to a different part of the globe. In doing this you may need to use the World->Time and Season menu option to restore daylight conditions. World View Name Specify the name of the World View in this edit box (e.g. East Midlands RW 09). This is the name (preceded with OpusFSI) that will appear on the screen and within the simulator's Views->View Mode->Custom menu. Assign Button After making any adjustments slewing your aircraft, the Assign button option MUST be used to record the aircraft's current position, altitude and attitude. The World View's 'assigned' position and altitude are displayed within the dialog. The aircraft's attitude (pitch, bank, and heading) are recorded but not displayed. The assigned pitch, bank and heading are generally only relevant in Non-Track mode. Disable View Tick this box if you want to disable or remove the World View from the simulator's Cameras.CFG configuration. When ticked the World View will not be selectable nor will it appear within the simulator's Views->View Mode->Custom menu. Track Aircraft Tick this box if you want the World View to always track and point toward your aircraft's current position. Zoom The default zoom level for all World Views is 1.00. You can use this option to alter the zoom to any desired setting. Joystick Button and Key Sequence When an assigned button or key sequence is detected the software selects or cycles to (when multiple World Views are assigned to the same button/key) the assigned World View that is within 48km (30 miles) of your present position. To change these assignments simply click within the Joystick Button or Key Sequence text boxes and press the required button or key sequence. Clicking a second time within the box will clear the entry. Displaying World Views ... When you display a World View using an assigned button or key sequence you will notice the OpusFSI External View momentarily flash onto the screen. This is deliberate and necessary as Live Camera must first select the OpusFSI External View, prepare the sim's display and allow the sim time to settle before cycling or stepping to the chosen World View. |
|
 |
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-04-2015 at 3:24am |
|
World View Dialogs ...
Creating a World View ...  Editing a World View ...  |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-04-2015 at 10:04am |
|
Just reposted the beta (30 mins ago). I forgot to enable the World View option when Creating new camera views. My bad. Sorry for any inconvenience.
Regards Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 1:51am |
|
I can persuade the new views to work in FSX, but absolutely no-go in P3D (but I'll keep trying).
Though the view is created fine in FSX, I couldn't get the "track" option to work. A "semantical" note: in the EDIT option, you use the word "Assign". I kept looking to see if was assigned to specific aircraft (which is more usually where the "Assign" button is used). In World View, though, it simply means "set these values" (other than if you're *only* referring to "assigning" a stick button or k/b sequence). I found it confusing. Would "Save" (or suchlike) be less confusing - for daft old farts like me? LOL. Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 2:31am |
|
The Assign assigns the current aircraft position, altitude, and attitude, and MUST be used to assign a new position or modified camera location. I will see about renaming the option to something less confusing.
Remember you MUST restart the sim after any changes as the Cameras.CFG is only read in on start up. You will have to Export your WVs from FSX set up, then run FSISERVER in P3D mode and Import the WVs. Then of course restart P3D. My Track option works perfectly and you can clearly see the Track = Track option in the Cameras.CFG file. Could you have another go and remember about restarting the sim to get the sim to read the CFG file again. These views cannot be edited on the fly, only defined within the CFG file. Stephen :-)
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 3:03am |
|
Just created cameras again and imported them into P3D. Everything seems to work very well in both FSX and P3D including the Track Aircraft option.
Note, you can run FSISERVER in P3D mode without running P3D. Import your cameras, click OK to save them and update the P3D Cameras.CFG file (make sure you are in P3D mode). Then close FSISERVER, run P3D, and restart FSISERVER again in P3D mode. Your new WVs should be loaded although you may have to assign buttons and keys to them but that does not require restarting the sim, only changes to the position, altitude, attitude, and Track options requires a restart. Stephen :-)
|
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 5:01am |
|
Thanks, Stephen.
I restarted P3D a number of times - to no avail. The camera view is there (in OPUS/LCC) - and can be edited - but never activates when in the aircraft, regardless of button or key assigned. That part works OK in FSX though. BTW: I set up NEW world cameras from scratch in both FSX and P3D. I'm wondering whether the P3D version of cameras.cfg is cached somewhere. I'll try some manual editing (FSX and P3D) to see if that helps. Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 5:28am |
|
Are you running FSISERVER in P3D mode ?
Check your Configure dialog and the Spy window. I can find NO problems and created several WVs in P3D this morning. Each time checking Cameras.CFG in the sims Appdata. Have you checked yours ? It could be FSISERVER is unable to edit your P3D CFG file due to security and permission issues, or if still in FSX mode it will be updating the wrong file. The file is in the usual place. Stephen |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 5:50am |
|
I checked both camera.cfg files. Both get updated OK. I shifted position slightly and saw the new lat/lon values being updated. Date/timestamps also updated fine. OPUS appears to be auto-selecting the appropriate FSX or P3D mode as per normal. I also fired up OPUS independently (no sims running) and could see nothing untoward.
The new world camera entries look almost identical to the traditional LCC entries. Even the "track = track" options are showing correctly. Nothing I could spot there. Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 9:26am |
|
Opus doesn't auto select the mode. It's defined by your Configure dialog or optional program argument.
The World Views in the sims AppData cameras.cfg file will be of Fixed type with defined FixedLatitude, FixedLongitude, and FixedAltitude settings at the end of the CameraDefinition. The OpusFSI External CameraDefinition will be numbered 999 and your World Views will numbered 998, 997, downwards. Stephen :-) |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-05-2015 at 9:38am |
|
Also check your Views -> View Mode -> Custom menu. You should see the OpusFSI External along with all your OpusFSI World Views listed in the menu, as per the CameraDefinitions in your sims AppData Roaming cameras.cfg file.
Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-06-2015 at 5:42am |
1) The correct version of OPUS is correctly fired up by either FSX or P3D - no problems there. I also have two manually created shortcuts - they both work fine as well. 2) The entries in the two respective cameras.cfg look OK too - just as you describe. Setting the current view via the views menu in P3D works - sort of. The world view correctly jumps to the defined world view (and tracks - yay!) ... but after visiting that view, when I try to select any of my pre-defined LCC external views, it starts sending me off to some distant spot. This is when parked very close to the World View as defined - so I'm definitely within range, so to speak. Vc views (as expected) are unaffected - and going back into an OPUS Vc view appears to "reset" everything ie. The normal external LCC cameras work - but this time the *World View* dumps me somehere in the middle of the Pacific (I think LOL). All very repeatable - and I'm not using the "A" key at any time. Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-06-2015 at 5:56am |
|
The corrupted WVs are the result of the sim not liking the displayed WV, having to load new scenery etc.. Once a WV is corrupted they will all remain corrupted until the sim is restarted. This normally happens when a distant WV is displayed but seems to be when any WVs are displayed on your system. Everything else will work ok but all the WVs data is corrupted internally within the sims memory. You should report this bug with Fixed views to Lockheed Martin as they should be able to correct it.
If you open TaskManager and examine the active applications, what name is the P3D sim listed as. I ask this because the software relies on reading child window names to determine what's on display on your sim. Also before displaying any WVs can you select your various VC and External Aircraft views? Have you tried just creating and using a single WV on your sim. You can edit your cameras.cfg if you wish and delete all bar one of your WVs. Stephen :-) |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-06-2015 at 6:00am |
|
You could also try flying in the N hemisphere with just N hemisphere WVs configured. Just in case this sim bug has anything to do with southern latitudes.
Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-06-2015 at 7:21am |
|
Hi Stephen - I've only ever set up/tested a single WV and - yes - it's in the southern hemisphere (NZ). All VC and external LCC views work fine until I start trying to go for the WV options.
I'll try in sunny UK and report back (with the Taskmanager info as well)! Adam. UPDATE (at EGBP / Kemble): Taskmanager reports Prepar3D.exe *32 1) Created new WV (only the one exists). 2) Restarted P3D 3) From default Vc view, selected OPUS Ext view (via menu). OK. 4) Went back to OPUS Vc. 5) Selected the WV (via menu) ... went bonkers - travelling to some far off place. |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-06-2015 at 10:43pm |
|
Update to the update!
I found that after a couple of P3D restarts, everything appears to be OK if I only use the menu to change views. The moment I use my usual pre-defined joystick button(s) for either Ext View or WV, then it all goes screwy. Hope that helps! Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-07-2015 at 1:56am |
|
Perhaps the button is not unique to the WV.
Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-07-2015 at 2:14am |
|
Nice try (!) ... but no - I thought of that when I set it up right from the beginning. The WV is mapped to a totally unique button.
Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-07-2015 at 2:32am |
|
Ok, I will be posting Beta 4.60.1 today with modified WV selection so try that.
What is the name of your P3D in TaskManager? R click on the task bar then select 'Start Task Manager' and check the Applications tab. Mine says ... Lockheed Martin® Prepar3D® v2
Stephen |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-07-2015 at 6:52am |
|
Stephen - that's odd, as mine says "Prepar3D.exe *32" (a couple of posts above - you may have missed it).
looking forward to playing with the next beta (will report back). Meanwhile - I'm greatly enjoying testing OPUS near my old stomping ground (Fairford):  :-) Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-07-2015 at 7:04am |
|
I need to know the name listed in the actual Applications tab, not the running Process name. Hopefully that will be the same as mine. Nice screenshot of Fairford.
Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-08-2015 at 2:12am |
|
Aaah - rightio ... we may have a problem here then, as I have an FSUIPS setting active to enable monitoring VAS useage - so I get:
Monitor IPC:024c(S32) = 1849320 I have it set to display on the title bar as it's far less intrusive than the flshing green thing that displays in the window when set to "FS Window". When flipped, I get: Lockheed Martin(R) Prepar3D(R) v2 It's fairly useful and I suspect quite a common setting for FSX/P3D users, so I wonder if you may have to find some other way of referencing the window title/task name <??>. After disabling that FSUIPC setting all works fine - mystery solved!!! And what a treat it is. I used to record aerobatic displays using kludged tower view positions - I'd forgotten how entertaining these "air-show" views can be. Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-08-2015 at 2:17am |
|
Thanks Adam, that all makes sense now. When I get back next week I will see if I can locate both possible processes, or all possible process names for Prepar3D and FSX.
Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-08-2015 at 2:43am |
|
:-) Glad we got there in the end!
Don't forget that the FSUIPC variation will be dynamic ;-) - that last number changes all the time. Adam. |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-09-2015 at 10:54pm |
|
Quick question: do world views need to be assigned on a per-aircraft basis, or are they enabled by default for ALL aircraft?
Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-10-2015 at 1:53am |
|
No, WVs are always global, hence there is no opportunity to assign aircraft to them, you can only assign the WV location, altitude, and attitude with an option to track the users aircraft.
Stephen :-) |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-10-2015 at 2:33am |
|
Thanks, Stephen - I suspected as much. I do see them when I'm selecting/assigning multiple (external) views though - which is why I wondered. Adding/removing them from aircraft assignments was one of the "hoops" I went through when trying to get WV's going initially.
Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 1:43am |
|
I have posted a new beta which should recognise your modified flight sim application name.
Stephen :-)
|
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 6:47am |
|
There still seems to be a bit of a "gotcha" ... in that if you start the session with previously defined camera views (all working OK after a few sim restarts) and *then* turn FSUIPC logging on, everything goes screwy again.
Also - when it all works OK, my camera position seems to drift (slowly) when set up with "Tracking" on - even though the aircraft is parked/stationary. As soon as the aircraft moves, it seems to start tracking properly again. All this in P3Dv2 (haven't tested FSX yet). Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 6:57am |
|
I can't do anything about the sims tracking, it has nothing to do with me. As for the other problem, you must not of course enable FSUIPC4 VAS monitoring during the session. I cannot hope detect such changes that would be far too slow and laborious having to search through 200 plus windows each time I want to change or detect the view mode. So you must start with it on and leave it or change it and restart FSISERVER so that it can identify the new sim application windows.
Stephen |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 7:18am |
|
Point taken about restarting after enabling window logging in FSUIPC. Is simply resarting FSI enough - or is it best to quit out and restart both?
Still something wrong though. I have two WV's active - with entirely different stick/keyboard shortcuts. After switching to FSUIPC logging (and recreating the local WV camera), the stick button fired up the wrong WV. It looks like it simply picks the first one (or the higher one) from the list (having displayed the correct one for a tiny instant). That key combo is then locked to the wrong view. Menu/view selection seems to be the only way I can find that WV again. The tracking movement appears to have sorted itself out. I *think* it was induced by me replaying a (P3D) recording then resuming "normal" flight. Adam. EDIT: After further tests (assigning separate/unique) *as well as* stick buttons - just to be double-sure - I'm finding that my keyboard shortcuts seem to be ignored (nothing mapped to thenm in P3D) but that the stick buttons are behaving like a "next" view. ie. Each button press cycles between all WV's - regardless of which button is used. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 7:29am |
|
You should only need to restart the FSISERVER as it then tries to detect the correct flight sim application on startup.
When you use a button or key to select a WV the software simply selects the nearest view that is considered to be local, that is within 48km or 30 miles. I will double check using separate buttons or keys. But you must only ever use unique button or key assignments. They must not be used elsewhere. It is always possible that you might see another WV flash up as the only way of selecting them is to select the first and step through them. So if the second view is the nearest it will have to select the external view and step twice upwards. Remember, view control and monitoring is very primitive if not unsupported within SimConnect. Once again, any changes, including reordering, then you must restart the sim as it only reads its cameras.cfg on startup. Stephen :-) |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 7:34am |
|
Just remember ...
Only the nearest WV within 48km can be selected using a button or key, which should be unique but a single 'unique' button or key can be used for all local WVs. Any other type of selection should be done via the Views menu but make sure you never display a distant WV. Stephen |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 7:38am |
|
OK - understood. My two views are Ardmore (NZAR) and NZWN (Wellington) - well over 48km away - yet I still get NZWN when I use the unique NZAR key.
BTW - I'm always restarting both P3D (and therefore OPUS) after *any* changes to WV's. Adam. EDIT: So ... what I'm seeing is (in effect) that my distant (NZWN) camera is being treated as "local" - and therefore "in the list" of local WV's that the same unique button will cycle through <?>. This would explain the apparently odd behaviour. Maybe the distance measuring routine is out in some way. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 7:45am |
|
Thanks Adam,
I will double check the button and key selection. What if you assign the exact same button or key to all your WVs as described in the notes. Then the software should only display the nearest within 48km. Probably using separate buttons or keys will be selecting the assigned, I will check and make sure the correct checks are made. Stephen |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 9:24am |
|
Thanks, Stephen. The way you describe (same for all) is how I had it initially (for a short while) and I had that behaviour then as well. Mind you - I had other things going on at the beginning.
Right: Fresh start! 1) Deleted all WV's. 2) Went to NZAR and created one local WV. 3) Restarted. Worked OK. 4) Same session: went to NZWN via the "World - Go to Airport" menu option. 5) Created a local WV - with the same stick/key combo as NZAR. 6) Didn't test (just in case) - I just quit out of P3D. 7) Relaunched P3D at NZAR. 8) Only local NZAR WV active after repeated button presses - so far so good. 9) Went to NZWN (as in [4], above) but WV's take me to NZAR as well. My next test is to NOT use the "Go to XXX" when setting up new cameras. Launch P3D and go to that airport before jumping into the aircraft. Is using the "Go to" a complete no-no - either for when setting up WV's in the first place or within the same session in P3D? I can see the logic of the former - but the latter will often be used by a fair few people I'd imagine. Will report back tomorrow! Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-14-2015 at 10:00am |
|
Thanks Adam,
I will test using the same procedure, looks like there's a problem in view searching or the distance calculations. Stephen :-) P.S. You are allowed to sleep down there in NZ'land you know. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-15-2015 at 2:16am |
|
Thanks for the detailed report Adam. I have found the problem which is again a fault identifying the correct WV from within the sims application. I have corrected it and am now testing.
Also added another clause to the list of DON'Ts in the WV guide (see above). Regards Stephen
 |
|
|
|
|
Adamski_NZ
Senior Member
Joined: May-29-2009 Location: New Zealand Points: 503 |
Post Options
Thanks(0)
Quote Reply
Posted: August-15-2015 at 8:48am |
|
Thanks, Stephen. I feel suitably refreshed now!
Apart from info in the guide, if there's a specific step-by-step procedure we could use in testing, please shout. I'd forgotten how much I used to enjoy static cameras (for recording pseudo air-shows etc.). I used to be able to create/place different "Tower" views in FSX but never bothered in P3D. I'm sure this will be a popular feature :) Adam. |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15442 |
Post Options
Thanks(0)
Quote Reply
Posted: August-15-2015 at 11:16am |
|
I have corrected that problem and am now including some other necessary changes where the sim seems to be happier with the WV cameras. I discovered these new improvements when testing the above, so it has been very helpful. I will finish coding and test over this weekend and hopefully post a new beta on Monday.
Stephen :-) |
|
|
|
|
Post Reply
|
Page 12> |
| Tweet |
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
Opus Software wrote: