|
MSFS 2020 |
Post Reply 
|
Page <12345> |
| Author | |
Brisi 
New Member 
Joined: October-09-2020 Location: Schweiz Points: 7 |
 Post Options
 Thanks(0)
 Quote Reply
 Posted: October-10-2020 at 10:54am |
|
yes it is not a motorized one.
I cleaned up and restarted spy. it shows exactly that as before. DEV RX: AA4B DEV RX: AA 49 AA 47 and so on ... |
|
 |
|
|
Opus Software
Senior Member 
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 10:54am |
|
OK. Please capture the Spy response to all flap movements 1 through to 30.
Post here like I did above.
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 10:55am |
|
Capture all of them like I did using Ctrl-C and Ctrl-V
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 10:56am |
|
Like this …
SIM Event: Sim Running DEV RX : 91 6C 95 7E DEV RX : Flaps 1 DEV RX : 91 6E 95 7D DEV RX : Flaps 2 DEV RX : 91 6F 95 7B DEV RX : Flaps 5 DEV RX : 91 67 95 77 DEV RX : Flaps 10 DEV RX : 91 63 95 6F DEV RX : Flaps 15 DEV RX : 91 61 95 5F DEV RX : Flaps 25 DEV RX : 91 69 95 3F DEV RX : Flaps 30 DEV RX : 91 6D 94 7F DEV RX : Flaps 40 Stephen |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 10:58am |
|
I can then compare and sort out the Non Motorised bit differences in the messages from your TQ.
Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 11:02am |
|
You really need to do the same for any problematic area of control regarding the Opus FSCTQ driver to TQ Device COM link. I only have the Motorised TQ and their (FSC) docs aren't always very clear.
I need to know what each message from your TQ is. Stephen
|
|
|
|
|
Brisi
New Member
Joined: October-09-2020 Location: Schweiz Points: 7 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 11:17am |
|
Hi Stephen,
they are really very attentive and very quick with your answers. Unfortunately the program doesn't work. I am deleting it now. And wait for one that works. Sorry and have a nice evening. Greeting Ralf Works perfectly here with the FSC Motorised TQ and should be simple enough to determine why your Non-Motorised TQ version isn't sending the expected COM message bytes. I cannot do this but am willing to assist you. Stephen
 |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 11:22am |
|
The protocols are DIFFERENT. It’s as simple as that.
If you want to assist, it’s very simple, I will then add support to interpret your Non Motorised TQ messages. If not I will simply remove the Non Motorised option and support only the Motorised version. Makes no difference to me. I’ve only implemented a driver because the FSC one is useless and no good and operating the 737. You can’t even takeoff correctly using the FSC driver. Good luck to you if you want to stick with that. But seems silly when all you have to do is copy and paste the full Spy messages. Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 11:35am |
|
Unless of course your COM Port settings are different. Either case it would be a simple procedure to copy and paste each received flap message sequence. I made sure they were displayed in Spy for this very reason.
Can’t understand why you’d want to fly the 737 using their faulty driver. It doesn’t allow the correct engine run up and TOGA use on takeoff. Nor does it allow the correct use of reversers on landing. The calibration is poorer as well. That’s why I developed my own driver that allows for correct 737 TQ operation during flight. For now I will remove all support for Non Motorised FSC TQs and grey out the Config option. Stephen
 |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-10-2020 at 11:45am |
|
You should at the very least double check your COM Port is setup as 19200, None, 8, 1.
Cant see how our FSCTQ driver in OpusFSI v6 would work correctly as that assumes identical protocol used for both Motorised and Non Motorised FSC TQs. Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-11-2020 at 3:38am |
|
OpusMSFS Beta Versions
After this distraction I will now continue with adding ButtKicker turbulence effects, improving the landing analysis, and making a start on the CPflight MCP/EFIS panel support. I am also investigating if there's anything I can do to assist with camera views. Stephen
 |
