Live Camera

Opus Software wrote: Do you mean virtual cockpit XYZ limits for the TrackIR device and I suppose for camera view editing?

paulnd wrote: Hello Stephen, Could I make a suggestion that may enhance Live Camera? It would be useful to be able to set and save limits for camera movement per aircraft to prevent inadvertently moving out of the cockpit, in effect defining the boundaries of the cockpit. regards Paul

Hi Stephen,

If you do apply camera setup movement limits, can you make it an optional check box. In order to set up my views, I need to go beyond the cockpit walls.

Thanks,
William

I took the plunge yesterday and installed last night.  Been testing today.  I REALLY like the LWE.  I took off from New Orleans after a quick check to see where there was significant weather in the US.  Very, very realistic experience.  There was some nice turbulence on takeoff and landing that I've not experienced before in FSX. 

EDIT: I've figured out exactly what is wrong I believe.  I've flown in windowed mode so I can keep an eye on things. 

FSXSERVER stops.  A LOT.  I set up TrackIR, and set up a camera view for my aircraft (RV-7) and enabled DHM.  I have EZCA, but removed the auto start feature for that from my exe.xml and so it's not running.  I've double checked that.  Not running at all.  I notice, though, that the default camera views I've set for my planes with EZCA are where I am situated in the VC however.  I suppose they are written into .cfg files somewhere.  I'm fine with that.

But, once I take off with both TrackIR and DHM running, FSXSERVER stops.  I'm testing now just sitting on the runway and so far, FSXSERVER remains running.  I've tried with several different aircraft, using both cameras I've created for each, and the default camera for all aircraft (for which I've also enabled DHM).

When it stops (FSXSERVER has stopped working...) and I exit the error message, there is still an icon on the task bar showing TrackIR interface connected, and TrackIR continues to work.  I have to exit this Dos connection before re-starting FSXSERVER or TrackIR won't work upon restart.  Once I restart, though, it only works for a few seconds up to a minute, and then stops again.

I can't seem to get FSXSERVER to run for more than a minute or so once I'm in the air.

Also, I can only turn my head about 90-95 degrees with TrackIR working.  My settings have always allowed me to turn my view all the way behind me, as is necessary and useful.  I need to be able to see at least 150 degrees behind me to judge my turn onto base.  Nothing I do in TrackIR settings seems to make any difference.  Does the TrackIR implementation in Opusfsx only allow for about 90 degrees of yaw movement?

So, not having a lot of success with cameras, which is at least 50% of why I am interested in this software.  Was hoping to be able to stop using EZCA, since it also seems a bit buggy (sometimes crashing FSX on startup).  It's more stable than my experience with Cameras in OpusFSX so far, though, and I'm able to look fully around with TrackIR with EZCA.

I'm about to disable Live Camera and see if that makes a difference, but, of course, I need those features to run to want to keep the software.

I've just flown a couple of patterns with Cameras disabled and FSXSERVER continued to run fine.  It runs fine with Cameras enabled while not flying, it appears.  Can't understand why that is the case, except perhaps that DHM isn't really doing anything.  About to test with Cameras enabled but DHM disabled. 

I'm okay with uninstalling EZCA in order to get this working correctly, as long as I know it will.  But I believe Stephen has EZCA as well and hasn't had these problems.  Also, I really need TrackIR to be able to pan more than 90 degrees to either side with OpusFSX, or it's not usable for me. 

EDIT: Just flew a pattern with TrackIR enabled but DHM disabled and it was fine (except for the 90 degree thing).  Then flew a pattern with TrackIR disabled and enabled DHM (and AHM), and it crashed FSXSERVER.  So, it's definitely DHM on my system at least that is causing the problem. 

