DickB, Using the method in post #5, F9 is going back to the new view that is made (the one perhaps called my virtual cockpit). And then from there the A key will get back to the original cockpit view.

 

Actually I am using the method you suggested (post # 2) for some planes, the method in post #5 in others.

 

Such as the A2A Piper Cub where the feature of Wendy in the passenger seat post #2 seems better, without Wendy I prefer #5.

I believe that changing the eyepoint in the aircraft.cfg will change the position (for that aircraft only) of any camera view defined with origin=Virtual Cockpit. So typically it is likely to change VC panel views, co-pilot view etc. It won't affect any external or 2D views.

 

I was wondering if it was due to the fact they were defined by relative or absolute coordinates.

 

The obvious solution would be to change them to "origin=center" and do the math to adjust the camera coordinates for each camera (presumably add the camera coordinates to the eyepoint to get the absolute coordinates). Though I have never tried it, don't see why it wouldn't work.. .. ..

 

G

^{DickB, Using the method in post #5, F9 is going back to the new view that is made (the one perhaps called my virtual cockpit). And then from there the A key will get back to the original cockpit view.}

^{Thanks Fielder - that's not what I expected. I'll have to revisit that !}

 

I was wondering if it was due to the fact they were defined by relative or absolute coordinates.

 

The obvious solution would be to change them to "origin=center" and do the math to adjust the camera coordinates for each camera (presumably add the camera coordinates to the eyepoint to get the absolute coordinates). Though I have never tried it, don't see why it wouldn't work.. .. ..

 

G

 

I agree - that should work. Bit of a chore though !

I agree - that should work. Bit of a chore though !

 

Actually looking at it I don't think it would as "CENTER" is for external cameras. So I guess the only option to get the default F9 would be to edit all of the cameras individually once you are happy with the position.

 

Major chore !!

 

G

Fielder, on 05 January 2013 - 01:28 AM, said:

 

In fact f5.csv and runways.xml is not anywhere on my computer (according to using SEARCH).

 

Gazzereth said:

It works fine here, you just need to run the makerwys utility (read the instructions)...

 

That creates the file so SimLauncher knows what airports/runways/parking is in your FSX...

 

Me again:I ran Makerwys.exe, it produced a new version of g5.csv

 

It did NOT make a runways.xml (such a file so named is nowhere on my computer after running makerwys.exe

It did NOTmake a runways f5.csv (such a file so named is nowhere on my computer after running makerwys.exe.

 

it DID also make r4.csv, airports.fsm, r5.csv, runways.csv, and runways.txt

 

But simlauncher is looking for f5.csv and runways.xml (neither of which makerwys.exe produces on my system).

Therefore simlauncher will not run, as it will not get past its set preferences screen.

I suspect the makerwys.exe on my installation is an old one.

I don't use FSUIPC for anything. Instead I map my 6 flight controllers with CH CM and its CMS scripts (controllers are all CH branded).

I had the same problem, think I needed to get the latest version of makerwys to get the .xml file....

 

G

Actually looking at it I don't think it would as "CENTER" is for external cameras. So I guess the only option to get the default F9 would be to edit all of the cameras individually once you are happy with the position.

 

Major chore !!

 

G

 

I can't help feeling there is an easier way to do it, and that I misled myself all those years ago. I'm inclined to take a fresh look at it, but I'm also considering moving to OpusFSX Live Camera for my views (and other stuff), so I might see how that works first.

I have been trailing the pack!

 

I had older version of simlauncher, not the latest.

I had older version of makerwy.exe , not the latest.

 

 

I menitioned CH CM, I noticed on the A2A board a short while ago about all 25 or so P40 commands (and even more Spitfire commands) that are made with a mouse only (no FSX commands correspond): FSUPIC can trap the code in FSX and allow programming all those mouse commands onto controllers (e.g. a yoke , flightstick, quad, etc. that has DX hats). CH CM cannot do that!

 

So FSUIPC is more advanced product for mapping commands (to say the least).

 

A modern jetliner software add-on with all the zillions of associated mouse interfaces: I don't believe anybody has trapped and mapped those, like a certain user in the A2A warbirds forum has done.for A2A's warbirds (like the P40 in my avatar).

 

simlauncher is awesome (you need the updated files from Pete Dawson's site) (I've only used it 5 minutes). Already I see it can do a ton of stuff, like it automatically checks your ORBX FTX applet to see what region you have set (Australia, NA, Europe (England!) and sees all your weather files (ORBX installs several with their scenery).

 

So, I've learned a lot here in this thread!

 

I can't help feeling there is an easier way to do it, and that I misled myself all those years ago. I'm inclined to take a fresh look at it, but I'm also considering moving to OpusFSX Live Camera for my views (and other stuff), so I might see how that works first.

 

Just remembered something that may help. If you define a camera as detailed earlier you can add the line:

 

Hotkeyselect=1

 

Which sets it to F9. I think you can go up to 10 and define the keys through the controls dialogue...

 

G

I have been trailing the pack!

 

I had older version of simlauncher, not the latest.

 

Get used to it with SimLauncher, Maarten is constantly developing it, so it updates often.

 

It is fantastic though!!

 

G

Just remembered something that may help. If you define a camera as detailed earlier you can add the line:

 

Hotkeyselect=1

 

Which sets it to F9. I think you can go up to 10 and define the keys through the controls dialogue...

 

G

 

You can indeed assign a hotkey to any view. But then you come to the next problem (again, if I remember correctly), which is that although the hotkey will snap to the required view, if it happens that you had panned that view last time you used it, you will get the panned view, not the initial setting. And for the VC view, I wanted to snap to the original forward view.

 

But then I'm just picky :rolleyes:

if it happens that you had panned that view last time you used it, you will get the panned view, not the initial setting. And for the VC view, I wanted to snap to the original forward view.

 

I'm using this "unintended feature" heavily in one aircraft I fly. You can reset the forward view by hitting the space bar, which puts you in mouse look mode temporarily and has always reset my view to forward. If you're using TrackIR, using the Center function does the same thing.

 

Hook

I'm using this "unintended feature" heavily in one aircraft I fly. You can reset the forward view by hitting the space bar, which puts you in mouse look mode temporarily and has always reset my view to forward. If you're using TrackIR, using the Center function does the same thing.

 

Hook

 

I didn't know that Hook - I must check it out. Although most of the time I fly without a keyboard :unsure: