Support for IL-2 Sturmovik 1946 v. 4.11

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Updating IL-2 Sturmovik 1946 to version 4.11 or above.
2.
3.

What is the expected output? What do you see instead?
Expected output: Functional TrackIR. Instead: No TrackIR response. 

What version of the product are you using? On what operating system?
Ubuntu 12.10; Il-2 Sturmovik 1946 v.4.11; TrackIR 4 Pro

Please provide any additional information below.
I have been useing Linuxtrack under Ubuntu 12.10 with IL-2 Sturmovik 1946 under 
Wine for months with no problems whatsoever for all versions until updating to 
4.11, which I think deals with 6dof. After that, TrackIR is no longer working 
with IL-2.
I know this is not a proper bug; sorry, but I didn't know where to get help. 
I'd like to know if there is anything that can be done.
Congratulations on the excellent work!

Original issue reported on code.google.com by fpin...@gmail.com on 23 Feb 2013 at 8:13

[GoogleCodeExporter]

Hello,
this is a proper bug, and I'm going to investigate it, that is for sure...
Right now, I don't own this particular edition, but I'll try to see what is 
going on in there.

There are few informations I need to get more clear picture...
Are you using the linuxtrack along with the wine bridge, or the ltr_pipe based 
solution? Which version of linuxtrack are you using?

Thank you for taking the time to report the problem,

Michal

Original comment by f.jo...@email.cz on 24 Feb 2013 at 11:32

[GoogleCodeExporter]

Hi!
Thanks for the fast reply!
I'm using ltr_pipe and, to tell you the truth, I have no idea what the "wine 
bridge" is, but sure I'd like to try it; maybe it would work.
As for what version I'm using, I've been looking around but I couldn't find 
where that info is. If you address me here, I'll get back to you ASAP. I'm 
using wine 1.4.1.
By the way, what do you mean you don't own this edition?

Fernando.

Original comment by fpin...@gmail.com on 24 Feb 2013 at 4:09

[GoogleCodeExporter]

Hi,
wine bridge in a brand new feature of the current linuxtrack - you can find the 
universal package in the downloads section of the project... In ltr_gui go to 
the fourth pane and there is a button called like Install wine plugin (or 
similar, not sure from the top of my head)...

As Track IR user, note that you'll have to "reinstall" trackir drivers - take a 
look at the What's new page of ltr_gui's help...

By not owning that edition means, that I do own the combined package of Il2, 
pacific fighters and aces whatever - it is 4.04m version I think... I should be 
able to get the 1946 in about two weeks (when the paycheck comes), so if we 
can't solve the problem this way, I should be able to try and reproduce the 
problem myself.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 24 Feb 2013 at 5:35

[GoogleCodeExporter]

One more thing - can you look into the Il2 install folder, if there is a file 
called devicelink.txt? If there is, could you send it to me, so I can take a 
look if something chaged there?

Thank you,

Michal

Original comment by f.jo...@email.cz on 24 Feb 2013 at 7:19

[GoogleCodeExporter]

Hey.

I'll try the new version of linuxtrack as soon as I have some time to play 
around with it, thanks.
I'm enclosing the devicelink.txt file from the IL-2 Sturmovik 1946 v.4.11 so 
you can have a look at it.
Again, how can I know which version of linuxtrack I am currently running?
Take care!

Fernando. 

Original comment by fpin...@gmail.com on 25 Feb 2013 at 9:21

Attachments:

• DeviceLink.txt

[GoogleCodeExporter]

Hello Fernando,
just quickly looking at the DeviceLink.txt, it doesn't seem there were any 
changes to the relevant part... 

Just out of curiosity - can you check that the devicelink is enabled in the 
conf.ini file and the port/IP address are correct? Also a firewall might be 
interfering there...

Anyway, I'll take a closer look as soon as I get my hands on the Il2 1946 and 
will report my findings.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 26 Feb 2013 at 6:20

[GoogleCodeExporter]

Hi, Michal.
I checkd the conf.ini file. The following lines are at the end, just like they 
should:

[DeviceLink]
port=6543
host=127.0.0.1

Also, I'm using no firewall.
For what it's worth, I have two different installations of the game, one 
updated up to v. 4.11 and the other up to v. 4.10.1 in which linuxtrack works 
perfectly.

