UPLOADED: Spitfire Mk.II Package

mongoose · Oct 28, 2019

I have not actually flown the Spit or the FW 190A which I am now realizing was a precursor for your new system. The readmes do require quite intense studying and digesting; if only to redo all the keyboard/controller bindings which is what I am looking at when I have time. First i am sorting those out and then the pilot instructions will follow, which will require some personal note taking and I will put on a side screen when I start to fly. These 2 ac types offer so much more realistic controls that it is not something to rush in to, but should be well worth it. IMHO they should make WOTR of less interest!

mongoose · Oct 28, 2019

So, forgive the ignorance as I have never used non standard CFS3 keystrokes, but if I have the FW190A and Spitfire Mk. II keytrokes on my X56 control System and am flying through the respective modules, will the new keystrokes work automatically?

gecko · Oct 28, 2019

If I understand you correctly, yes. I take it that you mapped the key strokes to be sent by buttons on your x56. With the Spitfire you do have to assign the new controls to a key or button using the normal CFS3 in-game key-mapping menu. With the Fw 190, the keys are not configurable, so you just assign your x56 buttons to send the appropriate key for the desired function.

Frosty · Oct 29, 2019

gecko said:
Any other TrackIR users having issues? Or is it working well for most?

Also curious how people are doing with flying the aircraft itself? Did the manuals help and are there any areas that need to be covered better?

Too soon to tell; I am reinstallling a vanilla ETO v1.50 to see if I can get my TiR to work with the Spit.

BUT I got two questions in the meantime: I was going through the vanilla ETO v1.50 effects.xml which is giving some trouble opening in XML Notepad. It noticed a double attribute in line 991, position 113 and line 1048, position 72. I assume I can delete one of the double "Effect0" entries for the first and rename the second hickup to "Effect1"? I also noticed there were quite a few instances of "Roration". I take it these are typos and should read "Rotation?

MajorMagee · Oct 29, 2019

Roration is in fact a valid typo going back to someone at MS when they were developing CFS3, and changing it to Rotation will interfere with its proper functionality.

Duplicate effects are sometimes done on purpose so you would have to experiment to see if renaming one has a positive or negative impact on the animation.

Frosty · Oct 29, 2019

MajorMagee said:
Roration is in fact a valid typo going back to someone at MS when they were developing CFS3, and changing it to Rotation will interfere with its proper functionality.

Duplicate effects are sometimes done on purpose so you would have to experiment to see if renaming one has a positive or negative impact on the animation.

I see, thanks. So that would fall into the category of intentional CFS3 typos, such as "guages" and "attatch".
I'll start a new thread, as this is diverging too much from the original topic and this tickles my curiosity. See http://www.sim-outhouse.com/sohforu...3-effects-xml-questions?p=1200690#post1200690

gecko · Oct 29, 2019

Frosty said:
Too soon to tell; I am reinstallling a vanilla ETO v1.50 to see if I can get my TiR to work with the Spit.

Joost, did you try the things I suggested with that a couple posts back? It will help me determine the cause.

Frosty · Oct 29, 2019

gecko said:
Joost, did you try the things I suggested with that a couple posts back? It will help me determine the cause.

Yes and no: killing your script didn't bring TiR functionality back but I haven't finished reinstalling ETO v1.50. I'll continue that tonight when I get home and leave all mods out except the Spit + the module and see how that goes. I did seem notice however that my TiR is very dependent on the compatibility set for the CFS3.exe. I'll let you know!

mongoose · Oct 29, 2019

gecko said:
If I understand you correctly, yes. I take it that you mapped the key strokes to be sent by buttons on your x56. With the Spitfire you do have to assign the new controls to a key or button using the normal CFS3 in-game key-mapping menu. With the Fw 190, the keys are not configurable, so you just assign your x56 buttons to send the appropriate key for the desired function.

So for the Spitfire keystrokes, I should ?:-

