YAME64 suite
-
This is how it looks with an NVidia card
-
“Invalid attachment”, but I think it might look similar to this, right?
All the best,
Uwe
-
Or this! 4.34, then 4.35… (I did not add the bottom gauges yet on the right, but they work fine in 4.35).
-
it seems that 4.35 sets g_bExportRTTTextures = 0 as default, once I changed that to 1 everything worked.
-
What GPU are you on linknet? i’ve heard from Radeon users that YAME still works w/r to MFD extraction for them.
All the best, Uwe
-
it seems that 4.35 sets g_bExportRTTTextures = 0 as default, once I changed that to 1 everything worked.
Mine is set to “1” (was 0 as default as you mentioned) and Yame64 1.2.1 MFDs are still corrupted. Fact is I set it to 1 per the RTT extractor readme and RTT works fine… As you can see in my sig I use an Nvidia card.
-
What GPU are you on linknet? i’ve heard from Radeon users that YAME still works w/r to MFD extraction for them.
All the best, Uwe
It’s an NVIDIA something or other, sorry but I don’t have the details to hand.
-
any work around for yame with geforce cards for MFD,DED,PFL,RWR ect. RTT is a no go as it freezes for for me and gives me alt/tab issues? thanks in advance
-
Yep, there’s an internal beta of YAME2 available but it has the same issues with the MFDs as the “official” release.
All the best,
Uwe
Hi Hoover,
Any chance of obtaining a copy of this for testing purposes?
-
For BMS 4.35 :
- Yame64 doesn’t extract mfd’s, rwr, ded. All the other gauges work . ( BMS 4.33 is installed and 4.34) (My gpu: AMD RX5700 XT)
- Center Pedestal block60 doesn’t show the map on Mediterranean Theater.(Maps are already copied from Weapon_Delivery_Planner…\MAP to YAME64\gauges\cp60\maps)
- Which keys we use for the CPD ? (How do I assign them .)
-
For BMS 4.35 :
Yame64 doesn’t extract mfd’s, rwr, ded. All the other gauges work . ( BMS 4.33 is installed and 4.34)Same issue MFDE has. It seems the switch to DX11 gives issues regarding extractions, mostly to Nvidia users, some others report no issues.
Is already mentioned here: https://www.yame64.com/how-to/Which buttons on keyboard can i use for the CPD ?
There’s no 1 answer to this. It depends on the BMS keyfile you use.
-
Same issue MFDE has. It seems the switch to DX11 gives issues regarding extractions, mostly to Nvidia users, some others report no issues.
Is already mentioned here: https://www.yame64.com/how-to/There’s no 1 answer to this. It depends on the BMS keyfile you use.
no issues with MFDE on Nvidia apart of the freeze issue which is not related to to tool used but a bug in BMS shared memory thread safety. So any tool using F4TexSharedMemory might face that issue at the moment
-
so if in a future 4.35 update the extraction problem( that causes RTT freezing) is solved, does this mean that YAME MFD’s extraction will carry on normally?
or it’s DX11 related issue? -
YAME MFDs will not work after the freeze fix.
-
YAME MFDs will not work after the freeze fix.
What is changed? In my dev version of yame the extraction works well.
-
What is changed? In my dev version of yame the extraction works well.
even on 4.35? the MFD’s not working since the 4.35 release…all other gauges work fine
-
even on 4.35? the MFD’s not working since the 4.35 release…all other gauges work fine
Yes on 4.35, but on my yame version, not the public one
-
I think it’s DX11 related.
All the best,
Uwe
-
MFD extraction (basically everything texture-related) won’t work for me on the current beta that I’m using (2.0.0.43 I believe) when using BMS 4.35.
All the best & a happy new year to all!
Uwe
-
I wouldn’t say that this is DX11 related. Prior to 4.35 BMS was able to write the texture in either 600x600 or 1200x1200. With 4.35 it’s fixed to 1200x1200.
Can’t speak for Yame as I have no access to the code. But for MFDE there are 2 version of 0.6.3 the “older” one sets the resolution in the program code by reading the rttdoubleresolution parameter (Not present In 4.35) whereas newer version read the texture homage size from the memory data.
So older MFDE showed the same weired image as no doubleresolution in config defaulted back to 0 hence assuming 600x600 whereas BMS writes 1200x1200Gesendet von meinem SM-G930F mit Tapatalk