Fernando.

Original comment by fpin...@gmail.com on 26 Feb 2013 at 4:35

[GoogleCodeExporter]

Hello Fernando,
the only thing I can think of right now is to use netstat to see if the sim has 
the port actually open or not...

Other than that, I have to wait till I get my hands on the thing to test it 
out...

Anyway, the wine plugin should be able solve your problem too (and give you all 
6 DOF)...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 27 Feb 2013 at 7:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello Fernando,
there is something that might be wrong - can you try to modify the conf.ini and 
add the following line below the host line:

IPS=127.0.0.1

Not sure it helps, but I think it is worth the shot...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 28 Feb 2013 at 11:01

[GoogleCodeExporter]

Hi, Michal.

I just installed the new linuxtrack version two days ago and I finally got a 
response from TrackIR in Il-2 Sturmovik v. 4.11 and, subseqently, in v. 4.11.1. 
It doesn't give all 6DoF, though: I only got pith, yaw and roll; no x, y or z 
(forward-back) movement. Maybe the game is not prepared for it. Also, 
calibration with ltr_gui doesn't seem to work when in-game.
As soon as I can (I'm kind of busy these days), I'll uninstall this linuxtrack 
version and will go back to the previous one to test that IPS line at the 
conf.ini.

So long!

Original comment by fpin...@gmail.com on 1 Mar 2013 at 7:14

[GoogleCodeExporter]

Hello Fernando,
I managed to get the simulator, so if things go well, this evening I'm going to 
try it out... As for uninstalling the new linuxtrack - it should not be 
necessary, the functionality didn't changed (if it did, please let me know and 
I'll fix it).
I'll keep you posted,

Michal

Original comment by f.jo...@email.cz on 4 Mar 2013 at 8:18

[GoogleCodeExporter]

Short update - for some reason, the Il-2 1946 doesn't run on my main sim 
machine - not even in windows; without even opening a window silently dies 
without single error message. Will try another computer when I get home...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 5 Mar 2013 at 8:14

[GoogleCodeExporter]

Hello Fernando,
I managed to install it at last (on windows, but good enough to test), and I 
can confirm your findings - 4.11.1 doesn't respond to the devicelink commands 
sent by ltr_pipe, while after downgrade to 4.10 it works...

At this point it looks more like a problem in the sim itself; anyway I'll try 
to talk directly to it and see if it is just this command, or the whole 
devicelink is hosed.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 6 Mar 2013 at 5:49

[GoogleCodeExporter]

Short update - the devicelink in 4.11.1 is active - tried to query some values 
and it does respond, so the communication problem (firewall, ports, wrong 
interface binding) are ruled out...

I'll try to see if I can set values, and also try if TrackIR itself will be 
able to controll the thing.
Kind regards,

Michal

Original comment by f.jo...@email.cz on 7 Mar 2013 at 5:56

• Changed state: Accepted

[GoogleCodeExporter]

Hello Fernando,
I managed to find the problem - they expanded the expected values from 3 to 6 
(full 6 DOF) without changing the docs...

Anyway the fix should be available in the new package, that should appear 
sometime during the weekend (or I can provide you with modified ltr_pipe).
Kind regards,

Michal

Original comment by f.jo...@email.cz on 7 Mar 2013 at 4:22

[GoogleCodeExporter]

Hi Michal,

As I told you, the new linuxtrack version does work with Il-2 v. 4.11.1. 
How come my TrackIR works only in 3 axis (pith, roll and yaw, as I commented 
before) if they expanaded to 6? What do you mean by "without changing the docs"?
Also, could you tell me what is new in the package you're preparing?
Thanks!

Original comment by fpin...@gmail.com on 9 Mar 2013 at 3:44

[GoogleCodeExporter]

Hello Fernando,
the new package is going to contain improved ltr_pipe, namely option 
--format-il2-6dof, that adds full 6DOF to il2 v4.11+; as for other highlights, 
there is improved pose processing to determine exact center of rotation, that 
will allow you to minimize unwanted head movement while looking around.

Device link just silently rejects "packets" that are invalid for some reason. 
That includes packets with wrong number of arguments. In 4.11, they started 
expect 6 values, while docs mention only 3...

You say the new linuxtrack does give you 3DOF - are you using the ltr_pipe or 
the linuxtrack/wine plugin?
Kind regards,

Michal

Original comment by f.jo...@email.cz on 9 Mar 2013 at 7:49

[GoogleCodeExporter]

I managed to find a problem, that I'd like to have solved before pushing the 
new package, so there will be a small delay... It shouldn't take more than few 
days to get it sorted out and tested. Anyway I'll report back when the package 
is ready.

If you'd like to get the new ltr_pipe to test it out, just let me know...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 11 Mar 2013 at 12:12

[GoogleCodeExporter]

Hey, Michal!

I'm using the linustrack/wine plugin now, so I can wait for you to release the 
package when you feel it's ready. I can't but be impressed at the good work 
you're doing  with this!

Regards.

Original comment by fpin...@gmail.com on 11 Mar 2013 at 10:44

[GoogleCodeExporter]

Hello Fernando,
I'm sorry it took me that long, but I wanted to check that everything is 
working and suddenly none of the test games would run... It took me few days to 
sort things out, but now everything works well.

As for Il-2 1946, both DeviceLink and wine plugin work, although the DeviceLink 
seem to have the translations overly sensitive (I'm going to investigate that). 
However, now the preferred way is to use the wine plugin where everything seems 
to work just fine. So unless you have a reason to stick with the DeviceLink, 
please use the wine plugin.

I'm going to close this issue now, if you experience any more problems, feel 
free to reopen this one or open a new issue.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 24 Mar 2013 at 8:52

• Changed state: Fixed

[GoogleCodeExporter]

Hi, Michal.

Sorry I didn't say anything before.
Maybe it's me and I'm doing something wrong... I'm getting the same three axis 
of movement that I got with previous version: pitch, roll and yaw. No x, y or z 
whatsoever... 6DoF does work in the Linuxtrack GUI, but not when in-game.
How can I see what version of Linuxtrack I'm running? I suspect maybe I didn't 
install last one properly.
Also, could you explain to me how to use the DeviceLink? I'd like to try and 
see if it works.
Regards.

Fernando

Original comment by fpin...@gmail.com on 1 Apr 2013 at 7:46

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello Fernando,
I'm using 4.11.01, but 4.11 should work just the same (6DOF). 

As for the linuxtrack-wine plugin, start the Tester app, put the number 1001 in 
the first textbox and click the start button; you should see movement in all 
six boxes - if not, there is a problem in Il-2 profile...

As for devicelink, I added this at the end of conf.ini:

[DeviceLink]
port=6543
IPS=127.0.0.1
host=127.0.0.1

and I start the ltr_pipe this way (note that you'd need to uninstall the 
linuxtrack-wine plugin to avoid clashes):

ltr_pipe --format-il2-6dof --output-net-udp

Kind regards,

Michal

Original comment by f.jo...@email.cz on 2 Apr 2013 at 2:59

[GoogleCodeExporter]

Hi again , Michal.

I must be doing something wrong here, because tester shows adequate movement in 
pitch, roll and yaw axis, while showing only erratic movement (althoguh some of 
it, at least) in x and y and almost none in z.
Same with DeviceLink (you are right, linuxtrack-wine plugin is more precise).
What puzzles me is that everything seems fine in ltr_gui and all 6DoF work 
perfectly there...?
What do you mean by a problem in Il2 profile? I'm also using v.4.11.01, by the 
way.
I'm quite confused.
Regards,

Fernando

Original comment by fpin...@gmail.com on 2 Apr 2013 at 7:00

[GoogleCodeExporter]

Hello Fernando,
to let me see the big picture, could you send me the package, that is created 
by pressing the "Package Logs..." button on the Misc. pane of ltr_gui?
It would package linuxtrack logs (it is just an archive, so you can check that 
it doesn't contain any sensitive info), that contain dump of linuxtrack 
preferences - there I can easily look to get all the informations and I can 
even try and reproduce the problem...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 3 Apr 2013 at 4:55

[GoogleCodeExporter]

Hi, Michal.

Mmm... No "Package Logs" button on the Misc. panel, but one labelled "View 
logfile". I just copied the output and pasted into a txt file, I hope that's 
what you wanted.
Regards.

Fernando.

Original comment by fpin...@gmail.com on 3 Apr 2013 at 6:11

Attachments:

• [Linuxtrack logfile.txt](https://storage.googleapis.com/google-code-attachments/linux-track/issue-34/comment-27/Linuxtrack logfile.txt)

[GoogleCodeExporter]

Hello Fernando,
it seems you use the beta1 package - could you install the beta2 and try that 
one instead? Also uninstall the wine plugin and install the new one - there 
were quite some fixes...
Other than that, the prefs seem ok...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 3 Apr 2013 at 6:50

[GoogleCodeExporter]

Hello, Michal.

After looking at it, I found this: I had both beta1 and beta2 packages 
installed, but I hadn't changed the link, so it was pointing to beta1 package. 
Nevertheless, I uninstalled both (just in case) and installed again beta2, and 
the wine plugin... Same results: everything works fine in ltr_gui, but not in 
the game. DeviceLink makes the system to exit the user session (?) and the wine 
plugin gives me pitch, roll and yaw, but no x,y or z; tester shows no 
consistent values.
I'm attaching the log file ltr_gui produced, in case you can find something 
there.
Thanks!

Fernando. 

Original comment by fpin...@gmail.com on 3 Apr 2013 at 9:05

Attachments:

• log.zip

[GoogleCodeExporter]

Hello Fernando,
the logs indicate you are using the new package. Right now, I'm not sure what 
causes the phenomenon you are seeing; I'll try to reproduce the problem and 
report back...

As for the devicelink closing your session, I'd suspect the problem in GFX 
driver - sometimes I got similar behavior on our notebook - should it happen 
again, look at /var/log/Xorg.log - most probably you'll see there a backtrace...

One more thought - how big are the peak values for x,y,z? It should go to 
values in order of thousands...

I'll report back with what I see.
Kind regards,

Michal

Original comment by f.jo...@email.cz on 3 Apr 2013 at 1:07

[GoogleCodeExporter]

Hello Fernando,
I managed to reproduce the problem...
The solution is easy - you need to recenter. This can be done easily - start 
the third application in the Linuxtrack directory under wine, called 
Controller.exe.so. A window pops up; if you didn't set keys to control it, just 
pres the "Redefine Pause key" button and then key of your choice and repeat the 
same for "Redefine Recenter key" - I use F11 and F12, but it should work with 
any other (single key, not Shifts, Ctrls, ...). Then minimize the window the 
(it goes to the tray as a little penguin) and allows you to control linuxtrack 
from within wine. Now start the tester and try 1001 as before - if the XYZ 
numbers doesn't behave, press the recenter key and see if it makes any 
difference - it did for me.

The problem was that the tracking should be recentered automatically when 
tracking starts; in fact, the tracking works just fine, the values were just 
limited and recentering makes then go to 0,0,0, where they work normally.
Please let me know if it works or you too...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 4 Apr 2013 at 3:01

[GoogleCodeExporter]

Hi, Michal.

Eureka! That was it. I used the Controller application and everything worked 
right away. All 6DoF are OK now. Plus, being able to pause tracking and 
recenter it every now and then is kind of convenient.
One question: in the Tester application, x and y axes have four windows (z axis 
has only three) Why is that? Apart from the first window of every axis, I only 
get something in the last one of the y one.
Again, thanks for your help.
Regards.

Fernando.

Original comment by fpin...@gmail.com on 4 Apr 2013 at 10:01

[GoogleCodeExporter]

Hello Fernando,
I'm glad it works for you now...

The tester application was used mainly for proving my assumptions when I was 
reverse engineering the protocol; the only windows that are supposed to contain 
meaningfull values are the first 6 (rotations and translations) and last two if 
I'm not mistaken - there is a status and frame counter... The rest is being 
either zero or when "enhanced" (read encrypted) interface is being used, they 
are filled with random data.

I'm going to close the issue now, if you encounter any other problems, feel 
free to reopen it or open a new one...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 4 Apr 2013 at 10:50

• Changed state: Verified

[GoogleCodeExporter]

Michal:

OK.
Yet another time, thank you for a good work and a ton of patience.

Fernando.

Original comment by fpin...@gmail.com on 5 Apr 2013 at 7:55