Helios on Slave PC help needed: Gigurra, Morphine, Rouge and Ice Profiles
-
Hi and happy boxing day 2014:)
Got me some new toys this week from very nice Santa Bloke
Thrustmaster Warthog arrived by sleigh from Germany in 3 days(alternate.de) £70 cheaper than any UK source (thats if you can find anyone with one in stock anywhere in the UK).
Set it up using Morphines profile run in TARGET Script Editor and spent a few hours getting my score up to 60,000 in instant action. I Died xmas day in a head on air to air with a MIG19 and almost fell out of my chair!! HOTAS rocks:)Next toy was a 22 inch touchscreen, installed it with Gigurras Pit Tools and Helios on a second win 8.1 PC and used Rouges Helios profile.
In Rouges Target Script I removed the // remarks from the Warthog section and put // to remark out the Cougar section.
This all worked some shape and I could initially control some things correctly in BMS with rouges profile in Helios on the slave PC touchscreen ICP buttons, laser arm, master arm. Some other things did not work correctly, Canopy Open/close, elctrical master.
I must have something wrong in the edited target script though as the controllers list in BMS had Warthog Stick, Warthog Throttle and Thrustmaster Combined listed in BMS. Morphines profile just leaves Thrustmaster Combined in the BMS list.
Q1: Not sure if this is correct or do I need to fix something in the TARGET script?The current problem I deffo have to fix is as follows.
Q2. Helios no longer talks to BMS across the network.
I found when it was working initially that Helios will not talk to BMS at all unless you run it as Admin (I think it may be a permissions thing that is the source of my current problem)
Fault Diagnoses I have done so far
1. I created a little Helios test profile for testing with just one switch and that won’t work either.
2. Keyboard test of GPT transmitter/receiver works fine (notepad open on both PCs and text typed on TX PC appears on RX PC as well.
3. PC has now been rolled back to earlier date, Helios, GPT and Java Development Kit all re-installed still no joy.
4. Installed all of the above on a win 8.1 laptop same network using Wi-FI and the test profile switch works fine sending the callback and BMS responds correctly.
5. Read every post on this forum!! (well it seems like it sometimes)
6. Googled Helios Network problem, not a lot of information available, I dont know what the next steps in diagnosing the problem are.The fault arose after some tinkering by me in Rouge.tmc using TARGET Script Editor, Rouge.key using notepad and Rouge.hpf in helios script editor. Just to make it more difficult to diagnose Win 8.1 decided that this was a good time to do some updates GRRR.
Any help greatly appriciated.
Thanks to Gigurra, Morphine, Ice and Rouge for their profiles and work. I would have taken years to get to where I am now without being able to use the work you have all previously done which must amount to 100s of hours.
PS: As another Noob request a link to the best Idiots Guide to a Team Speak tutorial pretty please.
GT:
Some challenges I overcome along the way
GPT runs fine but you neeed to edit some of the files in each tool to match your network IP settings
Java will moan about server not available if you install JRE it is included in JDK
USB ID assignment is a PITA, I now have various key files to match whatever windows decides is todays flavour. -
I have a similar setup as you and been using Helios and Gigurra magic programming, your right about running helios as administrator… This is one of the steps, the other is to ensure Helios is ran on both Pc’s this will then communicate the lights and switches, on the main pc just need to run the helios box and ensure its toggled on, no need to run the profile… Then on the second pc run profile.
Other than this run second pc first with helios and GPT then launch main pc…
Let me know how you go… I am glad you have joined the party of two pcs and helios, this should be standard… lol Gigurra is a legend.
Drop me an email, be great to chat about it [email protected]
-
I seem to have a similar problem.
Display receiver working fine, KeyCom working fine - when I type in notepad on the slave while notepad is the active window on the master, too. everything works.
when I hit ‘2’ on the ICP in Helios ‘2’ is written on the slave PC’s notepad window - but nothing on the master notepad. Directly afterwards hitting ‘2’ in the notpad on the slave it is transmitted.
To me it looks like keycom is only transmitting ‘real’ keypresses but no ‘artificial’ Helios produced keypresses.
Any ideas on this? -
I run Helios with the TM WH and with one pc and two monitors using ICE’s helios profile and key bindings (which are only slightly different than Morphine’s key bindings) on Win7 with no problem. I don’t use a network. What is the reason you are using a network? I am not that tech savvy so I don’t use Gigurras Pit Tools whatever they are.
-
-
still fiddling with touchscreen settings, no luck so far.
It must be some configuration of Helios. I tried sending out a keypress directly (used the Falcon interface = keyfile) before. No luck either ……
-
Livrot, are you running helios on both pc’s as administrator??
Master is just ran as power on as the same profile…
Slave Pc then runs on second with profile, it is vital you also use the same key file in both helios setups, so you will need to go into helios and explore and introduce a falcon profile with a Keyfile on both pcs…
happy to speak to you both about it, I had the exact same issue as you are having…
-
Hi Sobe, basically I went from 30 fps to 60 fps overnight, much better way of extracting mfd’s and ded… It works so well.
-
aclisset: I just have to run Helios on the main PC as admin? how do they communicate? any ports to open - IP adresss to forward?
I am using a simple LAN connection on two win7 machines - no homegroup.So you do not use giguras keycom transmitter?
-
I will check this now:
http://www.keyboard-and-mouse-sharing.com/keyboard-sharing.htm
-
-
This post is deleted! -
neither app transmits the keyboard exclusively …
gonna have to create a small app for this on my own.
I really wonder why the keycom transmitter fails to pick up the helios keyboard output.
-
I tried aclissett’s idea as above and ran HELIOS as administrator on the BMS PC with the
HELIOS control center running with no profile loaded.
BMS or notepad as active aplication on the receiving BMS PC would still not get any communication from HELIOS on the other PC but Notepad to Notepad was fine.I then ran the HELIOS install.msi again on the second PC that is just running HELIOS and and chose the repair option. I then created a new one switch, one button test pofile. The touchscreen then worked briefly for a while and I got input from switch and button from the profile on the HELIOS PC accross the network into BMS and/or Notepad
This was a short lived fix though as I broke it again 20 minutes later
I THINK this failiure was as a result of starting HELIOS without the keycomtransmitter running.
Still tinkering but another attemt at running instal.msi repair option has not brought it back to life this time.
Kind Regards
More to follow
GT
-
gadroc’s forum is down due to spamming and him having no time.
I have found it on the wayback machine.
http://web.archive.org/web/20141024221917/http://gadrocsworkshop.com/forum
-
Hi, back working again after HELIOS uninstall, registry clean reinstall, think it was all unneccesary though as I just found that TX/RX currently only works if I
1. start HELIOS control panel as admin
2. Start Key TX
3. Start HELIOS Profile
Any other order it does not TX/RX from HELIOS but does TX/RX from notepad.Next challenge is switches and buttons are now working correctly if clicked with a mouse but if I use the touchscreen the switches work correctly but buttons send two callbacks ie type 2923 on the ICP and 22992233 arrives in the RX PC anybody else get this or know what this problem is?
Regards to all
GT
-
Yes Livrot I do use Giguras keycom transmitter, however helios still needs a keyfile from your BMS keyfile so that when you input a button or switch in helios on the slave this translates into a key output, all that gigura key transmitter does is too send the key commands… I do use the keyboard and mouse sharing software however this is not needed, just easier when controlling two screens with one mouse and keyboard. However when I commit BMS I always turn this off as can conflict when using in the jet.
Happy to skype to go through or Teamspeak on falcon online or 185th … My call sign is Tank
-
Hi, back working again after HELIOS uninstall, registry clean reinstall, think it was all unneccesary though as I just found that TX/RX currently only works if I
1. start HELIOS control panel as admin
2. Start Key TX
3. Start HELIOS Profile
Any other order it does not TX/RX from HELIOS but does TX/RX from notepad.Hi
Next challenge is switches and buttons are now working correctly if clicked with a mouse but if I use the touchscreen the switches work correctly but buttons send two callbacks ie type 2923 on the ICP and 22992233 arrives in the RX PC anybody else get this or know what this problem is?
Regards to all
GT
Hi GT, the problem is under the settings within the touchscreen setup under windows, you need to go into settings and uncheck one of the boxes in the pen touchscreen settings under control panel in win 7/8. I believe the default is set too double click when taping on screen this box needs unchecking…… then your good to go!
-
The order of how you start things should not matter as long as you load slave GPT then master GPT using JAVA, I can send you the Read me file I have that “Yoda” aka Gigura completed for me, one is ran from the slave then the next on the gaming pc… then your done…
Send me your email address and I will send you them, this way it starts everything you need to complete the files needed to be ran.
I have spent hours trying to figure it out looking for complicated ways and outcomes… The programming is the only hard part of this puzzle, the rest is easy… Well done Yoda…
-
Hi, back working again after HELIOS uninstall, registry clean reinstall, think it was all unneccesary though as I just found that TX/RX currently only works if I
1. start HELIOS control panel as admin
2. Start Key TX
3. Start HELIOS Profile
Any other order it does not TX/RX from HELIOS but does TX/RX from notepad.Next challenge is switches and buttons are now working correctly if clicked with a mouse but if I use the touchscreen the switches work correctly but buttons send two callbacks ie type 2923 on the ICP and 22992233 arrives in the RX PC anybody else get this or know what this problem is?
Regards to all
GT
I have tried this already - doesn’t work for me.
ATM I have made my own transmitter and working on the receiver. Will publish if successfull.@ aclisset - could you post the stuff wrapped in ‘code’ tags here?