ClearDark

The gauges are vector-drawn and are saved in binary format in the DLL. So you won't see any images :) However, you should see the gauges on your screen (not functional but still drawn just like in the picture on the main post). Can you confirm that when you run HawgTouch, the Gauge Pack status indication says "Loaded (1.x)" Like in the picture below: If you don't see that line then something else might be going on.

In my pre release testing, i tried 10.0.0.1 and it was bound successfully...Odd :o Anyways! Glad you got it working. Thanks to all that are helping!!!

You arent getting on my nerves :). Im throwing ideas in the air to try and find the issue :) You are getting an exception on binding which means the socket cannot initialize on the IP address for some reason. Im going to get some more info on the subject n you try to think if there might be anything on your end that might cause this! We can surely work it out

Press the start button. Type cmd and hit enter. In the console window type ipconfig and hit enter. Make sure the ip located in the output of ipconfig matches your HT config. You are surely providing the wrong IP addy

Try the supplied config in this post. You probably dropped quotes or something small :) Try following Nu-NRG excellent writeup here! I will edit it and hang it all in the main post once we get remote machines running this setup stable! Config.zip

That means that the IP you typed in the config is invalid and cannot be bound. What was the IP you used? Did you make sure you restarted the application after saving the config file?

You need to see gauges regardless of anything running. If you don't see any, first make sure that you see in HawgToauch main window that a Gauge Pack is loaded (version 1.0 or 1.1). If no pack is loaded download it from the main post and put the dll in the same folder of HT and restart the application. If a pack is loaded and you still don't see a thing, make sure you have installed the latest .NET 4 release. I linked it in the main post as well. If after all that still nothing shows, let me know. We'll take it further to figure it out.

Yup! Thats exactly how you set it up!

All packages of HawgTouch have been updated in the main post. The application now comes with a .config file which lets you directly specify the IP address you wish HawgTouch to listen on. The default configuration is 127.0.0.1 You have to restart the application for the changes to take effect! Enjoy :)

Thanks for pointing that out Yargon! To address this I will add a simple config which lets you decide on which IP to bind HT to. Expect a released hotfix within a couple of hours :)

Here you go! The problem was you used capital letters for keybindings instead of lowercases. I should write that down in the main post so people won't get too frustrated. Let me know how this works out :) Showcase-storemaster.zip

Interesting... The only thing I can think of is that you are using the MFCDS+UFC template provided in ShowcaseProfile.xml and you probably edited keys on one of the UFC controls in the first tab of the same profile (the Scale Test tab). Post up your profile XML so I can inspect it and fix it if needed :)

Make sure to run HawgTouch as administrator :)

Thanks for the warm feedback automag. Posts like these give me the biggest drive to continue bring you guys the best I can. Plus, as a coder, I love seeing how so many people enjoy this piece of software which was conjured up in a month or so. It has really come a long way and there is plenty more to go :)

sobe, Could you take a screenshot of what you see and post it here? It would help me understand the issue you are having better and help you resolve it faster. Thanks :)

Thanks to Nomana's rapid response, I've compiled a fix for those of you who might have issues with the gauges displaying wicked data and erratic behavior! Go to the main post and download the Gauge Pack only package! It contains version 1.1 of the gauges modules which fixes the issue described above! Thanks for helping me find those issues out :)

Quick Update: I have found an issue that might be a problem on localized versions of Windows which causes the gauges to display incorrect data. This is due to .NET's way of handling double variables and how they convert which deeply depends on your Regional Settings. I'm investigating this issue now with Nomana and once I confirm its the cause of the bug I will release a hot fix to everyone who is getting awkward gauges readouts!

1. Glad you got it working easily! 2. Gauges displaying wrong data could be a result of numerous reasons. First you have to make sure you download the package which is right for your system (x64,x86). It is also important to not modify anything in the Export.lua file to prevent data corruption. There might be a very "slight" indication "gap" in 2 gauges (the engine temperature gauge at the lower 40's is the most noticable and the oil pressure gauge). These issues will be rectified in the next release of the Gauge Pack. The rest should be to almost perfect precision. 3. HawgTouch notes that Data Export needs to be enabled to make gauges work. But it doesn't check for installation of the A-10 sim on your machine and doesn't require the "SAME" machine to be the one sending the data to HawgTouch. In short, if you set the IP in the Export.lua file to your laptop, and HawgTouch is running on it. If the data will be received on your machine, the gauges will come to life. I suspect that the data is not being transmitted by the sim or received properly by your laptop which is what's causing the issues. I suggest making connectivity tests between your machines and to make sure that nothing interferes with port 1625 (UDP only). If the issue still remains let me know and we'll get this sorted!

Pretty good odds id say! HT wa tested on both XP and Win7. Server 2008 (not R2) is Vista core based and should work with no problems with .NET 4 installed.

Do you see any of the other gauges? This sounds totally strange. If you see 1 gauge you should see them all as they all are packed in one module. Please provide more details so I can try and help you sort this out. Did you modify the default profile by any chance?

:) TY I wouldn't have a clue on where to start with FreeTrack, but it could be something for later later on :)

The issue you are having is due to HawgTouch bug that was fixed earlier today in a hotfix. If you read the earlier posts in this thread you will find more details! To fix your issue simply go to the first page of this post and download HawgTouch again. The new packages have an updated executable which fixes this minor glitch! Im glad to hear you are enjoying HT :D

Some updates! I've started working on the second batch of gauges! I decided to tackle the one I fear most to begin with. It will make the rest easier. Here's the first sketch of the HSI. Which will be released in the next version along with the rest of the gauges for the A-10C! Also planned for next version, the ability to support multiple HawgTouch clients to receive simulation data with an easy to use wizard! More updates to come soon :)

That's up to ED :) I'd love to have one so we can help everyone trying to set HT up!

Actually, the UFC does have 1 button which can receive data, that would be the Master Caution button. If you want to see it come to life all you have to do is add this line to the button definition in the xml: <DataImportID>MASTER_CAUTION</DataImportID> Here is the "static" master caution button: <Button> <Name>MASTERCAUTION</Name> <Clickable>true</Clickable> <PressedImage>\Images\UFC\ufc-Mcaution-on.png</PressedImage> <DepressedImage>\Images\UFC\ufc-Mcaution-off.png</DepressedImage> <Type>ClickButton</Type> <ID>20</ID> <Y>11</Y> <X>573</X> <KeyCommand>1</KeyCommand> </Button> Fixed code <Button> <Name>MASTERCAUTION</Name> [b]<DataImportID>MASTER_CAUTION</DataImportID>[/b] <Clickable>true</Clickable> <PressedImage>\Images\UFC\ufc-Mcaution-on.png</PressedImage> <DepressedImage>\Images\UFC\ufc-Mcaution-off.png</DepressedImage> <Type>ClickButton</Type> <ID>20</ID> <Y>11</Y> <X>573</X> <KeyCommand>1</KeyCommand> </Button> This line makes the button receive data from the sim and turn it on/off according to the status received by the server. I'm seeing that multiple "receiving" ends is something people would want to see in the future so in next releases I will expand that Data Exporting function to support multiple "clients" and seamless "remote" configuration from within HawgTouch itself.