|
|
|
|
737Andi
New Member
Joined: January-21-2015 Points: 16 |
Post Options
Thanks(0)
Quote Reply
Posted: October-11-2020 at 4:36pm |
|
Thanks for your awesome service. Its a pity that people are asking for help and get the best support they can imagine and then refrain to make a simple copy and paste work :(
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-19-2020 at 6:15am |
|
New OpusMSFS Beta
Has anyone used the Landing Analysis yet. If needed the landing grading can be adjusted and the lateral motion factored in with help from users comments and their Landings.log file content. CPflight MCP/EFIS 737 Panels 2. Allowing changes in the sim to be reflected on the panel. For example, updating the MCP panel heading display when the user synchronises the heading by pressing the heading knob in the sim. Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-21-2020 at 6:44am |
|
New OpusMSFS Beta
Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-23-2020 at 7:18am |
|
First OpusMSFS Release Version Posted
The beta period for the new OpusMSFS software has now come to an end. All OpusMSFS Beta Versions 1.00.XX will now longer be valid. An OpusMSFS licence can be purchased from our Downloads page for 14.95 USD. Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-24-2020 at 7:40am |
|
OpusMSFS Release Version 1.01.1 has been posted with corrected and revised landing analysis and landing popup. See Announcements.
Stephen
 |
|
|
|
|
737Andi
New Member
Joined: January-21-2015 Points: 16 |
Post Options
Thanks(0)
Quote Reply
Posted: October-24-2020 at 8:51am |
|
Hi Stephen,
I just tested the new version. Everything seems to be working except Buttkicker Feedback for Flaps and Spoilers. Both are active under the config dialogue and with the test button they do also respond. However when activating them with the A320 or 787 nothing happens. You might wanna check the other buttkicker effects too. Thanks! Best regards Andi
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-24-2020 at 8:54am |
|
Will do.
Thanks Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-24-2020 at 9:34am |
|
Hi Andi,I've posted OpusMSFS Release Version 1.01.2 with the fix to the ButtKicker status changes.
Thanks for the heads up, it was my bad. Regards Stephen
|
|
|
|
|
Joshsum
New Member
Joined: May-01-2015 Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: October-30-2020 at 10:20pm |
|
Hi I upgraded my MSFS yesterday and now the buttkicker software does nothing. Do we need a patch for the latest update?
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 3:04am |
|
No but Announcements told everyone to check their settings again, including your BK settings.
Best check your Configure settings to make sure it’s enabled.
Stephen |
|
|
|
|
Joshsum
New Member
Joined: May-01-2015 Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 9:05am |
|
I have done all that but I keep getting red boxes at the bottom of the BK control. If I run test they all work but when I start flying they go red again. I ll try a full uninstall and re install to see if that works.
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 9:09am |
|
I’ll take a look at it here just in case I’ve done something in latest updates. Latest update posted this morning.
Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 9:18am |
|
No all is OK.
The Control and User indicators remain Disabled (Red) until the flight is actually loaded then they turn Green.
Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 9:46am |
|
ButtKicker Control and User Enable / Disable Indicators
At present these two indicators work in unison. If the flight is specified and loaded in MSFS then the SimConnect data is meaningful and both will turn GREEN to indicate Enabled. At all other times, including when the Welcome or Flight screens are displayed both indicators will be RED indicating Disabled (no control possible due to undefined SimConnect data). The User Enable / Disable is not really meaningful at the moment as I don’t believe MSFS SDK allows any form of Add On Menu allowing users to control the ButtKicker operation. I doubt there will ever be an Add On Menu in the sim so the separate Enable / Disable indicators may combine. Also at present the BKCTRL program is only activated when the MSFS sim is running and the SimConnect links are established. The BKCTRL program can actually be started manually to aid setting up without FSISERVER or the MSFS sim active, however in this mode there will never be any proper supervised BK control. I may look to activating the BKCTRL program automatically before the SimConnect link is established with the view of helping users set up and test its configuration. Stephen
|
|
|
|
|
Joshsum
New Member
Joined: May-01-2015 Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 12:11pm |
|
Its working now that I did a uninstall and then re install. MSFS has been a challenge lately with the issues in the latest update. Thanks for the making my flight simming more enjoyable with your product. Josh
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: October-31-2020 at 12:13pm |
|
You’re welcome.
Regards Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-03-2020 at 7:52am |
|
OpusMSFS Coming Soon
In-Flight Map I'm working on adding an in-flight map option to allow users to follow the flight overlaid on a variety of sizeable and moveable road and satellite maps. Similar to OpusFSI v5 and v6, the following map options will be provided, Bing Street Map Bing Satellite Map Bing Hybrid Map Google Street Map Google Terrain Map ArcGIS Street Map Yandex Street Map Open Street Map and the following map display options will be provided, Keep Aircraft in Centre Keep Aircraft on Map Map Server Cache Map Grey Scale Map Opacity Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-06-2020 at 6:38am |
|
OpusMSFS Beta 1.02.0 has been posted with the In-Flight Map feature added.
See Announcements for details. Stephen  |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-06-2020 at 7:11am |
|
Work in Progress - Assigning Joystick Button/Key Sequence Shortcuts
I am looking to add Joystick/Key Sequence events to OpusMSFS allowing Shortcuts to be defined to change view mode, toggle the In-Flight Map on and off display, etc. Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-06-2020 at 9:55am |
|
In addition to adding a feature for assigning Joystick button or key sequence Shortcuts I will also look to adding an option to display all traffic on the In-Flight Map using different coloured bitmap symbols for the traffic. Stephen
 |
|
|
|
|
Kaselite
New Member
Joined: June-05-2020 Location: Singapore Points: 16 |
Post Options
Thanks(0)
Quote Reply
Posted: November-16-2020 at 10:57pm |
|
Hello, im having erros with the Opus MSFS client (Ver 1.03.1) on my two side view PCs. It works for a while however when i change attitude / roll quickly then the opus clients crash at different time (MSFS2020 does not crash). I seem to be running all the right versions of .net.
I do have P3D on the same machines with Opus6.
Thanks! Here is the error: Log Name: Application Source: .NET Runtime Date: 17/11/2020 11:38:10 am Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: FSIMRIGHT Description: Application: FSICLIENT.EXE Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.SimConnect_CallDispatch(Void*, Void (SIMCONNECT_RECV*, UInt32, Void*), Void*) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(Microsoft.FlightSimulator.SimConnect.SignalProcDelegate) at ae.DefWndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef) at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32) at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) at ap.a(System.String[]) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-11-17T03:38:10.9425084Z" /> <EventRecordID>21424</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>FSIMRIGHT</Computer> <Security /> </System> <EventData> <Data>Application: FSICLIENT.EXE Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.SimConnect_CallDispatch(Void*, Void (SIMCONNECT_RECV*, UInt32, Void*), Void*) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(Microsoft.FlightSimulator.SimConnect.SignalProcDelegate) at ae.DefWndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef) at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32) at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) at ap.a(System.String[]) </Data> </EventData> </Event> |
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 2:23am |
|
Thanks for the detailed report. I will test the client again here, although my second system is in the process of having Win10 reinstalled due to a drive C crash.
Please try running the latest Beta Version 1.04.0 and see if the problem persists. Version 1.04 uses the updated SimConnect SDK from MS and Asobo. Regards Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 2:32am |
|
I will also be posting OpusMSFS Version 1.04.1 (as a beta or release, not quite sure yet) today which uses the very latest updated MSFS SDK 0.7.1.0 from MS and Asobo.
If you could download and try that when its posted, keep an eye on Announcements. Just in case the older SDK has incompatibilities with the newer upgraded SDK (SimConnect). After you upgrade to 1.04.1 (using the new MSFS SDK) run the Live View Tests again, client side followed by server side. Regards Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 4:40am |
|
I have posted OpusMSFS Release Version 1.04.1, see Announcements.
I was able to test the OpusMSFS FSICLIENT connected to an OpusFSI v6 P3DSERVER program connected to P3Dv5. All worked fine running the Live View Test from the server end. I had the 'Auto Height Adjustment' option enabled in the client and also added a 0.02 'Vertical Axis Offset'. I suspect your problems may have been due to an incompatible MSFS SDK version. The latest release is using the current 0.7.1.0 MSFS SDK so should be OK for compatibility. Regards Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 5:13am |
|
OpusMSFS Work In Progress I am now investigating adding support for Navigraph NavData options on the In-Flight Map. The NavData source will be identified and loaded via the FSISERVER's Configuration dialog. This will be done in a similar manner to OpusFSI v6 where a Default (out of date) set of NaviGraph NavData will be provided with an option to browse and identify the location of your current subscribed copy of NaviGraph's NavData. A 'Reload' option will be provided to convert the identified NavData source into quick access CYCLEINFO, AIRWAYS, NAVAIDS, and WAYPOINTS data files. The current Cycle Information will be displayed in the NavData dialog. I will look to add the following options to the current OpusMSFS In-Flight Map, Show Airway The 'Show Airway' option will be associated with a single text box allowing the required airway to be specified. When anabled the specified airway and all associated NavAids and Waypoints will be plotted on the In-Flight Map. The 'Show Aerodromes' option will be associated with four text boxes and an 'All' checkbox. The 'All' checkbox will allow all known aerodromes to be plotted on the In-Flight Map. The four text boxes will allow up to four aerodrome ICAO codes to be specified for plotting on the map. Similarly, the 'Show NavAids' and 'Show Waypoints' options will each be associated with an 'All' checkbox and four text boxes, the text boxes allowing up to four NavAids or Waypoints to be specified and plotted on the map. It is not possible to obtain details of your current flight plan from the simulator via the limited MSFS SDK at the moment, but the above options should allow you to plot the Airways, NavAids, or Waypoints that are relevent to your flight and location. Stephen
|
|
|
|
|
Kaselite
New Member
Joined: June-05-2020 Location: Singapore Points: 16 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 7:56am |
|
I will test and report back later tonight. thanks!
|
|
|
|
|
Kaselite
New Member
Joined: June-05-2020 Location: Singapore Points: 16 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 9:38am |
|
I downloaded the new SDK and installed the "core components" - exactly the same issues with the 1.04 beta. It lasted a little longer before the crash.
Process: uninstalled the 1.03 clients / server Installed the 1.04 clients and server Downloaded the SDK Stopped MSFS 2020 Installed the SDK Did not reboot Started the MSFS clients Started server started clients Client test button does not cause a crash. Crash only occurs during normal flight mode, just after take off. Camera.cfg has been modified to setup the left and right views correctly
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-17-2020 at 9:43am |
|
Thanks I will setup something to recreate the same thing here. My client system is still being fixed after its disk crash but I can run two sims on my main dev system and try to recreate it.
I will report back. Regards Stephen
|
|
|
|
|
Opus Software
Senior Member
Joined: April-12-2012 Location: Grantham, UK Points: 15407 |
Post Options
Thanks(0)
Quote Reply
Posted: November-18-2020 at 7:05am |
|
I have posted OpusMSFS Beta Version 1.04.2, see Announcements.
This is linked to the latest MSFS SDK. There is no need to download and install the MSFS SDK as SimConnect is in-built within the MSFS sim. In fact, unless you are using the SDK its best no to install it otherwise you may be forced to keep it updated. For Live View users must ensure all sims are running with flights loaded and ready before running the OpusFSI or OpusMSFS server and client software. Run the server program first then run each client in turn. If your OpusMSFS FSICLIENT program crashes please post the expanded crash report so I can see where the program failed. I have found no errors here but will have a new client system set up in the next week or so. Regards Stephen
|
|
|
|
|
Post Reply
|
Page <12345> |
| 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