sebbomann

I deserve it, because I'm a longtime Thrustmaster customer. :)

Did the first in line move in fear after that? :D

I don't know anything about the real reasons for this bug, neither do you. What you are doing is something like a dirty hack to get things working for you. But this is in most cases not the best solution. There seem to be bigger problems regarding taxiing and radio, which can not be solved by two clicks in the mission editor. Otherwise the developers would have done this, don't you think. ;) Nevertheless don't get me wrong, I also want to fly this mission in a proper way. But I just want to propagate a little understanding for the developers. :)

Actually this should have been fixed in an update 8 weeks ago. But this is how development goes... priorities are always shifting. ;)

Will do that. Thanks for the information. :thumbup:

Was my suspicion too, because it was stated, that this was fixed. But cannot confirm, because I just bought the campaign this weekend...

exactly that.

There happens to be a little traffic jam on start of mission 03. So i cannot finish this mission as planned... Trackfile

same here...

Glad to hear that. :)

If you have specific questions, just ask. We will try to help. :thumbup:

I don't know. Look's like it should work. Buy them, try them and tell us. ;)

I want a Hawk

Yes, it will be available.

These Pedals are the best Pedals i've ever owned. i use these for like a month, and i will never give them back. :smilewink: The precision, smoothness, lack of stickyness and all the things you can adjust are simply amazing. And to mention the best thing: wallspacers!!! I mean fsck yeah, why did no vendor ever think of that? How was I living without them? :thumbup: Yes, they are a little costy, but I really enjoy these pedals!

Really good explanation! :thumbup:

http://forums.eagle.ru/showpost.php?p=1196165&postcount=42 Maybe this is possible?

Yeah, but sadly displays in dcs can not be exported. I tried to build a similar app like this a while ago and ran into the same issue.

Given that the market for hardcore simulations like DCS is a niche market, I see the benefits of crowdfunding for getting the money to develop on a module. Developing a module seems to be much more work than I expected. They have my 50$.

This is killing my productivity. :smilewink:

Hi, I've tried to export some data from the simulation via a TCP socket: function LuaExportStart() package.path = package.path..";.\\LuaSocket\\?.lua" package.cpath = package.cpath..";.\\LuaSocket\\?.dll" socket = require("socket") host = host or "127.0.0.1" port = port or 8080 [color="Orange"]c = socket.try(socket.connect(host, port))[/color] c:setoption("tcp-nodelay",true) end The script crashes on creation of the socket: # -------------- 20130404-142657 -------------- # C0000005 ACCESS_VIOLATION at F50815C5 00:00000000 00000000 00000000 0000:00000000 F50815C5 001EE610 0000:00000000 ?pop@Config@Lua@@QEAA_NPEAVVec4f@osg@@@Z()+245 FA566F97 001EE650 0000:00000000 lua_yield()+507 FA567029 001EE680 0000:00000000 lua_yield()+599 FA565C22 001EE6B0 0000:00000000 lua_setlocal()+D92 FA5625E9 001EE6E0 0000:00000000 lua_error()+9 F74746CE 001EE710 0000:00000000 luaopen_socket_core()+35CE FA566F97 001EE750 0000:00000000 lua_yield()+507 FA574A86 001EE910 0000:00000000 luaS_newlstr()+44C6 FA567038 001EE940 0000:00000000 lua_yield()+5A8 FA5661BF 001EEAC0 0000:00000000 lua_getinfo()+39F FA56721E 001EEB00 0000:00000000 lua_resume()+10E FA562290 001EEB50 0000:00000000 lua_pcall()+60 F5081B74 001EEBA0 0000:00000000 ?call_func@Config@Lua@@AEAA_NPEBDPEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@HH@Z()+D4 402F8882 001EED40 0000:00000000 402CED2E 001EEE70 0000:00000000 402D1156 001EF160 0000:00000000 402C9AD2 001EF3C0 0000:00000000 F50A536A 001EF3F0 0000:00000000 ?sendOutputSymbol_@FSM@Common@@AEAAXI@Z()+2A F50A6025 001EF420 0000:00000000 ?enterToState_@FSM@Common@@AEAAXI@Z()+B5 F50A72F1 001EF450 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+1B1 F50A73DE 001EF4A0 0000:00000000 ?checkSymbolsQueue@FSM@Common@@QEAAXXZ()+AE 402CD920 001EF500 0000:00000000 402E6DC4 001EF530 0000:00000000 402E6C9B 001EF560 0000:00000000 40376BC8 001EF5D0 0000:00000000 40378018 001EFAC0 0000:00000000 4037AB9F 001EFB70 0000:00000000 7725652D 001EFBA0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7738C521 001EFBF0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 Any ideas at what I am doing wrong?

good luck. ;)

The specs are not really the same. Your Honeywell-sensor operates from 4.5V to 10.5V. And the specs on the A1302 are a little different (4.5V - 6V). This does not say much, but this difference could be the cause, why your sensor is not responding. I asked a colleague about that, who is very good in electronics, and he said, that if your part works at your given voltage level, even if it is not in the range specified in the datasheet, you're fine. So there are two things which remain to you: raise your supply voltage whith an external power supply (not cool, higher supply voltage means higher output voltage and you might kill your throttle) use the a1302 hope that helps...

No problem. Ask here or PM me, if you need any help. :)

should be exactly what you want.