@Revientor Thank you very much. Now I am understanding all situation in a better way.
Sorry for my strange questions, but I am an old pit builder, and I like Falcon BMS and I like to know what there is under the hood.
Cheers
Mauro
@Revientor Thank you very much. Now I am understanding all situation in a better way.
Sorry for my strange questions, but I am an old pit builder, and I like Falcon BMS and I like to know what there is under the hood.
Cheers
Mauro
Thank you very much, @SemlerPDX .
Your info on Menu.dat is very interesting to me.
I am trying to understand if when I plan a my mission in single player, it is possible to group more useful radio calls in a single customized menu page.
Ciao,
Mauro
Hello pal.
I respond myself because only now I understood @lcriscola replay: those callback are for PitBuilder, them permit to choose a defined replay between those shown on display.
RadioMenuOne means the replay associated to number “1” and so on.
Than again @lcriscola
Ciao,
Mauro
Thanks @lcriscola, but :
Hello,
someone knows meaning and use of nine callbacks
RadioMenuOne
…
…
RadioMenuNine
that are in key file but without key assigned them? Which is their use?
Thank You in advance,
Mauro
Ok, following your advice I am creating an account on Git, and soon as possible I’ll share my little program.
I think is important to understand that my big problem was the little but costant movement of Radar ( or HSD ) cursor towards lateral sides, thas united with cursor bumping feature, behaved that in a little time the radar or hsd range was at maximum. I cannot solve this problem using standard bms parameters, so I introduced a little hysteresis that seems to solve this annoying effect.
Ciao.
Hallo BMS users.
I am using a Warthog TM Joy and Throttle, and have a lot of problems using the cheap radar joy on throttle, also using the new parameters added in BMS Config files.
So I developed a different solution using Vjoy and a little console program that I wrote. My little console program, reads raw data from TM Throttle Joy, applies on them a different calibration law to make them more stable, and send them to Falcon BMS throught Vjoy device.
I am usin this simple solution from 4.36 and to me it seems to work fine. If anyone is interested, let me know that and I can send you my little program and more infos.
Ciao to you all,
Mauro
Uwe, I noted that 1200x4=4800 it is not multiple integer of 256, instead adding 64 to 4800 we obtain 4864 that is multiple integer of 256: 4864/256 = 19…maybe it could be a simple misalignment problem handled in a different way from nvidia or amd drivers.
Ciao,
Mauro
Hi giannis,
I opened a similar thread in the “Technical Support” section of forum with the hope that developers answer it. Maybe it should useful if also you post your question in that thread.
I do not know if my solution can work for you: to extract textures from shared memory I used a my self made software, so i can, in simple way, apply the trick that I explain…I do not figure how you apply it using a third part software.
Let me know if also you use a your software and like to know the algorithm that I apply: in this case I’ll be very happy to explain it to you, but if you uses a third part sw, only hope is in developers’s answer.
Situation is very weird, because I know people that use Yame, or other extraction tool, without troubles; so I do not understand the situation: maybe also some different setting in Falcon configuration affects the way of working of shared mem.
Let me know if you like more info.
Mauro
Strange hoover, if I click on the Attachment it opens their…maybe because they are on my pc. They are only two capture ( .png file ) made with the windows10 native tool.
These are gdrive’s links
https://drive.google.com/file/d/1KDXQG2v8xqc7K4FMd02kFR8q4xKn9zHN/view?usp=sharing
https://drive.google.com/file/d/1Fy9YZdjVs_GN2HyNi_CspxfKXMDmxc8P/view?usp=sharing
Mauro
Hallo all,
it seems me that textures in shared memory are not 1200x1200 pixels, but 1216x1200.
I have a little app that get textures in shared memory and saves them in a raw file. The app works fine in 4.34 ( with double RTT enabled ) , instead it works in a weird way with 4.35. I solved it discarded 16 pixels at the end of each line, like if textured was stored in 1216x1200 pixels format.
Ciao,
mauro
Tanks oakdesign. I see that BMS 4.35 export texture RTT 1200x1200 way.
Now I have another strange thing:
Using a stand alone windows program to show raw bit image that I saved, I see a strange thing: to see a good image i must declare that raw texture has width = 1216 point; if I declare 1200 it again shos strange weird image. My simple app only get a pointer to texture shared memory, adds 128 bytes to jump the header, and than copy the texture data only stripping the Alpha byte, changing from 32 to 24 bit and saving it in a file.
I remarks that it works fine with 4.34 but with 4.35 it need to handle bitmap like it was 1216x1200 pixel.
I attach two image of tha same file, using 1200x1200 and 1216x1200.
Thankyou in advance,
mauro
Sorry oakdesign, maybe I make some mistake :shock: but, using BMSFlightData.exe tools, it seems me that BMS 4.35 writes texture only in 600x600 mode, instead BMS 4.34 in 600x600 and 1200x1200 according setting into Falcon BMS.cfg .
I am using Windows XP SP3 to test YAME64 32 bit Client.
Regards
Hi Roccio,
no idea about my problem? Someone uses Yame64 32bit Client on a WinXP S.O.?
Thank You in advance
Hi Roccio,
I install and run same YAME32 on a Windows7-64 bit and it works fine.
But when I try to do the same on WindowsXP, I install YAME32 successly, but then it doesn’t run. This is the error. The virtual machine runs on the same Win7 pc.
Bye
Thank for your answer People, but obviously my english in not good: I’ll try to explain it again:
The previous version of YAME ( 64 bit server side, and 32 bit client side ) runs fine; if I try the same configuration with last YAME release, when I starts the client side have the error “this is not a WIN32 application” .
But sure I am doing some type of error that I don’t understand…:(
In each case my congratulations, YAME SUITE is a great work .
Hi Roccio,
Falcon BMS runs on win10 64 bit, and on this pc also runs YAME 64 Server. On an old netbook Asus eeepc900 with win XP SP3 runs YAME32 like client. The two pc are connected using LAN. previous version of YAME runs very well, but the last version does not run: when I start that, winxp says me that it is not a win32 application.
Best Regards
Hi Roccio,
I am trying to use YAME32 Client on Windows XP, but It does not work: do you have advices?
Thank You in advance.
Mauro