28.01.2010, 15:55
Everything up there (great bug-reporting, Spider, just what I needed to know) suggested that nothing was wrong. Instead you were both right, it was something I had not foreseen.
On a note, the command promt window showing "not sock" is normal - the throttle program and it's netcat component does not actually make a 'connection' - UDP does not work like that. Instead it justs 'aims' it's guns towards a UDP port target, and then only sends. So no matter what it will say that (as long as the IP adress exists).
I can confirm what you both claim - if having nothing started, then starting the throttle program FIRST; it will not work. But if starting a mission, then the throttle program, it works fine. I will test a bit, but I think mainly this can be solved comfortably for users.
It is currently set up so that:
1. The Throttle 3.0 launcher.exe file only does one thing, it runs a command with the windows console to launch the actual throttle program (MikkOwl_Magic.exe), and to 'pipe' that into "netcat", with the correct IP address and port for netcat to be able to connect successfully to IL-2's device link.
2. After that, the launcher exits and has no more function. The user supposedly is in the game enjoying all the functions. When done, can click "ALT-E" and the MikkOwl_Magic throttle program will first shut down the console window (that contains 'netcat') and then after 2 seconds, itself too.
I will make the following adjustments:
1. The launcher, when started, does not do anything. It stays in memory and waits.
2. The user loads IL-2 and enters a mission.
3. When the user clicks a hotkey (like ALT-G as in "go" for example), the launcher performs the action it originally did, launching the connection and throttle program, and then quits.
4. User enjoys awesome free program to get all their hardware working without problems
I'm sure that will solve it.
I'll fix it tonight and update documentation.
And if you really enjoy this software and think it enabled make fun things, consider donating whatever little sum you think it was worth to me on paypal - "mikko.artist@bredband.net". I'm unemployed and in a bad situation in general with health problems and other things. I took the development of this program very far beyond what I needed just for myself, because I thought it would be helpful for others.
And by the way regarding names, I also use this name on hyperlobby - "MikkOwl". I only fly on a certain server sometimes, usually during the night and early morning in Europe - "War-Clouds". In there, only one thing is certain, I'll be flying twin engined aircraft, either Bf 110, Ju-88 (rarely) and I think I want to move over to the allies to try the P-38. I love twin engined, but I also want to be able to fight aircraft, and since the Me-210 is messed up and the Me-410 is not available nor correctly modeled, the P-38 seems to be the only option that isn't extremely terrible.
On a note, the command promt window showing "not sock" is normal - the throttle program and it's netcat component does not actually make a 'connection' - UDP does not work like that. Instead it justs 'aims' it's guns towards a UDP port target, and then only sends. So no matter what it will say that (as long as the IP adress exists).
I can confirm what you both claim - if having nothing started, then starting the throttle program FIRST; it will not work. But if starting a mission, then the throttle program, it works fine. I will test a bit, but I think mainly this can be solved comfortably for users.
It is currently set up so that:
1. The Throttle 3.0 launcher.exe file only does one thing, it runs a command with the windows console to launch the actual throttle program (MikkOwl_Magic.exe), and to 'pipe' that into "netcat", with the correct IP address and port for netcat to be able to connect successfully to IL-2's device link.
2. After that, the launcher exits and has no more function. The user supposedly is in the game enjoying all the functions. When done, can click "ALT-E" and the MikkOwl_Magic throttle program will first shut down the console window (that contains 'netcat') and then after 2 seconds, itself too.
I will make the following adjustments:
1. The launcher, when started, does not do anything. It stays in memory and waits.
2. The user loads IL-2 and enters a mission.
3. When the user clicks a hotkey (like ALT-G as in "go" for example), the launcher performs the action it originally did, launching the connection and throttle program, and then quits.
4. User enjoys awesome free program to get all their hardware working without problems
I'm sure that will solve it.
I'll fix it tonight and update documentation.
And if you really enjoy this software and think it enabled make fun things, consider donating whatever little sum you think it was worth to me on paypal - "mikko.artist@bredband.net". I'm unemployed and in a bad situation in general with health problems and other things. I took the development of this program very far beyond what I needed just for myself, because I thought it would be helpful for others.
And by the way regarding names, I also use this name on hyperlobby - "MikkOwl". I only fly on a certain server sometimes, usually during the night and early morning in Europe - "War-Clouds". In there, only one thing is certain, I'll be flying twin engined aircraft, either Bf 110, Ju-88 (rarely) and I think I want to move over to the allies to try the P-38. I love twin engined, but I also want to be able to fight aircraft, and since the Me-210 is messed up and the Me-410 is not available nor correctly modeled, the P-38 seems to be the only option that isn't extremely terrible.