Same if not similar issue. I could get the 1920 setting to show in setup, and when I entered the sim, but when I’d arrive in 3d in my jet it would have dropped to 1280 x ? 800. What I found was that if you have WIN 10 build 1809 or higher you are screwed. The only way I found was to use an older WIN 10 (build 1709) and buy a license from (MacroSelfish)
Additionally, do NOT allow any updates to it that are NOT security related.
This has something to do with a conflict with nVidia and WIN 10s versions of “Display Optimization”
With MSs’ new policies towards these kinds of conflicts I wouldn’t expect no help from MS.
g’'luck
Trilogy
Posts made by Trilogysc
-
RE: Windows10: Unable to get desired display resolution 1920x1080 in game 3D
-
RE: New problem New thread
Tried that, and no difference. Helios will SHUT DOWN if I try to open the profile that was working for a year on WIN 8.1, but will stay open and run fine if I create a new file and save it.
So I’m not sure YAME is the problem, seems HELIOS might be. It acts as though the monitor setup is wrong, but I can’t get into HELIOS to sort it out.
Next guess? -
New problem New thread
Been running Helios and Yame (latest versions of ALL file types) on Win 8.1 for about a year - not perfect but happy with it. Steam causes some micropauses in my desktop apps, and every now and then F4 would refuse to load. Remedy was copy/ pasting an archived copy of the F4 exe.
Finally got tired of all the glitchy stuff, copied all the .xml, hpf, key and every other file that made up my Helios install and did a clean install of Win10 CFA (1709)
I then installed F4 v5, Yame 1.21, latest (same versions as before) helios and Yame.
When I start Helios, it opens fine. When I load my .hpf file it fades out with a spinning circle in the middle, and goes away. No error message, nuttin.
No matter what/how I try to get my profile running I get the same result.
However, if I create my own file thru the EDITOR it opens fine…. but never in any circumstance… does it show FALCON in the list of devices, , though it does show my Cougar.
I’ve tried editing my layout xml and every other thing I can think of.
This hardware is the same that has run F4 of nearly a year and I am now officially baffled.
Need HELP from the masses.
TIA Trilogy -
RE: Curiosity Poll - How much did you spent for HOTAS (stick and thruttle)
Another Colorado pilot! That makes 2 of us!
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Downloaded it again from here: http://www.mediafire.com/file/k85jg9eek97h0m9/BMS±+FPM+by±Ice.key but still doesn’t work]
Regards.
Greyfox, I just tried the link you listed, and it seems the date of that file was from March 14th of 2017. An older version.
Try this link
http://ihpff4bms.blogspot.co.uk/2017/09/v421s-release.html
and in the RIGHT frame make sure you have SEPTEMBER selected. You’ll find v4.21s there.
I’ve found that if you just click on the link in post #239 you MAY end up viewing the blog from the MARCH entries. I suspect it will do this for many first time visitors of Ice’s blog.
Fingers crossed
Tril -
RE: It's kickin me while I'm down!
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 -
RE: It's kickin me while I'm down!
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 -
RE: It's kickin me while I'm down!
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 -
WIN 10 and Cougar
This is likely common knowledge here, I just found out that onboard graphics with the i7 7700k chip will ONLY work with Windows 10. There are other artificial limitations that Intel has put on this architecture to force folks into using it, such as dx12, but it presents me with a problem.
I had planned to roll back to Win 7, or stay with Win 8 because of the difficulties I have always had (after xp) to get my Cougar properly recognized by them. I know all of the procedures, throttle disc, trigger in, etc, but even with Win 7 and 8 the ONLY way I could get the Cougar to be seen ( the in/out ) was to plug it into an old USB 1 hub. USB ports, hub or mainboard would NOT work, just the ol’ hub. Well it’s busted now and I’m at a loss for what to do.
btw, once it was recognized I could plug it into any port I wanted and it worked fine, the problem was always the initial install. Anyone else face this issue and figure out a way around it?
Tril -
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Guys, at the end of the day we are a Band of Brothers joined in a community attempting to enjoy the experience of F-16 flight simulation and, I’m sure, other aircraft as well. Laughably, my experience has been vexing as I’ve spent the last couple of years just trying to get this sucker to work. In all honesty, I haven’t flown a full mission yet. But when I eventually do, I’m going to do it right - with all the bells and whistles.
This immersive experience, living for brief times vicariously thru the experiences of the real heros that flew, and fly for our rights, is something I have failed to find a way to convey to those close to me that are non simmers. But mikemadmax, you nailed it. You described it precisely, thank you Sir.
Tril,
out -
RE: YAME64 suite
That didn’t work. A couple of starts then back to the same error. I may just put this off for a couple of weeks and do it on a fresh install on a new puter, but I’d like to find out why and what the fix is now so if it happens on my new box I’ll know what to do about it.
If anyone would check and report on the version of VisualStudio 2015 they have, and whether or not it is giving them problems it might help a lot.
Cheers
Tril -
RE: YAME64 suite
So along the path of a jacked up vb 2015, I went to control panel and selected to “REPAIR” it.
It’s working now, but I’m afraid to reboot.
BTW, somehow the version I have is newer than the version available via google search and a MS search.
14.0.24215 vs 14.0.24212
Well, off to scorch some clouds - fingers crossed -
RE: YAME64 suite
Can you check recent program updates? I’ve had a similar issues about 6 months ago and it was due to a recent VisualStudio 2015 redistributable 64 bit update. Rolling back to a previous version fixed it, and a later update a month or so later didn’t have the issue.
Well that didn’t work. If it is the c++ library it brings up a question. The version of c++ that I have installed is 14.0.24215. Could you tell me what version you have? I am getting the same error, vcruntime140.dll = although the verbage is different now
-
RE: YAME64 suite
I suspect that its something like what happened to yours. Issue I’m having is that there is a problem registering the .dll
First off, I didn’t realize that 32bit .dlls go into syswow64 bit folder, and 64 bit dlls go in system32
Once I figured that out I made a bit more progress, but not over the hump.
Trying system restore now, fingers crossed. -
RE: YAME64 suite
I keep getting an error (yame has stopped responding etc,) and it names VCRUNTIME 140.dll
I have replaced it, now it tells me the application cannot start correctly,
This started when I exited the game, and YAME was still minimized. The "stopped responding " error ccame up while it was still minimized, and from that point forward it would never run again. Initially it would act like it had loaded, but remain minimized, and useless - I couldn’t start it or the client - I then reinstalled it (after uninstalling it and all of the folders that it needed.) and that is when the Stopped Responding error began. 10 hours so far and no gain.
Need some more help please,
I7 920 @3.2, 6 gig ram, 660ti, 27 main, 24 Dell touch. -
RE: Curiosity Poll - How much did you spent for HOTAS (stick and thruttle)
I knew I couldn’t be the only one that was this devoted, but I never thought I’d see someone else with MORE commitment than I! As for evidence, I said my wife knew about it, but didn’t say she liked it! She “tolerated it”.
Her favorite pastime came right after I got VAC. She’d sneak into the office, wait until JUST ThE WRONG MOMENT, and shout out EJECT EJECT EJECT!!! Then laugh all the way down the hallway while my carcass floated to earth…
ahem, notice I’m speaking of her as my wife in the “PAST TENSE”….feel free to fill in the detailsDang cool cause youre a die hard TM dude like me…
I dont EVEN want to add up my TOTAL as it would be evidence in court; but i started with the FCS, WCS and RCS for Falcon3 on Win31 on a 8" color Toshiba laptop with math co-processor, high mem manager, batch file. 14.4kbs hayes modem, paralel gameport interface. Lets say I have a “collection” of just about every upgrade since.
Still have the laptop and F3 still runs. Whoa nelly, have we cone a long way since.
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
I finally get it all working, and you have to throw out something better, sigh.
I LIVE FOR BETTER!!!
Time to build a new box then!
Cheers
Tril -
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Yes, and it does work well. It would be a TREMENDOUS help if some would put the 1.1 version on the www.yame64.com site. Other than an archived copy I had, there was no other 1.1 release available that I could find on the interweb.
Sorting out a few bindings, and learning about all the parts that get put together to make this all work. So far, about 90% is good, which is actually a new record for first time out-impressive.
What it does for immersion, for me, is amazing. Thanks to everyone that created or helped with the pieces, and to those that put them together to make this manageable (that would be you, ICE).
Off to scorch some clouds,
Tril -
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
I am having the same problem. I have verified that all of the files are in the correct location, windows 8,1 64 bit. So close to getting this to work!!
-
RE: Curiosity Poll - How much did you spent for HOTAS (stick and thruttle)
Started with FLCS and TQS, about $300 in 1996. TOTAL $300
Upped the ante’ to an FLCS Limited and TQS a couple years later. FLCS Limited -$500, TQS $150, and TM RCS $100. Added the sw22 and asked Bob Church to create a calibration routine with “Dead Zones”, that was free and the best thing that happened to that stick until my next-and last step up. TOTAL $750
What I’ve had since 2004: TM Cougar UBER2 NXT. HALL sensors in stick and throttle as well as SIMPEDS (with toe brakes) Errors in manufacturing have been corrected (alignment of the AirBrake switch and the DogFight switches) and I can’t say how many thousands of hours I have, but it’s been a blast! TOTAL $1300.
Accumulative $2350. And my wife knew about it!!! Now how cool is THAT!??