It's kickin me while I'm down!
-
Little bits at a time, I’m working thru the issues. Need ya’lls help again.
I just got a Dell 2418 Touchscreen, and after finally sorting it out so that the main game isn’t affected by what I do on the touchscreen, I have a new issue.
Using the newest Yame 64, I get the gauges (just rwr lfmd and the pedestal for now) and start BMS in full screen. BMS shows up on my 27" AOC, and the gauges show up on the DELL, but the moment I touch one of the buttons on the gauges (touchscreen), say the MAP button, it dumps BMS to the taskbar, but the gauges stay responsive. I have to go to the taskbar with the mouse and “restore” BMS - which works just fine, until I touch another button from the gauges, or - in fact - ANYWHERE on the DELL screen, gauge present or not.
If I start WINDOWED, it doesn’t happen, but the “Windowed” version only covers about 50% of the screen and I can’t get more.
Thanks in advance,
Tril -
You tried my profile?
-
Your xml profile? Yes. I got the problem solved, and deeper simming revealed a couple of issues that I can NOT figure out.
Your profile is really great, but I prefer the DUNC DX files for my Cougar. The DX programming is simple, reliable, and matches the functions. Of course there are conflicts with your profile. IE if I use your xml and DUNC dx for the Cougar, then certain things on the stick just “work”. Wearing my track IR, the hat acts like a cursor in the default position (instead of view) and when the pinkie switch is held in it gives me TRIM. I like it that way, and it needs to be that way because if I turn on the MOUSE/MICROSTICK it causes the radar cursor to scan up and to the right, increasing the ranges so fast I cant lower them. It’s unusable.
Ideally I’d like to merge DUNCs tmm/tmj with your profile. I’ve made a couple of attempts but it breaks the DUNC functionality-and the way I was doing it resulted in only the first 10 mfd buttons working on either mfd. Lots of searching in the configs to figure out what was causing the mouse/cursor problem. Even though I had the mouse turned off in my TMJ file, I hadn’t turned it off in the CCP. I was using the toebrakes on the Simpeds with digital statements so that I could use the toebrakes AND the mouse. Turns out that it was the cause of the drift. Disabling the Microstick in the tmj AND the ccp solved that issue, many more to work out. Any advice on the best way to merge these files?
Cheers
Tril -
No, I meant my Helios profile. Your initial post hinted at an issue between BMS, YAME, and Helios, so I don’t see why you’re talking about my TARGET profile. Might be best to make a video to show/explain what issues you’re having.
As for my TARGET profile, using it is not required to be using my YAME and Helios profile. You can use Dunc’s stuff and it should not be an issue.
-
I am not referring to your TARGET profile, but the COUGAR profile created by FOXY (not TARGET)
When I use DUNCs tmm and tmj files in my COUGAR and the corresponding DUNC.key file in F4’s setup, I get HAT 1 functioning as a radar or view cursor. I can use it to easily pan around in the mfd’s for such things as the TGP and MAVERICK calibration and targeting,
SUMMARY:
HELIOS runs Ices BMS 4.33 v4.21s.hpf profile
The keyfile used in HELIOS is BMS-FPM by-Ice.key
Up to this point it works wonderfully. All the KEYBOARD commands work. Here is where it gets messed up.
If I select your BMS-FPM by-ICE.key in the SIM/SETUP/CONTROLLER section I lose some of the DX mapping (most importantly the way the pov hat works as described in the first part of this post), but most of the cockpit devices work fine,
If I select DUNC’s .key in the SIM/SETUP/CONTROLLER section the dx assignments in the stick work great, but the cockpit loses 80% or more of it’s function.
So, I’m either doing something wrong, drawing the wrong conclusions about what file does what, and their interdependency, or need to figure out the best way of manually merging the .key files.Here is how I attempted it a couple days ago,
I opened the HELIOS/YAME stuff on my 24" Dell Touch and opened the SETUP/CONTROLLERS section of BMS on my 27" main monitor.
The CONTROLLERS selection was DUNCs DX.key and the HELIOS and YAME stuff was set up with BMS-FPM ICE.key.
I would go thru the DUNC file line by line, and when I found a mismatch I would press the corresponding button on HELIOS and it would remap that button in DUNCs profile.
Seemed logical to me, though time consuming. However it didn’t work well. It messed up the dx efficiency of the stick, and the buttons themselves weren’t working properly. IE: on both the LMFD and RMFD only the first 10 buttons worked. AP switch on the left worked, the one on the right didn’t. Many more bugs like this.
So, should I even try to merge them? Merge them a different way?
Hope that cleared it up.
Many thanks
Tril -
You cannot tell Helios to use my .key file but then go into BMS and use Dunc’s .key file. You’ll have issues right away. You’ll have to use my .key file for Helios to work so I suggest importing the DX mapping from Dunc’s .key file into my .key file. Open both files in Notepad++, copy everything from line 1156 onwards of Dunc’s .key file, delete everything from line 1153 onwards on my .key file, and paste Dunc’s lines there. Save my .key file under a different name, like BMS - Tril Custom, and use that .key file in both Helios and BMS.
Good luck!
-
HUGE success ICE!. I keep layin 'em in there and you keep knockin 'em right outta the park!
Little glitches here and there but I think I can sort them out.
Again, thanks
Tril -
Hehehe… thanks for the kind words! Glad that worked out for you! Enjoy!