Hey there,

 

since neither google nor searching this forum gave me any results, I'll just aks and hope this hasn't been answered elsewhere.

 

I recently purchased OpusFSX and switched over from using EZdok to use OpusFSX' Live Camera. I was able to set up the views for most of my add-on aircraft, but I'm not able to get the iFly 737 NG planes to show up in OpusFSX' Aircraft Types list. I checked all my permissions and everything seems okay. Is there anything special to consider when setting up the iFly views or am I just being stupid.

 

Thanks for your replies.

 

Gordon

 

PS: I'm using a single machine setup.

Hi Gordon

 

Does the iFly 737 NG plane have a panel folder ?

 

Check the <SIM>\SimObjects\Airplanes\<Aircraft Name>\ folder and let me know if there is a 'panel' folder.

 

Also this extract from our FAQs might help ...

 

The camera dialog doesn't list all my aircraft

 

Ensure your aircraft.cfg file is not corrupted and the file attribute is not 'read only'.

 

My aircraft disappeared from the FSX list

 

When you open/edit an aircraft.cfg file in Notepad, select File - Save As ...

You will see the Encoding type in the bottom right-hand corner of the dialog. This should be set to ANSI.

 

Also make sure you ran the EZCA Restore utility to remove the EZCA definitions. You can also put all your FSX key settings back to default if you wish as well to get the hat switch panning back.

 

Beta Version 3.46.2 has just been posted, testing some new view transitions if you fancy giving it a go, or wait a short while for it to be posted as the next release version if you wish.

 

Stephen :smile:

Hi Stephen,

 

thanks for your quick reply.

 

If the panel folder is needed, then I can see, what the problem seems to be. The iFly 737 comes with different panels for fullscreen and widescreen monitors and thus there are two different panel folders in the aircrafts subfolder. One of them is called 'panel.normal' and the other one is called 'panel.wide'.

 

If I rename one of them to 'panel' the aircraft does indeed appear in the Aircraft Types list. I have no idea, if the iFly still works, when renaming those folders, but I doubt that. Nevertheless I will test it, for example by copying the panel.wide folder and rename the copy 'panel'.

 

For the beta, I will definitely take a look

 

Thanks,

 

Gordon

Many thanks Gordon,

 

A recent beta and release removed aircraft that did not have a panel folder. My mistake I should check for any folder with 'panel' anywhere in its name. I will correct this problem and should be able to post a new beta tomorrow. Sorry for any inconvenience.

 

Don't bother renaming them unless you want to do it on a temp basis. But you will have to modify the relevant aircraft.cfg file as well (or the file that identifies the panel folder). I will post a beta with the fix ASAP.

 

Regards

Stephen :-)

Hey Stephen,

 

great news. I was just starting to write a batch, which would place symbolic links in the aircrafts folder to fool OpusFSX into thinking the 'panel' folder is actually there even though it is not. Well, seems that I don't have to bother anymore.

 

I'm looking forward to the beta, thanks for all your work

 

Gordon

You're welcome.

 

Stephen :-)

Gordon

 

Got back on the computer so I've prepared and posted a new Beta Version 3.46.3 for you to try with your iFly 737 NG.

 

Regards

Stephen :biggrin:

Hey Stephen,

 

that was pretty fast

Unfortunately I get a Microsoft .Net error when I try starting up 3.46.3. Don't know if this happens just for me or everyone. I will try a few things und keep you up to date.

 

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.DllNotFoundException: Unable to load DLL 'fsgencom.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at FSSYSTEM.FSGencom.fsgencom_init(Byte A_0, UInt32 A_1, Char[] A_2)
   at FSSYSTEM.FSGencom.Gencom_Init(UInt16 taskID, Byte pm, UInt32 bn, UInt32 gn, String path)
   at bo.v(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8000 (FX35W81RTMGDR.050727-8000)

----------------------------------------
FSXSERVER
    Assembly Version: 3.4.6.3
    Win32 Version: 3.4.6.3

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.7905 (win9rel.050727-7900)

----------------------------------------
FSXSYSTEM
    Assembly Version: 3.4.6.3
    Win32 Version: 3.4.6.3

----------------------------------------
Microsoft.FlightSimulator.SimConnect
    Assembly Version: 10.0.61259.0
    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.8428
    Win32 Version: 8.00.50727.8428

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 

 

Regards

Gordon

This has been reported elsewhere as well. Looks like the uploaded OpusFSX.msi file is corrupted.

 

I will rebuild it and upload it again.

 

Thanks for the report.

Stephen

I have rebuilt it and uploaded a new Beta Version 3.46.3 for you to try.

 

Stephen :-)

...and now it works like a charm. Once again, thank you very much, sir :-)

Glad to hear you're all sorted.

 

Regards

Stephen