arnonmoscona

Awesome! This is exactly what I was looking for. Thanks!

Yes. I realize that. That's the point though - what I would like to do is use OpusFSI cameras etc. but instead of using live weather I want to sometimes use Weather Architect with custom weather. If I use it by itself and don't have OpusFSI running, then I get the custom weather but lose the cameras, the TrackIR, and the effects. So the question is: is there a way to use both together? BTW: the OPpusFSI team says no. But maybe someone figures out a way to do it anyway...

Hi! I use OpusFSI for real weather as well as the cameras. That works for me quite well. However, I am interested in flying some times with completely custom weather. So REX Weather Architect looks very attractive for this. But, if I decise to get it, I would like to get the weather from REX Weather Architect, while using the cameras and TrackIR integration from OpusFSI. So my question is: can the weather functionality of OpusFSI be temporarily deactivated such that I can use another weather engine without losing the rest of the OpusFSI functionality? Looked in several places and could not find a discussion on this subject. Ideas?

This is a known problem. You can only start Opus while a flight is loaded. Opus claims that it's a p3d problem. No word on a fix to date.

I've been using OpusFSX (not FSI) since P3D 2.0 came out. It works. The camera features work well. So does the dynamic head movement. The UI is a bit weird, but after you get used to it, it's fine. There are a couple of things to watch out for. Neither is critical if you know what to do. You have to start OpusFSX only after you're in a flight situation (in the cockpit, not in the situation setup UI), or else you get a CTD in P3D. I don't know whether this has been fixed yet with OpusFSI+P3D 2.4 You really should not use "bump aircraft" (checkbox unselected) in the DHM options dialog (whatever it's called) See http://www.opussoftware.co.uk/opusfsi/Opusfsi_Server_DHM.jpg the "bump aircraft" checkbox should not be checked. if it's checked then your performance can suffer greatly and you can get severe pauses and unresponsive controls Other than that, I love it!

The problem is not fixed in P3D 2.3 Any way to create a work around of some kind? It's fairly annoying to start the SIM, setup the flight, get into the flight and then get out of the SIM start opus fsx and go back to the SIM, and then wait for the weather to come in... I mean, it works, but there's got to be a better way...

For me, it has pretty much the same symptoms. If I start OpusFSX after a flight is loaded then it works. But if I start it when the create scenario screen is up then it leads to a CTD.

Yes. It looks nice. But I would not recommend it. The Carenado G1000 is quite partially implemented and shows quite a few odd behaviors I've had problems with it picking up ILS (say, in Yakutat PAYA) where I could do it with no problems using other aircraft (e.g. A2A C172) My FSX setup is quite reasonably tuned, but this aircraft behaves very badly for me when flying manually (OK on AP as long as you don't have problems with nav aids). I mean, After a missed approach at PAYA I went around, flying manually, on final it started behaving very oddly, and suddenly it started flying backwards!! The cockpit instruments did not show it, but the scenery was flowing past backwards. I swear it! I double checked that I was not on a helicopter :lol: Never, ever saw any flight model like this on a fixed wing aircraft... I've nearly given up on this baby, as good as it looks. Waste of money. If you are really interested in learning the G1000, I'd say - go with the best one out there, which is (apparently) the Flight1 Super King Air B200. If you have to have it in a business jet (would be nice, no?) then maybe the Flight1 Cessna Mustang will fit the bill. I did not try that one. It is said to be quite good, although it appears to be a frame rate killer (as is the Carenado Phenom)

My mistake. I did not uninstall the previous version before installing the latest one. After uninstalling and reinstalling, the trainer no longer crashes. I have not had the chance yet to actually go through the training and test FSX with the new version. When I get around to doing that I'll report any problems if there are any. It would be nice if future versions of the installer would warn you about an existing installation, or would automatically uninstall the existing version before proceeding.

For me the flight plan trainer still doesn't work. I get a crash: Hi! I am experiencing a crash of the flight plan trainer. This happens when I click the general training button. See details below. Please advise. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.BadImageFormatException: Could not load file or assembly 'Interop.SpeechLib, Version=5.3.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format. File name: 'Interop.SpeechLib, Version=5.3.0.0, Culture=neutral, PublicKeyToken=null' at VATrainer.Form1.Form1_Activated(Object sender, EventArgs e) at System.Windows.Forms.Form.WmActivate(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- VATrainer Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- ************** 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. Oh, and on top of that the contact form on the web site does not work ("processing error")

Doesn't work for me. AutoTrim=False and still after takeoff the trim wheel goes crazy. After some time I can stabilize it, but the first 2-3 minutes after takeoff are almost uncontrollable. Constantlyh fighting and extreme tendency to pitch up. Depending on the aircraft, it may be impossible to control (i.e. in a Maule I can eventually stabilize it. In an F35 - forget it.)

No problems here. Using FSX and P3D V2.2 on the same machine.

I've been running GTX770 4GB without OOM problems. mainly FSX. BUT, I don't fly heavies.

Does anyone know how to get the phenom to start cold and dark? Even if I start the SIM in a parking space it still starts with engines on...

OK. Good news for you. Yesterday I upgraded my GPU from the ATI 5800 1GB I had there before to EVGA nvidia 770 4GB. No other tweaks or changes made. No CPU overclocking (actually my BIOS prevents me from overclocking anyway). The results were nothing short of astounding. Both on FSX and on P3D. The max FPS I was able to squeeze out of this box before, with any aircraft was maybe 26. Never even sustained 30. Immediately after upgrading the GPU, my FPS shot up to the 60s. More importantly, difficult combinations of weather and scenery that used to drop my FPS to an unfliable 7-8 FPS are now running quite comfortably at about 20FPS, which is not fast but totally usable. So the prevailing wisdom that GPU upgrades don't do much is totally bunk. If you had an under-powered GPU before - specifically an ATI 5800 series, and you upgrade to a reasonably up to date nvidia GPU you get a huge boost in performance immediately. This is not to say that an upgrade from a 680 to a 770 would do the same. I wouldn't know. i am pretty sure that doubling my price to get 780ti would probably only marginally improve performance. But this particulat upgrade is just spectacular in FPS terms. The same (even better, actually) on P3D. Thre the performance improved even more than on FSX (which is to be expected, as they use the GPU better). Now all of that said, and it's still early for me with less than a day with the new GPU, some add-ons in some sceneries (e.g. Carenado C210 with ORBX NCA near SFO) started displaying some weird behavior after the upgrade, and I don't quite understand yet what's going on there. I get really severely delayed response to stick input. I try to back, and it takes a couple of seconds before it responds. I did notice that this odd behavior is location specific, as it does not happen with the same aircraft in, say ORBX PNW, and I don't quite see why this would be related at all to the GPU upgrade. I guess I will have to tinker with things before I find out...