Hello, Does anyone know how to fix the missing image of the “ICP Panel” in Ice’s Helios profile? I think after updating Helios to the latest build somehow ICP image changed locations and now is not showing up in the profile.
Posts made by Sleeper.M
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
-
RE: YAME64 suite
Hi Sleeper,
Read my first post#1179 page 117 and the subsequent discussions with Ice and others. It looks like the WIN 10 update and or Nvidia updated drivers, are part of the problem. I had the same issue, default YAME profiles would run fine, but modified ones (like Ice’s) would slow down the computer to a halt. I reverted to older WIN10 and Nvidia drivers, and everything works beautifully.
Johan
Thanks, I think I subsequently figured out the issue on my end at least. So after messing arounnd with the Keyfile and discovering that something changed either with windows or because of U5 I decided to take out any formatting that was in the Keyfile. ICE uses a lot of formatting such as ############### to add description etc to his keyfiles and a lot of ============== to make it pretty and separate the different areas of the the callbacks. Well you know how if you replace a key with in the UI with one of your own and save the file it removes any of that formatting and makes it similar to a default key file. Well that solved the issues on my end it seems. Stay tuned in case something else pops up. Again not sure if it as U5 or the creators update that caused this. I actually used DDU uninstaller to Remove any older Nvidia drivers and re-installed the latest driver which is 391.35. So far everything is working on my end. Again stay tuned ya never what will happen with Win10 and their updates.
-
RE: YAME64 suite
Hi Guys. I’ve got the same problem. Win 10 updated 2 days ago and now I’m getting the same window as you Sleeper. M. In fact this recent Win 10 update even corrupted my mouse pointer. I rolled back to a previous restore point which I hope - fixed the pointer (will see when I shut down and restart my system), but no joy with YAME. I lost Hellios a few months back with the a similar stop working window. Now YAME - Heaven FORBID. I can’t live without my YAME. I’m running a 4 monitor setup with along with a Samsung Galaxy Tab A for my moving map and a separate ICP replica. Please help Roccio. Happy Easter to all.
Ok I’ve been trying to figure this out and up until this morning same issue over and over. Well I’m not sure what happened but I was able to get YAME64 to load completely by having one of the default BMS Keyfiles loaded within BMS and not my personal edited keyfile. For some reason Yame is not liking the Key file I had been using for months. (Maybe it was to much formatting going on inside the key file or a conflicting DX assignment). Try opening BMS and then loading a default applying it then closing BMS then Launch YAME64 and see what happens.
-
RE: YAME64 suite
Hey sorry for the lack thereof and late response I was out of town for a few days. I’ve taken out any custom xml file and was just trying to get it to start stock. So I believe it loads the default xml file right. I’ve uninstalled and wiped the registry and will try to reinstall and see if something changes.
-
RE: YAME64 suite
go to yame installation folder then in conf folder you will find yame64.xml. try to rename it to something like yame64.old and restart program.
Update: So I tried what you suggested and it didn’t work. Nothing changed that I can see. Doing that just created a new yame64.xml file. It is still crashing doesn’t get any farther then the picture above. When I go into event viewer in Win 10 this is what it says so maybe this VCRUNTIME140.dll got corrupted some how? What do you think?
Here is what the Event viewer says:Faulting application name: YAME64.exe, version: 0.0.0.0, time stamp: 0x59afa99e
Faulting module name: VCRUNTIME140.dll, version: 14.13.26020.0, time stamp: 0x5a39fee3
Exception code: 0xc0000005
Fault offset: 0x000000000000ca27
Faulting process id: 0x2e78
Faulting application start time: 0x01d3c3338db496a6
Faulting application path: D:\YAME64\YAME64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 45be4c30-fcfe-4b0f-9975-816802ddd040
Faulting package full name:
Faulting package-relative application ID: -
RE: YAME64 suite
Ok guys need your help. I had Yame64 working great for months. Not sure what happened but here is what changed Windows 10 updated and I also installed BMS U5. Now Yame64 is crashing every time I try to launch it. Not sure if it’s a result of U5 or the windows update. When I try to launch the UI open’s a white box then immediately crashes and I get the following message. So what do you guys think? hopefully someone has seen this and knows what I am missing here. I vaguely remember this happing before but I don recall how or what fixed it lol. It doesn’t generate a log I’ve checked multiple time and the log file is empty. Any and all help is greatly appreciated.
-
RE: YAME64 suite
Thanks for the response but I got it working by simply starting over with “Morphines” Paddle shift profile. I think I had some keys that were conflicting with what I had Edited within ICE’s Key file. Maybe to many conflicts caused the key file too crash the .exe. I cant call it but if I figure it out or it happens again ill let ya know asap.
-
RE: YAME64 suite
Hey guys. First off thanks for an awesome piece of software. It has worked flawlessly but as of late not so much. I was wondering if anyone has experienced something similar, and how did they fix it? For some reason when I change key files with-in Falcon and close it down the next time I try to open and Run Yame it immediately crashes and gives me the “YAME64.exe has stopped working” pop up. I’ve isolated the problem to a key file issue. Something within the key file has caused this crash but I cant figure out what it is. Would conflicting assignments cause .exe to crash? Any and all help would be greatly appreciated. Thanks.
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Well just to update you on what I’ve had to do. The above configuration you said to try did not work for me. I cant figure out why especially after what I ended up doing. So I started a new profile and have copied and pasted several pieces of your profile to a new one with my screen laid out the way I wanted. I have mapped most of the ICP and both of the MFD’s to Morphine’s “paddle as shift layer” key file. I’ve had to enlarge a few things as I’m using TM MFD’s on top of my touchscreen, just for immersion, and the rest as touch. So far what I’ve gotten done has worked and lined up perfectly. A couple little issue’s that I need to work out still but for the most part I’ve just looked at your profile watched your tutorial’s and tried to put it all together. I’m working on incorporating YAME64 now. Thanks for all your help and the use of your profile I’ve learned a hell of a lot about Helio’s , BMS and and now YAME trying to get this all working. Still have a lot of work to do as I’m sure you probably spent days getting it working for yourself right?
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Thanks Ice. I will do that today and see what happens I bet that is the problem. For some reason it probably just don’t want to line up with the profile. A resolution conflict is probably issue. Stay Tuned
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
All 4 monitors go into one GPU. 3 via display port, the touchscreen is HDMI. My main center monitor is 4k but it is set at 1080p like the rest. Display settings are all at 100% recommended size, nothing up scaled. I’ve done the Touchscreen calibration alignment a couple of times just to rule that out and even made sure it was manufacture drivers for each monitor. Touch screen seems to work fine when opening and closing programs and the internet by touch, so I cant call it. I’m going to try and create a new small profile with a couple switches and see if they work and line up. yeah I will try to post a picture or two.
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
1.) A: The touchscreen is this one http://www.microcenter.com/product/467866/thinkvision_23_led_touchscreen_monitor.
Yes all monitors are powered by the same pc, using two GTX 980’s. I turned on surround like you have it setup to see if that made a difference, it seems to have or it was something else i did. But this is what’s happening now. So i load profile for single touch screen reset monitor’s, save to my layout. Close editor load up TrackIR, Load up target with your .tmc i run profile wilth Helios and it pops up beautiful right where it needs to be. So i proceed to start Falcon and go into setup where i confirm your key is loaded. I test right there in that UI screen under controller and and see if the buttons function and pop up next to input. At first i couldn’t get anything but now they will work but it seems the spot on the touch screen that you have to press is about 2 inches to the left of the the actual image. For example: to press the master caution i have to actually touch about and inch and a half to the left of it, in the gray area for it to register a depress. I cant call it but I’m determined get it working so all your help is very much appreciated.
Q: do i need to be running in windowed mode ? Also does the mouse capture need to be enabled in config or anything like that. How about when i reset monitors does scale have to be checked? Also the profile i have doesn’t look exactly like the picture you posted. The buttons like TrackIR Pause, Pause, and freeze are all on the right side of the HSI, the AoA indicator and fuel selector knob etc. Maybe i have downloaded the wrong link for your profile.
-
RE: Helios acting crazy, mouse but no touch. I need help. Please
Having Windows 10 creators update installed.
-
RE: Helios acting crazy, mouse but no touch. I need help. Please
ICE, I just read this could this be the issue to all my problems that I mentioned in a earlier post? Has this not gotten resolved yet?
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Ice, So I pretty much have the same set up as you. Just lacking the second touch screen that you have on the lower left. Most of the time I only run the center monitor when flying, just recently got my Lenovo touchscreen for the lower center console etc. The profile shows up on the touch screen just fine and doesn’t move loading Falcon and changing from the UI to 3D. The problem I’m having is when moving a button or knob on the touchscreen nothing happens in the pit. I’ve tried it in Instant action also in the TE’s and even starting a new campaign. What seems to happen is when I touch a button on the MFD or even the UFC on the touch screen the mouse cursor on the main flight screen also moves. None of the callbacks attached to the profile seem to be activating any corresponding functions in the 3D pit. I have the Helios pointed at your key file in the config folder. I have Helios pointed at 4.32 or should it be seeing 4.33 ? I’m running TrackIr, Target and Helios all as Admin, and starting them prior to loading Falcon. Do I need to change something in the config to capture the mouse cursor or is that not needed? Does this all Require Yame for it to work? Or Yame only for the Extracting of the gauges and MFD’s ETC? What am I missing Please Help. Thanks
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
ICE, Thank you for the fast reply, that would be great. Yes I reset the monitors as advised, although I may not have put them in the correct order within windows before doing so. I think I glossed over that part. Let me try it again and see what happens.
-
RE: -Ice's Falcon BMS Helios Profile Updated… Again!
Hello ICE,
Is it possible to get the photo links updated or changed so we can actually see what you have posted? I’m having issues on my end running a four screen set up in the '“T” formation. The touch screen being right below the center monitor. I’ve followed the setup instructions and can not get it working. I know I’m missing something and being able to see the pictures might help. Thanks for your time. -
RE: Target Scipt Editor Error need Help please.
Hey Mud
Thanks for your help. The problem was in the “file path” under the Tools/options/file paths Tab. I had it pointing to the wrong path. It should of been pointing to the :
C:\Program Files (x86)\Thrustmaster\TARGET\scripts.thm That’s where that .thm file is. Wow something so simple right? Thanks again for your response and all.
A fellow Viper pilot from UO “DarkFib3r” walked me through it