Closed GoogleCodeExporter closed 9 years ago
Hello,
thank you for the report; I've tested it before the release and it did work, so
I'm a little bit puzzled. Could you try and take a look at the linuxtrack log
(fourth pane) and tell me if there is any suspicious message (like some missing
library or anything alike)?
I'll try and check the thing in the evening to see if I didn't miss anything...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 13 Jul 2013 at 1:10
Just a quick update - did some test and no matter what I do, I can't trigger
this message even when I remove the wine completely. I'll investigate further
to see what is going on.
Anyway, there is one more thing to check - when you go to the contents of the
package, directory MacOS, you should see there the actual ltr_gui executable;
open the terminal (Application/Utilities) and drag'n'drop the ltr_gui there
(should fill in the its path) and press enter - the ltr_gui should start. Now
look in the terminal - there is a line like 'Launching wine command:
'/Volumes/.../ltr_gui.app/Contents/MacOS/../wine/bin/wine --version '.
Now close the ltr_gui and run the whole command (everything inside the
apostrophes) in the terminal - what output do you get?
Thank you for your help,
Michal
Original comment by f.jo...@email.cz
on 13 Jul 2013 at 2:26
[deleted comment]
[deleted comment]
Hello, thanks for the quick reply.
Unfortunately there are no error messages in the log (I've attached a copy of
it here as well)..
I'm thinking that it may be due to leftover files from a previous version of
linuxtrack that I installed a few months ago. Is there something that I can do
to remove them?
Original comment by cbcf...@gmail.com
on 13 Jul 2013 at 2:43
Attachments:
Ok... I tried launching ltr_gui from Terminal. Drag and drop didn't work for me
so I used "open -a ltr_gui" instead.
Unfortunately I didn't get the line "Launching wine command etc etc" in
Terminal.
Original comment by cbcf...@gmail.com
on 13 Jul 2013 at 2:43
[deleted comment]
Hi,
can you try and put ltr_gui on your desktop, or somewhere where there aren't
spaces in the path? I think I know what the problem is, I'll try and reproduce
it.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 13 Jul 2013 at 4:57
Yes, you are absolutely right, but still I'm having troubles...
At first I had the "Wine not working, you'll not be able to install NP firmware
and Wine plugin!" at startup, but now I don't because the spaces were really
the issue here.
The problem now is that wine still doesn't start de installation of the
firmware after it was downloaded. I tried downloading it directly from NP and
running it through wine (outside of ltr_gui) and it installed perfectly...
I have even tried using the file I downloaded (in a directory also without
spaces) by using the "Browse" option and still wine does not start the
installer...
Original comment by jotama...@netcabo.pt
on 13 Jul 2013 at 5:23
It jams right here and nothing else happens. No pop-up, no installation in the
background, no wine app running...
BTW, this is an iMac without any previous installments of linuxtrack. I just
run FSX on Windows via Bootcamp and now I wanted to use X-Plane on Mac with
Track IR as well...
Thank you for your support.
Original comment by jotama...@netcabo.pt
on 13 Jul 2013 at 5:44
Attachments:
It seems that the problem is still present for some reason... I just found out,
that the message is probably subject of the race condition and does not have
appear at all, when timing is right (well, wrong really).
But still it doesn't explain what is going on in there... If I may, I'd like to
ask you this:
you said you downloaded the NP driver, so copy it to some directory, then open
a terminal, switch to the directory where the driver is and run the following
commands:
mkdir prefix; WINEPREFIX=prefix
/Users/JONESYdj/Desktop/Linuxtrack/ltr_gui.app/Contents/wine/bin/wine
TrackIR_5.2.2.Final.exe
Please adjust the paths, if necessary (there might be a typo); this should
mimic the process ltr_gui does... I'd be interested in any error messages, that
might pop up (assuming the process fails) - especially missing libraries and
alike...
Thank you very much for your help!
Kind regards,
Michal
PS. One more thing, if you run ltr_gui from terminal (directly, using that
drag'n'drop) and press the download button in the firmware dialog, it prints
the command issued - could you paste it here please?
Original comment by f.jo...@email.cz
on 13 Jul 2013 at 7:35
Thank you for the reply. For the first part, there seems to be an error by
Wine. Nevermind I'm using another version because that's the one I prefer
(never liked the upgrade to version 5 of TrackIR). So here goes:
jonesy-imac:npdriver JONESYdj$ ls
TrackIR_4.2.039.Final.exe
jonesy-imac:npdriver JONESYdj$ mkdir prefix; WINEPREFIX=prefix
/Users/JONESYdj/Desktop/Linuxtrack/ltr_gui.app/Contents/wine/bin/wine
TrackIR_4.2.039.Final.exe
wine: invalid directory prefix in WINEPREFIX: not an absolute path
Then I used the absolute path for the prefix and this is what I got (I would
say that is the problem). Is this what it was supposed to return?
jonesy-imac:npdriver JONESYdj$ ls
TrackIR_4.2.039.Final.exe prefix
jonesy-imac:npdriver JONESYdj$ mkdir prefix;
WINEPREFIX=/Users/JONESYdj/Desktop/NPdriver/prefix
/Users/JONESYdj/Desktop/Linuxtrack/ltr_gui.app/Contents/wine/bin/wine
mkdir: prefix: File exists
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
So far so good, but...
I ran ltr_gui from the terminal and there were no errors returned. Just
complete inactivity after I click OK on the warning that the NP Installer will
pop-up. Terminal window was like this:
jonesy-imac:~ JONESYdj$
/Users/JONESYdj/Desktop/Linuxtrack/ltr_gui.app/Contents/MacOS/ltr_gui
Going to create lock '/Users/JONESYdj/.config/linuxtrack/ltr_server.lock' => 19!
Lock 19 success!
Passing the lock to protect fifo (pid 5637)!
Changed index to Default
Profile Default found, setting it!!!
Launching wine command:
'/Users/JONESYdj/Desktop/Linuxtrack/ltr_gui.app/Contents/MacOS/../wine/bin/wine
--version '
Found device 3
Object read!
Type: 3
Launching wine command:
'/Users/JONESYdj/Desktop/Linuxtrack/ltr_gui.app/Contents/MacOS/../wine/bin/wine
/Users/JONESYdj/Desktop/NPdriver/TrackIR_4.2.039.Final.exe'
Any suggestions?
Original comment by jotama...@netcabo.pt
on 13 Jul 2013 at 11:05
Hello,
I did some changes, hopefully it will help - the new archive is located here:
http://linuxtrack.eu/test/linuxtrack-0.99.3.1.dmg
When testing, I was able to install the firmware just fine, even from path with
spaces.
Please let me know if it helped.
Kind regards,
Michal
PS. 2:30am here, I'm heading to bed; unfortunately I won't be able to do more
till the evening; just so you know...
Original comment by f.jo...@email.cz
on 14 Jul 2013 at 12:36
Ok, thank you very much. Yesterday I've downloaded the file and very quickly
tried it and I think it stalled pretty much on the same spot. But it was all
very quick because it was late. Today at midnight (1am there) I'll try it again
and will report the results.
Thanks again for the support. I desperatly need this working (I'm so used to
TrackIR that I can't play any flight simulator without it).
Original comment by jotama...@netcabo.pt
on 14 Jul 2013 at 4:30
I do understand, although I didn't fly pretty much at all several last years,
in the rare occasions when I did, flying without headtracking was like flying
with my left hand - possible, but uncomfortable...
In case it doesn't work, I'd ask you to do this: Open the terminal and go
inside the ltr_gui.app/Contents/wine/bin directory. Then copy the
TrackIR_5.2.2.Final.exe there and run the following command:
./wine TrackIR_5.2.2.Final.exe
Does any interesting error message pop up? Like a segfault or a missing library
or so?
Thank you,
Michal
Original comment by f.jo...@email.cz
on 14 Jul 2013 at 7:34
Hi,
you can disregard the second part of the previous message - please download new
package here:
http://linuxtrack.eu/test/linuxtrack-0.99.3.2.dmg
It should put the error messages to the log, so when you try to extract the
firmware, and it fails, please open the log (fourth pane) and either attach it
here or paste the error message. Hopefully it will shed some light on what is
going wrong there...
Thank you,
Michal
Original comment by f.jo...@email.cz
on 14 Jul 2013 at 9:55
Wow, thank you so much for your effort. Here goes - this time I tried to
download the latest firmware so that we are sure we are on the same page
(although this shouldn't be the source of the problem). This is the juicy bit
of the log (the program now returns an error message instead of being just
idle, so nevertheless it is an improvement):
"Going to download "
"http://media.naturalpoint.com/software/TrackIR_5.2.2.Final.exe"
QPixmap::scaled: Pixmap is a null pixmap
"/var/folders/py/pyG6ZVvkET02ltOcMhaTRU+++TI/-Tmp-/winekUsebb"
Launching wine command:
'"/Users/JONESYdj/Desktop/Linuxtrack09932/ltr_gui.app/Contents/MacOS/../wine/bin
/wine"
"/var/folders/py/pyG6ZVvkET02ltOcMhaTRU+++TI/-Tmp-/winekUsebb/TrackIR_5.2.2.Fina
l.exe"'
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
err:appbar:initialize_appbar Could not create appbar message window
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
err:systray:initialize_systray Could not create tray window
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
err:rundll32:wWinMain Unable to load L"setupapi"
wine: configuration in
'/var/folders/py/pyG6ZVvkET02ltOcMhaTRU+++TI/-Tmp-/winekUsebb' has been updated.
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
Original comment by jotama...@netcabo.pt
on 15 Jul 2013 at 12:28
Wow, thank you so much for your effort. Here goes - this time I tried to
download the latest firmware so that we are sure we are on the same page
(although this shouldn't be the source of the problem). This is the juicy bit
of the log (the program now returns an error message instead of being just
idle, so nevertheless it is an improvement):
"Going to download "
"http://media.naturalpoint.com/software/TrackIR_5.2.2.Final.exe"
QPixmap::scaled: Pixmap is a null pixmap
"/var/folders/py/pyG6ZVvkET02ltOcMhaTRU+++TI/-Tmp-/winekUsebb"
Launching wine command:
'"/Users/JONESYdj/Desktop/Linuxtrack09932/ltr_gui.app/Contents/MacOS/../wine/bin
/wine"
"/var/folders/py/pyG6ZVvkET02ltOcMhaTRU+++TI/-Tmp-/winekUsebb/TrackIR_5.2.2.Fina
l.exe"'
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
err:appbar:initialize_appbar Could not create appbar message window
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
err:systray:initialize_systray Could not create tray window
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
err:rundll32:wWinMain Unable to load L"setupapi"
wine: configuration in
'/var/folders/py/pyG6ZVvkET02ltOcMhaTRU+++TI/-Tmp-/winekUsebb' has been updated.
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Application tried to create a window, but no driver could be loaded.
The X11 driver is missing. Check your build!
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
Original comment by jotama...@netcabo.pt
on 15 Jul 2013 at 12:32
Maybe this is relevant (I wasn't the one starting the thread so I never
revealed these details):
iMac 27" running Mac OS X Snow Leopard 10.6.8
3.2 GHz Intel Core i3
4 Gb 1333 MHz DDR3
Original comment by jotama...@netcabo.pt
on 15 Jul 2013 at 12:38
I think my transcription of the log keeps being blocked because of the presence
of many URL's. Here goes the .log file...
Original comment by jotama...@netcabo.pt
on 15 Jul 2013 at 12:40
Attachments:
Hi,
so there goes another theory - I thought that it was tied to the MacOSx new
update 10.8.4 (I didn't installed it yet)... Strange thing is, that my
development machine does have 10.6.8 installed too (in fact it is used to do
the builds in order to have linuxtrack usable for 10.6+), but the wine does
work just fine.
What more, the messages in the log are similar to what I see when I install the
thing outside of ltr_gui. So I'll do the following: first of all, I'll add a
possibility to override wine version (probably through setting some env.
variable), and just in case, I'll let the analysis commence even when the
install doesn't report zero status.
Leaving for work in a few minutes, but the new build should be ready for you in
the evening.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 15 Jul 2013 at 2:48
I think I've solved the problem. I had the same problems as jotama, but I
realised from the logs that it's because the version of Wine packaged with
ltr_gui doesn't know where to find FreeType and X11.
To resolve this, I essentially did the following (Note: for me, I've a separate
instance of Wine that I installed via Macports some time ago, and it's located
in /opt/local/lib/ on my machine):
1. Place the following aliases in /usr/bin:
a. libfreetype.6.dylib
b. libfreetype.a
c. libfreetype.dylib
d. libfreetype.la
(I know that I could be aliasing more files than I need to, but just to be
cautious, I did the whole works :p)
2. Placed a copy of winex11.drv.so within ltr_gui.app/contents/wine as the log
said that Wine couldn't find the X11 driver.
Bottomline: I'm no expert at this, but Michal,
a. I suspect your dev machine already has Wine installed in another folder
outside of ltr_gui.app/Contents/etc etc, and it's referencing critical files
that are *outside* of this folder.
b. I think you forgot to include the X11 driver inside the wine folder within
the package (ie ltr_gui.app/contents/wine/)
Original comment by cbcf...@gmail.com
on 15 Jul 2013 at 2:45
I spoke too soon. To add on to my previous comment:
msiexec crashes at the first screen of the TR installer. I'm not sure why. I
tried running the installer using my own instance of Wine and it worked
perfectly.
Original comment by cbcf...@gmail.com
on 15 Jul 2013 at 4:03
Hello,
as for the wine that is built-in to the ltr_gui, it is sort of minimal thing -
no X, no freetype, only necessary things (it is ~100MB anyway); funny thing is,
that the installer still does its job - well at least on my machine it does...
Anyway, I did two changes to help you overcome that problem - first of all, if
you have the NP soft already unpacked somewhere, just use the "Extract from
unpacked" button - point it to the unpacked TrackIR directory (see help for
details). Also you can add the wine you have already installed (the one
working) to PATH environment variable and ltr_gui will pick that one instead.
So hopefully this will get you going...
http://linuxtrack.eu/test/linuxtrack-0.99.3.3.dmg
However, I'd still ask you to help me to pinpoint the problem - try the
nonworking wine and send me the logfile - all the error messages should be
there... I think, that it is possible that the wine you have installed already
might be somewhat interfering with the one in the ltr_gui - sort of dll hell
thing...
Thank you for your patience and help,
Michal
Original comment by f.jo...@email.cz
on 15 Jul 2013 at 10:02
I will try it soon, but just so you know, I had never installed wine before on
this computer and have only installed it after this problem started. So it is
not interference...
I also had no difficulties running TrackIR installer from the wine I had
installed for that purpose. But I have no clue of what I am doing here and am
unable to understand the environment wine creates and it's relation to Mac OS.
But nevermind that, I'm not asking for a wine tutorial here...
Will let you know how this last version goes, but I don't think I understood
this part:
"Also you can add the wine you have already installed (the one working) to PATH
environment variable and ltr_gui will pick that one instead."
Thank you
Original comment by jotama...@netcabo.pt
on 16 Jul 2013 at 8:26
So there goes another theory... I'm just trying to come up with some common
denominator, some place to start from. Funnily enough, on my machine, when I
compile the wine, it does work on both 10.6 and 10.8; however when I compile it
on 10.8, some part of it crashes in a very strange way - the wine and
wineserver is running, but the prefix is not initialized correctly...
To your question, I thought, that when you have a working wine installation,
then when you add path to it to your PATH environment variable, it will be used
instead of the built in one. For example, lets say you installed a wine to
/opt/wine and it does work well; so you add the following statement to your
.profile or .bashrc :
export PATH=$PATH:/opt/linuxtrack/bin
This way, when you run a wine in a terminal, it will invoke the one you
installed. After the last update, ltr_gui honors this, so if you have a wine
setup this way, it will be used instead of the built-in one; for others, it
will use the one built-in as before.
If I may, I'd like to ask you to perform the following test:
1) Try to download the driver from net (if possible) or use the "Extract from
installer" button and point it to the installer you downloaded. If it doesn't
work, I'd like to ask you to attach the log here, so I can take a look where it
went wrong.
2) If that doesn't help just use the "Extract from unpacked" and point it to
the driver package you unpacked using the external wine; however, if you didn't
set the wineprefix when you installed it, it will be in ~/.wine - to see it,
use the terminal with command 'mv ~/.wine wine' to change te name, so it si not
hidden anymore...
Thank you for your help,
Michal
Original comment by f.jo...@email.cz
on 16 Jul 2013 at 8:52
Hello guys, there is a new version (0.99.4) available in the downloads section,
it contains all the changes as 0.99.3.3 so please use that one instead...
Kind regards,
Michal
PS. If you both (if possible) could send me the log of wine failing, I'd be
very gratefull... I'd like to know what the culprit is and if it is the same
problem you both experience.
Original comment by f.jo...@email.cz
on 17 Jul 2013 at 5:14
I just tried to reproduce the problem on the freshly installed MacOSX 10.8 -
"unfortunately" it does work as expected... The more I'm interested the logs
from you guys - hopefully they will allow me to find out what is going on...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 18 Jul 2013 at 12:11
Hello Michal,
I'm not exactly sure what changed in 0.99.4... but it works perfectly now :D
I've tested it with both options (ie extract from installer and extract from
unpacked), and both are ok!
X11 doesn't exit after the installer is done, but I guess that's ok since I can
manually quit the app. I'm going to keep testing it for a few more times just
to be sure. Thanks for your help!
Original comment by cbcf...@gmail.com
on 18 Jul 2013 at 2:36
Attachments:
Hello,
I'm glad to hear that it does work finally...
The fact, that you got X11 started, suggests that this is your wine being
invoked, not the built-in one (you have it in your PATH). The fact, that X11
stays up is I think normal - at least I do see the same behavior.
Thank you for the report!
Michal
Original comment by f.jo...@email.cz
on 18 Jul 2013 at 7:12
Well, I'm still stuck. Tried downloading and tried from installer and same
error. Worst of all, I'm still unable to use TrackIr on X-Plane because there
are no alternatives :(
Here goes the log:
Original comment by jotama...@netcabo.pt
on 19 Jul 2013 at 3:43
Attachments:
This is really strange - I just tried on cleanly installed SnowLeopard, as well
as on the Mountain Lion (clean install too) and both of them work without any
problems (I don't even get the X and freetype related messages).
There is still one possibility left though - I'd like to see, if there isn't a
sort of dll-hell like problem; hopefully I'll have the package ready for you in
the next 24 hours...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 20 Jul 2013 at 1:25
I mainly use this computer for everyday uses and audio production tools (and
now for XPlane as well). The only time I've seen a X11 window was with the app
Gimp, and I didn't like it and erased it. I don't know if it may have altered
the state of the software.
Let's hope the next one hits the spot.
Original comment by jotama...@netcabo.pt
on 20 Jul 2013 at 8:22
I tried set the wine in such a way, that it should ensure that no external
libraries are used (other than few system ones)... Also the logging is much
more extensive, so lets hope this one will uncover the problem... If it still
doesn't work, please send me the log, maybe there will be something
interesting...
The new package is here:
http://linuxtrack.eu/test/linuxtrack-0.99.4.1.dmg
Kind regards,
Michal
PS. BTW, have you checked your email? My message might have ended up in spam...
Original comment by f.jo...@email.cz
on 20 Jul 2013 at 8:21
No I haven't, sorry, this is my spam e-mail (the one I use for everything but
professional purposes)... But I already have, thank you.
I will only use that alternative in last resort as I'm afraid it will influence
the troubleshooting of this version.
Here comes the log (it didn't work):
Original comment by jotama...@netcabo.pt
on 21 Jul 2013 at 9:40
Attachments:
Actually you can use it, just instead of install firmware, you'd do reinstall...
Will take a look at the log and report back.
Thank you for your dedication,
Michal
Original comment by f.jo...@email.cz
on 21 Jul 2013 at 10:05
Hi,
going through the logs, I noticed one strange thing - your log suggests that
things go south when a default printer driver (wineps.drv) is loaded (and then
unloaded for some reason); do you, by any chance, have a printer connected to
your Mac. The thing is, that on my machine it doesn't even try to load that
thing...
Anyway, here is the newest package - I'm affraid that it won't fix the problem
yet (although I removed the cups support, just in case), but it will produce
even more detailed log, that will hopefully provide enough info to see where
exactly the problem is.
http://linuxtrack.eu/test/linuxtrack-0.99.4.2.dmg
Thank you for your patience,
Michal
Original comment by f.jo...@email.cz
on 23 Jul 2013 at 5:07
Hi,
I *may* have a solution - it seems that when the thing starts, it enumerates
available printers and when it does find one, it loads the wineps.drv, which in
turn tries to load font metrics and create a default font.
My theory is, that for some reason one of the operations fails, leading to
unloading of the wineps.drv and it causes the whole thing to fail. When I get
back to the computer, I'll try to reproduce the problem and hopefully will be
able to provide a fix that should solve your problem...
Will keep you posted,
Michal
Original comment by f.jo...@email.cz
on 23 Jul 2013 at 10:00
So, I managed to reproduce the problem - the printer plugged-in does it.
I just uploaded a fixed package here:
http://linuxtrack.eu/test/linuxtrack-0.99.4.3.dmg
Works for me, so hopefully it is going to work for you too - if you confirm it
works for you too, I'll upload new official package.
Thank you for your help,
Michal
Original comment by f.jo...@email.cz
on 23 Jul 2013 at 10:39
Greetings! I believe it has worked this time :) I'm not 100% sure because I had
already installed the firmware the way you told me through e-mail so nothing
has changed in the ltr_gui. The software behavior was as follows:
- Downloaded the latest TrackIR firmware;
- Analyzed and extracted the files;
- The "Extractor" window closed after saying the installation was successful
and nothing changed;
- I believe everything is still working (will test right now).
Even though I browsed through the log and found some errors that I leave for
you to analyze as they may not be of importance:
0028:err:wincodecs:JpegDecoder_CreateInstance Trying to load JPEG picture, but
JPEG support is not compiled in.
0028:fixme:ole:CoCreateInstance no instance created for interface
{9edde9e7-8dee-47ea-99df-e6faf2ed44bf} of class
{9456a480-e88b-43ea-9e73-0b2d9b71b1ca}, hres is 0x80004005
0028:err:ole:OleLoadPicture IPersistStream_Load failed
0028:err:msi:msi_load_picture failed to load picture
0028:err:msi:msi_dialog_bitmap_control Failed to load bitmap L"NewBinary5"
0028:err:msi:msi_dialog_run_message_loop Failed to create dialog
L"SetupCompleteSuccess"
Nice going Michal :) And thank you for everything! This ltr_gui is a far
superior tool for configuring the curves of sensitivity of the head movements
and translation than the original NP software, lol. At least I like it much
better than the original!
Thanks!
Jonesy
Original comment by jotama...@netcabo.pt
on 24 Jul 2013 at 12:58
Attachments:
Hello,
I'm glad it finally works for you and thank you for those kind words...
Those messages are OK, as long as the thing unpacks correctly and extracts what
is needed.
I also took the liberty to introduce you to the project "Hall of Fame", because
you really helped me a lot.
Thank you,
Michal
PS. I'll close this issue as soon as I have the new version up.
Original comment by f.jo...@email.cz
on 24 Jul 2013 at 8:37
Thank you :) I did it because this tool is fundamental for any flight sim
enthusiast on Mac or Linux. And you even have support from Laminar Research (at
least they mention Linuxtrack in the in-game menus).
Kudos
Jonesy
Original comment by jotama...@netcabo.pt
on 25 Jul 2013 at 4:20
Hello,
the newest version (0.99.5) should be ok; should you experience any more
problems, feel free to reopen it or file a new one.
Thank you for your help hunting this bug down,
Michal
PS. The menu you mention, comes from my plugin, Laminar has nothing to do with
that...
Original comment by f.jo...@email.cz
on 29 Jul 2013 at 8:21
Original issue reported on code.google.com by
cbcf...@gmail.com
on 13 Jul 2013 at 7:03