Jean-PaulM wrote: Griphos, No need to remove EZCA completely. Just make a backup your exe.xml before removing the following lines from it so it won't start with FSX  <Launch.Addon>   <Name>EZdok camera addon</Name>   <Disabled>false</Disabled>   <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> </Launch.Addon> If you want EZCA back, just use the backup exe.xml file. Concerning the fsxserver.exe crash, I think Stephen mentioned somewhere that AHM shouldn't be used with TIR. DHM is fine. Jean-Paul

It is enough to change the line :
<Disabled>false</Disabled> to <Disabled>True</Disabled>

It is an XML file and with that change you say that this item should be Disabled.
False means it is loaded and active.

-Per

We have a problem at the moment if OpusFSX is not installed on drive C. We will look at it tomorrow.

Regards
Cheryl

jaycee75 wrote: My controllers are all configured through fsupic and Linda and disabled in fsx. Ok looking at it, it seems that because I don't have joysticks enabled in fsx that likely the issue, as Ezca as a joystick configuration part where my yoke and my belkin virtual hid device are enabled in them. I don't really want to enable joysticks in fsx,

Opus Software wrote: If you open the main Spy window of your OpusFSX server program then press your joystick inputs then you should see the joystick event displayed in the Spy window, something like Joystick 1 Button 3. If you see the input in the Spy window that means FSX is relaying that event to OpusFSX (we ask for the events for first 6 joysticks and 32 inputs per joystick), and that means you will be able to assign the input to a camera view.

griphos wrote: with OpusFSX going and TrackIR running through it, it only goes to about 90 and stops.

We will look into it tomorrow.
Regards
Stephen

You could always just enable the controllers you want to use with Live Camera within FSX then its problem solved.

We will have a look at getting the button presses through FSUIPC4, wouldn't want you to lose all those frame rates by running EZCA, and especially to lose all the intelligent and real life DHM effects.

Doesn't need to be through fsupic as such that it detects button presses. Live camera just needs to be able to detect and control the joysticks/interfaces connected. Ezca isn't using fsupic to do that. My belkin keypad or hat switch on yoke isn't set up with Linda or fsupic.

Enabling in fsx isn't an option as it enables all controllers and leads to possible conflictions/spikes etc, as is with most things in fsx 3rd party software does it better than the original, thankfully I suppose for companies like opus to exist!

Down on the list ...

Slight problem with that one JP, our policy is not to interfere with the normal key assignments within FSX and hence do everything via user friendly dialogs. When FSX operates in full screen mode, there is a bug in FSX which prevents any dialog being displayed. The SimConnect option to allow dialogs to be displayed does not work (we have already tried it) but when we develop the Live Camera Control interface we will allow camera control and full editing to be carried out on a networked client, that way you will be able to do what you want whilst FSX is in full screen mode. We are also going to look into addding the mouse look control but haven't had time to look into whether the FSX interface works yet.

At present we have included a single transition smoothness option in the Configure dialog, but adding it to the camera view would make sense, we found different aircraft sims respond differently. So probably yes, the global transition setting will most probably be moved into the Cameras dialog.

Once in a camera view, how do you pan around?

Does it recognize the hat switch automatically?

bradrcfii wrote: Does it recognize the hat switch automatically?

You probably like many of us have disabled your controllers in fsx and using fsupic? If that the case then you won't be ale to pan using hat switch unless you re enable fsx controllers. If you we're able to pan before using Ezca it's because it has its own controller interface with controls fr panning smoothness.

Updated with today's release and tested it this evening.  I still really like the LWE.  I flew around in southern BC which had broken high cloud cover and your engine modeled that extremely well.  I never once, in 2 1/2 hours, noticed any abrupt shift in clouds or weather.

And, man, you guys have excellent service. DHM now works quite well on my D:/ install.  And what realistic DHM it is.  In addition, I was flying the Dodo.  EZCA doesn't do helicopters well at all.  I disable EZDOK when flying helis.  But your DHM was incredibly realistic in the helicopter.  Bravo.  And I also had full range of motion in TrackIR.  Overall, a smooth, user-friendly, and trouble-free experience with both cameras and weather this evening. 

Hi