YAME64 suite
-
This post is deleted! -
@Jaycee & LAB93 I’ll post the image I use asap, it’s nothing special, you still need to overlay everything with the necessary gauges & indicators of course. I can also make a screenshot of my image when Yame client is running so it has everything on it so you can use it as a placeholder for where to add the gauges & indicators. This is just for my screen of course. You could also check -Ice or some else Helios setup. That also features some sort of cockpit image you could use.
@Mailman
I don’t know the technical issues, that would be more of Roccio’s expertise, but I do find it strange there timestamps seem out of sync somehow?
For example your server log says:
03/02/2018 11:37:18: New TEXTURE client connected
But the client log says:
03/02/2018 11:27:25: Texture connecting to server.
03/02/2018 11:36:33: Texture data extraction stop.So the client connected at minute 27 and stopped the connection at minute 36 while the server only has a connection after that (minute 37)?
I didn’t run it very long. As soon as I knew it wasn’t working, I exited BMS and stopped both the client and server looks like at 11:38:45. Not sure what’s going on before that. I may try leaving it running a little longer and post the new logs. And after looking more closely at what you pointed out, it looks like a possible client issue? Could it have anything to do with Video Driver?
-
I have the server running on my main machine where BMS is running and the client running on my networked machine.
Try it the other way round? i.e server on the networked machine and BMS machine as client and make sure to select get data from network on the networked machine.
-
I cannot get any extraction. I am running a networked PC to show MFD’s and RWR. Network is open, Firewall off, etc. I have the server running on my main machine where BMS is running and the client running on my networked machine. Myself and Badger worked on this for hours. Everything is set up as it should be. RTTExtraction on 0 (tried it on 1 too). Using Yame to start up BMS. I am stumped. Here are my logs.
From server:
Server Log
03/02/2018 11:30:01: ***************************************************
03/02/2018 11:30:01: * YAME server START *
03/02/2018 11:30:01: ***************************************************
03/02/2018 11:30:01: Start accepting connections.
03/02/2018 11:37:18: Connected to Falcon
03/02/2018 11:37:18: Flight data extraction start.
03/02/2018 11:37:18: Texture data extraction start.
03/02/2018 11:37:18: New TEXTURE client connected
03/02/2018 11:37:18: Sending texture infos to all clients…
03/02/2018 11:37:18: done sending texture infos.
03/02/2018 11:38:45: Flight data extraction stop.
03/02/2018 11:38:45: Texture data extraction stop.
03/02/2018 11:38:45: Stop accepting connections.From Server:
Hook Log
03/02/2018 11:30:09: *************************************************
03/02/2018 11:30:09: * YAME64_d3d: InitInstance called *
03/02/2018 11:30:09: *************************************************
03/02/2018 11:30:11: Loaded original dll: C:\Windows\system32\d3d9.dll
03/02/2018 11:30:11: Direct3D9 created.
03/02/2018 11:36:53: Reset YAME D3DDevice
03/02/2018 11:37:18: Created render target
03/02/2018 11:37:18: Created offscreen surface
03/02/2018 11:37:18: StartMFDThread--------------------
03/02/2018 11:37:18: MFDThreadFunc…--------------------
03/02/2018 11:37:18: Texture size: 1200x1200 at 32 bpp
03/02/2018 11:37:18: Created file map
03/02/2018 11:37:18: Mapped file
03/02/2018 11:37:18: StartSendingData…
03/02/2018 11:38:31: Reset YAME D3DDevice
03/02/2018 11:38:45: YAME64_d3d: ExitInstance called.
03/02/2018 11:38:45: CloseAll-----------------------From Client:
Client Log
03/02/2018 11:27:25: ***************************************************
03/02/2018 11:27:25: * YAME client START *
03/02/2018 11:27:25: ***************************************************
03/02/2018 11:27:25: Data extraction: false
03/02/2018 11:27:25: Texture extraction: true
03/02/2018 11:27:25: Texture connecting to server.
03/02/2018 11:35:07: Texture extraction connected.
03/02/2018 11:36:33: Texture data extraction stop.
03/02/2018 11:38:45: Client::run ended.It seems that the extraction started and ended in few moments.
From what I see you have only textured gauges (like mfd or ded) and no flight instruments. Try to add a little flight gauge (like an ADI) and post yor results. -
Great… Thank you very much… i use 27" like you. the example of a 1920x1080 YAME window with a custom background. from YAME manuel (page 76) look fantistic…
This is the background image I use:
Then when I add YAME gauges it looks a bit like this:
-
Try it the other way round? i.e server on the networked machine and BMS machine as client and make sure to select get data from network on the networked machine.
I don’t have BMS installed on my networked machine. How will the server get info if there is no install?
-
This is the background image I use:
Then when I add YAME gauges it looks a bit like this:
Is OK for me to use your background image?
It looks much more real than any I could find.
Thanks. -
Sure, no problem
-
Sorry MailMan, please disregard my suggestion, after checking my install I realise I have offered incorrect advice - for some strange reason I’m thinking the server needs to be the remote machine, I know it doesn’t as I have YAME running on my network.
-
This is the background image I use:
Then when I add YAME gauges it looks a bit like this:
could you plz share your .xml layout also for the gauges also ?
-
Sorry MailMan, please disregard my suggestion, after checking my install I realise I have offered incorrect advice - for some strange reason I’m thinking the server needs to be the remote machine, I know it doesn’t as I have YAME running on my network.
No prob.
-
Hi guys, YAME is awesome!! which files are suggested for backup, in order to restore YAME windows & gauges in case of setting up Windows OS from the beggining?
thx!! -
Hi guys, YAME is awesome!! which files are suggested for backup, in order to restore YAME windows & gauges in case of setting up Windows OS from the beggining?
thx!!Just backup YAME64.xml in /conf folder and the layouts folder
-
Has anyone having had issues with YAME and the new Windows 10 fall creators update found a fix yet? I reset Windows completely but the update is now part of the installation and there is no way to get rid of it. I have not tried rolling my vidcard drivers back but will tonight. Does anyone have a specific Nvidia driver that works with the fall creators update and YAME?
MFDE is wearing on me.
Thanks,
-
Has anyone having had issues with YAME and the new Windows 10 fall creators update found a fix yet? I reset Windows completely but the update is now part of the installation and there is no way to get rid of it. I have not tried rolling my vidcard drivers back but will tonight. Does anyone have a specific Nvidia driver that works with the fall creators update and YAME?
MFDE is wearing on me.
Thanks,
Hi, I have the same problem, impossible to use YAME since the Windows update… I tried lots of things, but nothing works
-
Ok, I did some testing tonight with nvidia drivers but I don’t think they made much difference. What I did find is that if I used one of the YAME pits that are included some worked fine. The block 60 and one of the MLU’s worked just like normal. However, I noticed when I applied the gauges it didn’t creat a window mask for these pits, nor did it have to create the whole layout when I ran them in client mode.
Next I loaded the base block 52 with all analog layout from YAME. This one did create a mask both when applying guages and running it. Immediately upon running it my CPU usage shot to 70% like it has since the fall creators patch for Win10 came out.Now I don’t have the first clue what the difference is between YAME creating a mask and not creating one. I make extensive use of Ice’s fine work and only make positional and size changes. But for sure the problem lies with creating the mask since the fall creators update.
Any ideas? I really want my gauges back lol.
-
Hi, I have the same problem, impossible to use YAME since the Windows update… I tried lots of things, but nothing works
When you get a chance, can you load the Block 60 pit that comes with YAME and see if it works? If so, then creating window masks is what’s FUBAR now with the Win update.
-
that’s interesting. thanks for the reports i Will look into mask creation to see of there is something wrong. better it would be of you can send me your layout.
and just to Know, all of you reporting high cpu usage are using window mask?
and antialias in on? -
Yes to both questions for me. I’m using Ice’s most recent single monitor layout. Neither it nor the previous 1.2 work after the Win update.
I’m assuming I use window mask with Ice’s layout since I’ve not changed any of his settings.
-
could you plz share your .xml layout also for the gauges also ?
https://www.dropbox.com/s/n4wy0j7g65nvcwb/Faan-1screen.xml?dl=0