1. Add them manually to the Flight Simulator.xca file such as <Key ID="C" Mod="Control" Action="Cockpit Door Close"/>
etc. BTW is "Alt" the full word or short for something?

2. Then add those to my X56 profile

While for the F190A I can just add them directly to my X56 profile?

Also noted "[FONT=Helvetica, serif]Radiator Shutter Close Ctl + Alt = R"
I assume meant to be "Radiator Shutter Close Ctl + Alt + R" ?[/FONT]

gecko · Oct 29, 2019

James, yes, that's it, though you don't have to add the controls manually to the xca. You can just configure them using the in game menu like you would for any normal stock CFS3 key binding.

Joost, I'm beginning to suspect your TrackIR problem is not related to the Spitfire add-on, but keep me posted just in case.

mongoose · Oct 29, 2019

I think I find it easier in the xca which I will then post here for others. Just a ? of "Alt" being short for something else as "Ctl" is for "Control" ?

AnKor · Oct 29, 2019

"Alt" is full word, you can use it in xca.

mongoose · Oct 29, 2019

OK. I've added the below to the Flight Simulator.xca file and re named the whole file as 'Spitfire MK II Module.xca" in line with the "Fw 190A Module.xca". However I note that the new keystrokes aren't actually showing up on the in game control options when I select the xca's (although they also are in my AppData folder); see pic below. I haven't tested them yet as not ready to fly, but any thoughts? I sort of suspect it may not matter.

<Key ID="C" Mod="Control" Action="Cockpit Door Close"/>
<Key ID="C" Mod="Alt" Action="Cockpit Door Open"/>
<Key ID="L" Mod="Control+Alt" Action="Landing Light Extend/Retract"/>
<Key ID="R" Mod="Control+Alt" Action="Radiator Shutter Close"/>
<Key ID="R" Mod="Shift+Alt" Action="Radiator Shutter Open"/>
<Key ID="F1" Mod="Shift" Action="Coffman Starter Re-Index"/>
<Key ID="1" Mod="Alt" Action="Fuel Cock Bottom Tank Toggle"/>
<Key ID="2" Mod="Alt" Action="Fuel Cock Top Tank Toggle"/>
<Key ID="3" Mod="Alt" Action="Generator Toggle"/>
<Key ID="L" Mod="Control" Action="Landing Lights Toggle"/>
<Key ID="4" Mod="Alt" Action="Landing Light 1 Toggle"/>
<Key ID="5" Mod="Alt" Action="Landing Light 2 Toggle"/>
<Key ID="G" Mod="Control+Alt" Action="Landing Gear Emergency Extension Engage"/>
<Key ID="6" Mod="Alt" Action="Landing Gear Position Light Toggle"/>
<Key ID="7" Mod="Alt" Action="Landing Gear Warning Horn Silence"/>\
<Key ID="N" Mod="Alt" Action="Navigation Lights Toggle"/>
<Key ID="S" Mod="Control+Alt" Action="Starter Cover Toggle"/>
<Key ID="F" Mod="Control+Alt" Action="Fuel Quantity Bottom Display"/>
<Key ID="F" Mod="Alt" Action="Parachute Flare Release"/>
<Key ID="{" Mod="Alt" Action="Gunsight Brightness Decrease"/>
<Key ID="}" Mod="Alt" Action="Gunsight Brightness Increase"/>
<Key ID="{" Mod="Shift" Action="Gunsight Range Decrease"/>
<Key ID="}" Mod="Shift" Action="Gunsight Range Increase"/>
<Key ID="\" Mod="Shift" Action="Gunsight Toggle"/>
<Key ID="[" Mod="Alt" Action="Gunsight Wingspan Decrease"/>
<Key ID="]" Mod="Alt" Action="Gunsight Wingspan Increase"/>
<Key ID="A" Mod="Alt" Action="Gun Safety Toggle"/>
<Key ID="S" Mod="Alt" Action="Engine Priming Pump Operate"/>
<Key ID="M" Mod="Alt" Action="Mixture Auto-Normal"/>
<Key ID="N" Mod="Alt" Action="Mixture Auto-Weak"/>
<Key ID="X" Mod="Alt" Action="Slow Running Cutout Engage"/>

