YAME64 suite
-
MIrage 2000? Do you not just extract the same stuff as you do with the F-16?
-
IIRC the values are different cuz 3dckpit files are different from F16 files
Same for the F18, that’s why a dedicated config is present in the conf/extraction.xml file -
If I remember correctly the mirage uses 512x512 texture size, so it is not possible to extract in the current version of YAME.
In the next version will work, but not using directx hook. -
YAME has nothing to do with 3dckpit files. There is a different config present in YAME so that they use different textures as background for stuff like the F-18, but that’s about it. The skin may look different for the F-18 MFD, but that’s just a skin…. the extraction stuff is the same because essentially, it’s the same MFD but just with different skins. Same thing for gauges, RWR, etc…
EDIT: Looks like I could be wrong…
-
If I remember correctly the mirage uses 512x512 texture size, so it is not possible to extract in the current version of YAME.
In the next version will work, but not using directx hook.What is 512x512 texture?
-
What is 512x512 texture?
It’s the size in pixels of the texture in shared memory. Default size is 600x600 (or 1200x1200 if you enable the doubleResolution in config file). Some planes use 256x256 (or 512x512) texture size. The current version of YAME is forced to use 600x600 (or 1200x1200) texture sizes.
-
Ah, I see… is this for everything in sharedmem for the M2000? Or just a few items? I didn’t expect there to be different textures for different aircraft.
-
Possible memory leak… I recently changed from windows 10 to windows 7. On windows 10 is was actually running pretty well, but in Windows 7,
I have a lot of problems with lag after running for a few minutes. I noticed in the Resource Monitor, that the YAME64.exe is
constantly increasing in memory footprint, even without running any active screen (the client is not started)…
After 30 minutes the memory usage is around 700MB and still going up… I think this might be related to the shader on the info page…
The framerate in the beginning is very high, now after 30 minutes it is 1 frame per 2 seconds. -
Strange, running win7 here and can fly missions of 2h+ without having issues.
Can you send some more info? Graphical card, drivers, settings, layout xml, yame64.xml etc? -
Hi,
Yes I have attached everything you need… The OS is a complete reinstall and no special settings have been made to graphics or anything else for that matter
-
I think you can ignore this. Apparently YAME64 was started in compatability mode…. Which is never a good idea… Removing that and everything is fine.
-
Why were you starting in compatibility mode in the first place?
-
Hey Gents.
I use YAME V1.1 in 3D Hook mode to extract the MFD’s to two external 8" screens. Sometimes the entire game freezes for 1-2 secs and the MFD’s blank shortly. This happens about 4 or 5 times until the crashes with Windows 10 announcing that an application has been blocked from accessing falconbms.exe
My troubleshooting so far:
- graphic driver update
- windows 10 update
- Use Falcon Display Extractor instead.-》 runs well and stable (despite fps penalty)
Can anyone of you help me to solve the problem?
-
Is it perhaps running in compatibility mode? If so, try disabling that.
Also worth a try, don’t use 3D hook but try the other way with RTTextracture set to 1 and see if it still happens.
Any firewall/Anti-virus application you have running? Try whitelisting yame exe in that. -
Is it perhaps running in compatibility mode? If so, try disabling that.
Also worth a try, don’t use 3D hook but try the other way with RTTextracture set to 1 and see if it still happens.
Any firewall/Anti-virus application you have running? Try whitelisting yame exe in that.I will give them all a shot.
I have the Windows Firewall and Kaspersky Anti Virus… maybe I have to dig into those also… -
Is it perhaps running in compatibility mode? If so, try disabling that.
Also worth a try, don’t use 3D hook but try the other way with RTTextracture set to 1 and see if it still happens.
Any firewall/Anti-virus application you have running? Try whitelisting yame exe in that.Do I have to enable “Texture Overlay” or “Send Texture to client” in the Hook-Tab, when using 3D Hook?
-
I am still getting constant crashes.
Initially I thought it was due to the AA, but my theory proved to be wrong.the extractions works OK for a random period of time(sometimes 5min, sometimes 25min), but then the client starts crashing.
If I restart the client (while keeping BMS and the YAME server running) the extraction starts working again. There is no need to restart the server.
Both W7x64
I have tried:
-opening all the 53000 and 53100 ports
-Switching off all the antivirus and software firewalls
-Reinstalling yame64 on both server and client PCs
-Reinstalling the prerequisites on client/server PCsI am using the hook extraction and both server and cliet PCs are connected via LAN cable to the main router.
This is the crash report
Problem signature: Problem Event Name: BEX64 Application Name: YAME64.exe Application Version: 0.0.0.0 Application Timestamp: 583eac64 Fault Module Name: StackHash_d370 Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 000007ff3a7600fa Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3082 Additional Information 1: d370 Additional Information 2: d37053bcba7a62e0971e0f91963ff1e7 Additional Information 3: a179 Additional Information 4: a179589ee5ce7cc73a7b96fe42330ee2 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
Problem signature: Problem Event Name: APPCRASH Application Name: YAME64.exe Application Version: 0.0.0.0 Application Timestamp: 583eac64 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.23864 Fault Module Timestamp: 595fa942 Exception Code: c0000005 Exception Offset: 00000000000185fd OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3082 Additional Information 1: 78e1 Additional Information 2: 78e1b10fbfc5fbbbc9cf32d5db3f2882 Additional Information 3: 1d7a Additional Information 4: 1d7ab1c83c47d8aab256e68db8766d16 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
Problem signature: Problem Event Name: BEX64 Application Name: YAME64.exe Application Version: 0.0.0.0 Application Timestamp: 583eac64 Fault Module Name: bdcam64.dll_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 57fb1d72 Exception Offset: 000007feee542bf6 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3082 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
Any idea/suggestion?
-
I am still getting constant crashes.
Initially I thought it was due to the AA, but my theory proved to be wrong.the extractions works OK for a random period of time(sometimes 5min, sometimes 25min), but then the client starts crashing.
If I restart the client (while keeping BMS and the YAME server running) the extraction starts working again. There is no need to restart the server.
Both W7x64
I have tried:
-opening all the 53000 and 53100 ports
-Switching off all the antivirus and software firewalls
-Reinstalling yame64 on both server and client PCs
-Reinstalling the prerequisites on client/server PCsI am using the hook extraction and both server and cliet PCs are connected via LAN cable to the main router.
This is the crash report
http://imagizer.imageshack.com/img922/2668/8rlOGz.pngProblem signature: Problem Event Name: BEX64 Application Name: YAME64.exe Application Version: 0.0.0.0 Application Timestamp: 583eac64 Fault Module Name: StackHash_d370 Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 000007ff3a7600fa Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3082 Additional Information 1: d370 Additional Information 2: d37053bcba7a62e0971e0f91963ff1e7 Additional Information 3: a179 Additional Information 4: a179589ee5ce7cc73a7b96fe42330ee2 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
http://imagizer.imageshack.com/img923/74/tW2a3p.png
Problem signature: Problem Event Name: APPCRASH Application Name: YAME64.exe Application Version: 0.0.0.0 Application Timestamp: 583eac64 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.23864 Fault Module Timestamp: 595fa942 Exception Code: c0000005 Exception Offset: 00000000000185fd OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3082 Additional Information 1: 78e1 Additional Information 2: 78e1b10fbfc5fbbbc9cf32d5db3f2882 Additional Information 3: 1d7a Additional Information 4: 1d7ab1c83c47d8aab256e68db8766d16 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
http://imagizer.imageshack.com/img924/7646/Y5Mh0w.png
Problem signature: Problem Event Name: BEX64 Application Name: YAME64.exe Application Version: 0.0.0.0 Application Timestamp: 583eac64 Fault Module Name: bdcam64.dll_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 57fb1d72 Exception Offset: 000007feee542bf6 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3082 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
Any idea/suggestion?
It shoull all be fixed in the next release. Just wait few weeks
-
It shoull all be fixed in the next release. Just wait few weeks
I WANT IT ALL, AND I WANT IT NOW!!!
:bdance:
-
3-4 Falcon weeks, my friend.