![]() |
Coming Soon |
Post Reply ![]() |
Page <1 161718 |
Author | |
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
Work in progress ...
Finishing touches to the smaller footprint OpusFSI Weather Reports with default options. Similar options (topmost, font, opacity, resizeable) for the Spy windows. Auto setting for Default Surface Visibility using Relative Humidity. Stephen :-) |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
Working on a few Camera upgrades at the moment ...
![]() Also looking to add an optional 'Properties' box so that you can quickly expand on a few of your camera properties, see the assigned aircraft types etc., without having to open the Edit dialog. The Properties box will remain displayed allowing you to simply click on different listed cameras and wiz through their overall properties and configuration. We are also looking to include an Automated Joystick re-assignment or re-ordering which will re-configure all cameras and change the Joystick numbers to match the sims ordering. Stephen
![]() |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
Making good progress on the Camera Details box which can be used to expand on the details listed in the Camera Management dialog. Also have a few ideas on methods allowing the joystick ordering to be reassigned to match any new numbering scheme within the sim. We will try to indicate the mapping very clearly in both the Spy window (when button events are received) and in the new Joystick re-assignment dialog.
We are also open to suggestions on any further information and features that could be added to the new OpusFSI Weather Reports, LWA Map, and Wx Maps. We soon hope to add Relative Humidity to the weather information which will allow a new 'Auto' Default Surface Visibility option. Stephen :-) P.S. OpusFSI Beta Version 4.72.0 has been posted with the new Camera Management dialog and Details box. |
|
![]() |
|
Adamski_NZ ![]() Senior Member ![]() Joined: May-29-2009 Location: New Zealand Points: 503 |
![]() ![]() ![]() ![]() ![]() |
With time, it's becoming harder and harder to find features that OPUS hasn't already got!
I'm not sure whether this has been mentioned before ... is importing Google Earth KML/KMZ files possible - even though Google Earth isn't one of the map types supported by OPUS? Not a huge deal (for me at least) as OPUS LWA maps already give me more than I need ;-) Adam. |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
I have looked at this in the past but will look again.
Stephen |
|
![]() |
|
Adamski_NZ ![]() Senior Member ![]() Joined: May-29-2009 Location: New Zealand Points: 503 |
![]() ![]() ![]() ![]() ![]() |
As long as it's not diverting resources from other (more important) features!
The only other thing I've thought about over the years (and this may already be possible but I haven't found a way to do it!) ... I'd love to be able to assign LV camera views to *groups*. Let's say I have a set of common VC views plus a typical set of external views. It'd be great to be able to assign all these cameras to a newly added aircraft in one go. For instance, for GA aircraft, I usually have: VC: A couple of default front views at 100%, 70% zoom. VC: A slightly offset (higher) viewpoint for take-off/landing. AC: Eight view angles: at 0,45,90,135,180,225,270,315 degrees (same elevation/distance/zoom). For airliners/large aircraft, I have a further set of eight AC views similar to the GA ones, but zoomed back a bit. I used to have a "mid-range" set of eight as well, but found I hardly used it. For Warbirds with long noses, I usually assign a left/right "peek" view - similar to sticking your head out of the window! So ... if I added a new fighter, it'd be really handy to simply assign it to my "Warbirds" group - which (for example) would include the default VC views, the two "peek" views" plus the Ac/external set of eight. You get the picture! Adam. |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
I think you can can't you. When you assign aircraft types again to a camera it asks you whether you want to change multiple cameras, at this moment you can add the new aircraft to the list and change the assigned aircraft across multiple camera views.
Do you have a specific KML file for me to test with. Stephen |
|
![]() |
|
Adamski_NZ ![]() Senior Member ![]() Joined: May-29-2009 Location: New Zealand Points: 503 |
![]() ![]() ![]() ![]() ![]() |
Yes - you can assign multiple cameras, but you have to go through the whole list of cameras and pick all the relevant ones each time you add a new aircraft. I just thought it might be a mre elegant way of doing things - though actual time savings might be marginal (!).
I'll dig out a KML file for you! Adam. |
|
![]() |
|
Adamski_NZ ![]() Senior Member ![]() Joined: May-29-2009 Location: New Zealand Points: 503 |
![]() ![]() ![]() ![]() ![]() |
Here's the Mach Loop:
<?xml version="1.0" encoding="UTF-8"?> <kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="http://www.w3.org/2005/Atom"> <Document> <name>NORTHMACHLOOPNEW.kml</name> <open>1</open> <Style id="s_ylw-pushpin"> <IconStyle> <color>b200ffff</color> <Icon> <href>http://maps.google.com/mapfiles/kml/paddle/ylw-stars.png</href> </Icon> <hotSpot x="32" y="1" xunits="pixels" yunits="pixels"/> </IconStyle> <LabelStyle> <color>7fffff55</color> </LabelStyle> <ListStyle> <ItemIcon> <href>http://maps.google.com/mapfiles/kml/paddle/ylw-stars-lv.png</href> </ItemIcon> </ListStyle> </Style> <StyleMap id="m_ylw-pushpin"> <Pair> <key>normal</key> <styleUrl>#s_ylw-pushpin</styleUrl> </Pair> <Pair> <key>highlight</key> <styleUrl>#s_ylw-pushpin_hl</styleUrl> </Pair> </StyleMap> <StyleMap id="msn_ylw-pushpin"> <Pair> <key>normal</key> <styleUrl>#sn_ylw-pushpin</styleUrl> </Pair> <Pair> <key>highlight</key> <styleUrl>#sh_ylw-pushpin</styleUrl> </Pair> </StyleMap> <Style id="sh_ylw-pushpin"> <IconStyle> <scale>1.2</scale> </IconStyle> <LineStyle> <color>7f0000ff</color> <width>3</width> </LineStyle> <PolyStyle> <color>7f00ff55</color> </PolyStyle> </Style> <Style id="s_ylw-pushpin_hl"> <IconStyle> <color>7fffffff</color> <scale>1.18182</scale> <Icon> <href>http://maps.google.com/mapfiles/kml/paddle/ylw-stars.png</href> </Icon> <hotSpot x="32" y="1" xunits="pixels" yunits="pixels"/> </IconStyle> <LabelStyle> <color>7fffff55</color> </LabelStyle> <ListStyle> <ItemIcon> <href>http://maps.google.com/mapfiles/kml/paddle/ylw-stars-lv.png</href> </ItemIcon> </ListStyle> </Style> <Style id="sn_ylw-pushpin"> <LineStyle> <color>7f0000ff</color> <width>4</width> </LineStyle> <PolyStyle> <color>7f00ff55</color> </PolyStyle> </Style> <Folder> <name> Waypoints </name> <Placemark> <name>EGOV</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -4.535339, 53.2481,10.9728 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP0</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -4.108833,52.69, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP1</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.96817,52.74333, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP2</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.92,52.75117, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP3</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.87517,52.74517, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP4</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.84017,52.74533, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP5</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.82833,52.73383, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP6</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.84367,52.7075, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP7</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.8805,52.6785, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP8</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.84417,52.652, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP9</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.84383,52.6395, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP12</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.84967,52.61867, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP13</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.849,52.6025, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP15</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.81833,52.6055, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP15A</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.78367,52.61217, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP16</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.70733,52.65083, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP16A</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.69967,52.68184, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP17</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.684,52.69117, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP18</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.69333,52.71833, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP19</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.722,52.73167, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP20</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.75683,52.73117, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP21</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.79167,52.73983, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP5</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.82833,52.73383, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP6</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.84367,52.7075, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP7</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.8805,52.6785, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP22</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -3.926,52.6605, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP23</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -4.00983,52.6195, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>MCHLP27</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -4.13967,52.58867, 10000 </coordinates> </Point> </Placemark> <Placemark> <name>EGOV</name> <styleUrl>#m_ylw-pushpin</styleUrl> <Point> <coordinates> -4.535339, 53.2481,10.9728 </coordinates> </Point> </Placemark> </Folder> <Placemark> <styleUrl>#msn_ylw-pushpin</styleUrl> <LineString> <extrude>1</extrude> <tessellate>1</tessellate> <altitudeMode>clampToGround</altitudeMode> <coordinates> -4.535339,53.2481,10.9728 -4.108833,52.69,10000 -3.96817,52.74333,10000 -3.92,52.75117,10000 -3.87517,52.74517,10000 -3.84017,52.74533,10000 -3.82833,52.73383,10000 -3.84367,52.7075,10000 -3.8805,52.6785,10000 -3.84417,52.652,10000 -3.84383,52.6395,10000 -3.84967,52.61867,10000 -3.849,52.6025,10000 -3.81833,52.6055,10000 -3.78367,52.61217,10000 -3.70733,52.65083,10000 -3.69967,52.68184,10000 -3.684,52.69117,10000 -3.69333,52.71833,10000 -3.722,52.73167,10000 -3.75683,52.73117,10000 -3.79167,52.73983,10000 -3.82833,52.73383,10000 -3.84367,52.7075,10000 -3.8805,52.6785,10000 -3.926,52.6605,10000 -4.00983,52.6195,10000 -4.13967,52.58867,10000 -4.535339,53.2481,10.9728 </coordinates> </LineString> </Placemark> </Document> </kml> http://www.fs2000.org/2016/01/04/fsxp3d-machloop-flight-plans/ Also .... ORBX produces KMZ files for all its areas. Sometimes I want to find out whether I've strayed outside the designated region/area, so fire up Google Earth to check. I don't currently have any Google Earth + P3D utilities that will plot my aircraft in Google Earth, so I have to try and work out my position manually. PlanG used to do this once, but I think they had to drop GE for licensing reasons. Anyway - it'd be great to not to have to run [yet] another utility whilst in-sim. These KMZ files can be quite large/complex (with many layers), so I'm not sure how feasible importing all that into the LWA map would be. Adam. |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
Thanks. Can't you name your cameras to indicate their role or type, as in Warbirds... etc.. then use the Up and Down arrows to arrang the cameras in a logical order.
I am investigating allowing KML/KMZ files to be loaded and their content overlaid on the LWA Map. Stephen |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
LWA Map 'Airways' Option ...
I am looking to add an Airways option to the LWA Map, this will compliment the current SIDs and STARs options. The Airways option will assist in examining an Airway and choosing an appropriate entry and exit point for your route. I'm also looking to allow you to examine and display the SIDs and STARs associated with any station displayed on the LWA Map. You will right-click on a station and SIDs and STARs button options will be available at the bottom of the Station form. They will be greyed out if none are available. I will give details regarding the ways in which Airways can be identified and examined as I progress. Stephen :-)
|
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
LWA Map 'Airways' Progress ... The LWA Map's Station Report dialog now contains 'SIDs', 'STARs', and 'Airways' button options. The Station Report dialog is displayed by right-clicking on any displayed Met station or Aerodrome map marker. The 'SIDs' and 'STARs' button options are greyed out if no departure or arrival data is available for the selected station. The 'Airways' button opens the LWA Map Airways dialog which can be used to search for all Airways that have Navigation Points within the specified distance from the station (default 50nm). Clicking on any listed Airway displays a list of its Navigation Points. The 'Reverse' checkbox option can be used to reverse the order of the Navigation Points making it handy to cut and paste from the lower text box. The 'Plot Route On Map' option will plot the Airway's route on the LWA Map. Large pink dotted markers along the route are used to identify each of the Airway's navigation points. Stephen ![]() ![]() |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
LWA Map 'Airways' Example ...
Selected DTY4P SID (Standard Instrument Departure) for Runway 09 at EGNX (East Midlands) to intersect Airway M605 at DTY (Daventry) VOR. ![]() |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
Used the above procedure plus an examination of the STARs for EGKK (Gatwick) to create the following flight plan. Exiting the Airway at WOD and then intersecting the WILO3B STAR for EGKK at MID.
EGNX IEMW2 IEMW5 HON30 D040Y D040S D340W DTY M605 WOD MID D118E HOLLY WILLO EGKK EGNX LAT 52.831111 LON -1.328056 Met Stn United Kingdom IEMW2 LAT 52.830995 LON -1.253642 Way Pnt IEMW5 LAT 52.803097 LON -1.178981 Way Pnt HON30 LAT 52.751970 LON -1.162369 Way Pnt D040Y LAT 52.686233 LON -1.246536 Way Pnt D040S LAT 52.607272 LON -1.347206 Way Pnt D340W LAT 52.534139 LON -1.354258 Way Pnt DTY LAT 52.180278 LON -1.113889 Nav Aid FINMA LAT 51.996389 LON -1.053611 Way Pnt SILVA LAT 51.847500 LON -1.005278 Way Pnt BENSU LAT 51.578889 LON -0.918889 Way Pnt WOD LAT 51.452778 LON -0.878889 Nav Aid MID LAT 51.053889 LON -0.625000 Nav Aid D118E LAT 51.016892 LON -0.506745 Way Pnt HOLLY LAT 50.886667 LON -0.095000 Way Pnt WILLO LAT 50.985000 LON -0.191667 Way Pnt EGKK LAT 51.148056 LON -0.190278 Met Stn United Kingdom |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
OpusFSI Beta Version 5.24.0
New GPS Output options to support SkyDemon / Foreflight running on an iPad. Regards Stephen
![]() |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
OpusFSI Beta Version 5.24.0 has been posted (see Announcements) New GPS Output options to support SkyDemon / Foreflight running on an iPad. I am now working on adding traffic data to the SkyDemon / ForeFlight GPS feed. Regards Stephen
![]() |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
Not necessarily coming soon but... For SkyDemon and ForeFlight users. We are now looking to simulate the WiFi communications of real world systems such as in-flight GPS and ADSB-In/Out devices (e.g. SkyEcho 2) using industry standard protocols. This will allow the sim to mimic all the usual RW in-flight data such as GPS data, aircraft data, and of course traffic TCAS/TAS warnings. We are also starting to implement a standalone 64-bit Live Weather Engine and hoping to provide interfaces to OpusFSI_v5 (DHM, ButtKicker, etc), FSX, FSX Steam, P3D, and XPlane sims. New 64-bit DHM and ButtKicker control software may also be developed to supplement the new Live Weather Engine. The new LWE will support all the current modes, providing Live, Historic, Relocated, Imported (user specified or supplied), and Global weather, along with the saving and loading of OpusFSI World Weather Themes. All the usual weather maps will be provided, including the Weather Locator / Overview feature. A user/developer interface will be provided to allow third-party developers to incorporate the Opus LWE, or support for the Opus LWE data into their own products. Stephen :-) |
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
OpusFSI v6 for P3Dv4 and MS FS2020
We are currently in the final stage of preparing and testing a new 64-bit version of OpusFSI. This version (OpusFSI v6) will be available for P3Dv4 with a separate MS FS2020 version available when the new sim is released. We will most likely be adding a fast 64-bit PDK interface for P3Dv4 users, and if possible adding any fast SDK interface to the new FS2020 sim. We will be posting OpusFSI v6 in beta form for current licensed OpusFSI v5 users to try out asap. Eventually a low cost upgrade will be offered to existing OpusFSI v5 users. Regards Stephen
|
|
![]() |
|
Opus Software ![]() Senior Member ![]() Joined: April-12-2012 Location: Grantham, UK Points: 13893 |
![]() ![]() ![]() ![]() ![]() |
OpusFSI v6 for P3Dv4 The fast 64-bit OpusPDK interface has now been added so it will be included in the first beta. I have also added a PDKSETUP program which will make all necessary changes to setup the OpusPDK interface. Stephen
![]() |
|
![]() |
Post Reply ![]() |
Page <1 161718 |
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 |