AnKor · Oct 29, 2019

You should use special names like "COCKPIT_DOOR_CLOSE" instead of display labels like "Cockpit Door Close". You also can't use special symbols (like [ ] { } \ ) in key names, they should be referred by their names.
That's why gecko said it is easier to use controls menu.

But here I fixed your list to save you some time.
Should be all as you set, except I had to modify gunsight controls because "{" is just "Shift+[". I don't remember if these match the old gunsight controls, can't check right now

mongoose · Oct 29, 2019

Thanks for that. I'm moving all my new comments to a new thread as I'm actually looking at both the FW190A and Spitfire Mk. II at the same time so I want to get off this Spit only thread,

Frosty · Oct 29, 2019

gecko said:
Joost, I'm beginning to suspect your TrackIR problem is not related to the Spitfire add-on, but keep me posted just in case.

I installed the Spit in vanilla ETO v1.50 without shaders v.2019-10-22 to see where the problem lies:

- If I start ETO using the cfs3.exe, TiR works fine but of course I can only fly the Spit the 'old way', without the RS module.
- If I start ETO using the RS module, it also starts fine, but there is no TiR: No head tracking, no blue LED on the camera. Bringing up the task manager to kill the Systems_TIR.exe process doesn't do a thing; TiR still stays dead. I have a TiR v4 camera and I run software version 5.4.2.27545.

- Shaders v2019-10-22 simply make CFS3 crash on start-up (It gets to the screen filling second splash screen, sometimes with the UI background noise already audible) but the blue LED does come on.
- TiR and CFS3 work fine in my other installs and in combination with shaders v.2018-01-17

Getting a little frustrated here because I can't find the problem and it already kept me two days from doing other stuff :banghead:

.

gecko · Oct 30, 2019

Frosty said:
I did seem notice however that my TiR is very dependent on the compatibility set for the CFS3.exe.

What are the details here?

When I open my cfs3.exe properties and click the compatibility tab, none of the boxes are checked. The same goes for TrackIR5.exe. One possibility is that when the Real Systems Module runs CFS3, it runs it as administrator, so maybe something with that is causing TrackIR not to pick up on the fact that CFS3 has been launched?

Also, the head tilt won't work without the 2019 shaders, though there is nothing that should disable the rest of TrackIR if that version is not installed. Your TrackIR software is the latest and the same version I use, so no problems there. Rob tested the function successfully on a TIR4 camera, and I use a TIR5, so everything should be good there too.

I'll look through the shaders issues as well and see if I can come up with anything.

EDIT: see the shaders thread for a possible fix for your shaders issue. Fingers crossed.

Frosty · Oct 30, 2019

I now have set the compatibility of CFS3 to nothing (boxes unchecked) and have set CFS3, TiR and the RS Module to "Run as Administrator". That seemed to do the trick in runnning CFS3 with the Spit installed and with TiR functionality! But the shaders still make CFS3 crash (even with the latest version you posted). To be continued!

gecko · Oct 30, 2019

Well, one gremlin down, one to go!

mongoose · Oct 31, 2019

I am doing pics of the pit with labeling for my and others use but don't see any reference even in the pilots notes as to what this is. Not important but interesting!

UPLOADED: Spitfire Mk.II Package

SOH-CM-2023

SOH-CM-2023

Charter Member

SOH-CM-2022

SOH-CM-2022

SOH-CM-2022

Charter Member

SOH-CM-2022

SOH-CM-2023

Charter Member

SOH-CM-2023

Members +

SOH-CM-2023

Attachments

Members +

SOH-CM-2023

SOH-CM-2022

Charter Member

SOH-CM-2022

Charter Member

SOH-CM-2023

Attachments