4.35 MFD font impossible to read at 'normal' zoom levels.
-
Download this Rar file https://drive.google.com/file/d/1DEVjlNI1Ez2iP6cTXZv1QbLWycI2_LMC/view?usp=sharing , decompress the two files in it and paste them in this directory (C:\Falcon BMS 4.35\Data\Art\CkptArt\3dFont)
At the end in the above directory things may look like this:
https://i.ibb.co/ChRj0VZ/mfd-font.png
In the red box there are the two files that will change. Pay attention to the date of modification(green box). At the yellow boxes the date need to be as shown in order to have the mixed fonts.
Note that if you have an extra theatre except KOREA you need to replace Korea and the third theatre’s files(respective 4.34 theatre) in order to see properly the mixed font
hmm that is not working for me… i even replaced the whole “3dFont” folder from .34 into .35 …just to see what that does (same files) … nada… still too small (bulls-eye cirlce and numbers … and locked target info etc in fcr
-
@A.S:
hmm that is not working for me… i even replaced the whole “3dFont” folder from .34 into .35 …just to see what that does (same files) … nada… still too small (bulls-eye cirlce and numbers … and locked target info etc in fcr
If you are using another theatre than KOREA you need to replace files in KOREA and the other theatre too.
Take the respective files from KOREA 4.34 to the KOREA 4.35 and the other theatre files from 4.34 to the respective 4.35.
In conclusion you need to have 4.34 files for korea and for the other theatre in order to put them in the respective folders of 4.35. Try this and let us know!
-
i just tried on default korea
-
This is ( https://drive.google.com/file/d/1TWzbP3Ypgcuh5F_6MtuW39fPAaXlCc4r/view?usp=sharing ) my content of this directory (C:\Falcon BMS 4.35\Data\Art\CkptArt\3dFont). Try it out
-
This is ( https://drive.google.com/file/d/1TWzbP3Ypgcuh5F_6MtuW39fPAaXlCc4r/view?usp=sharing ) my content of this directory (C:\Falcon BMS 4.35\Data\Art\CkptArt\3dFont). Try it out
same not working
look…
green i made bigger (myself)
red! is what i need bigger (as it was in .34)
no idea why they changed it… dont break what is right …
-
Really i can not understand what is going on here. All the fonts are really odd in this picture.
Try to put the original files again and confirm that everything is ok. Maybe another member here can confirm that the files that i gave are ok. In my squadron every member is ok with this change.
-
only replacing mfd_smaller_font_d.gif and mfd_smaller_font_d.rct will work.
The theater has to point their own Ckptart dir in TDF file or should be placed into the default KTO folder. -
I fixed it differently… sometimes easy solution is best solution
I just used the
- mfd_font_d.gif
and
- mfd_font_d.rct
files
and renamed them to (as a mod)
- mfd_smaller_font_d.gif
and
- mfd_smaller_ ont_d.rct
Now everthing is very read-able. The rest are “edits” in the 3dckpit.dat files.
Note: i posted the file (mod) in BFM/ACM BAR discord https://discord.gg/kuYBPMJ … and the radar blip (contact) size and HSD symbol size you can adjust in configuration - as usual.
-
Thanks alot A.S. Could this be discussed with BMS team for inclusion in 4.35u1? MFD font readability is an issue for quite a few folks up here.
-
Just a heads up everyone.
According to the BMS Bug Tracker this issue has been fixed internally by BadBoy for U1. Not sure exactly how but I’m excited to see all the fixes for U1.
The BMS team have quietly but quickly smashing all the bugs that have made .35 a little tricky in certain circumstances.
-
-
Good news it would be fixed in U1.
BTW I could find out what each lines of .RCT file means<id><x><y><width><length><spacing><unknown></unknown></spacing></length></width></y></x></id>
-
@DUSTOFF17:
Just a heads up everyone.
According to the BMS Bug Tracker this issue has been fixed internally by BadBoy for U1. Not sure exactly how but I’m excited to see all the fixes for U1.
The BMS team have quietly but quickly smashing all the bugs that have made .35 a little tricky in certain circumstances.
Mav-jp (code) and MikeCZ (data) fixed the issue. I just committed the fixed font files in the svn branch.
-
@A.S:
I fixed it differently… sometimes easy solution is best solution
https://i.imgur.com/59d0DB1.png https://i.imgur.com/BHZKsqw.png
I just used the
- mfd_font_d.gif
and
- mfd_font_d.rct
files
and renamed them to (as a mod)
- mfd_smaller_font_d.gif
and
- mfd_smaller_ ont_d.rct
Now everthing is very read-able. The rest are “edits” in the 3dckpit.dat files.
Note: i posted the file (mod) in BFM/ACM BAR discord https://discord.gg/kuYBPMJ … and the radar blip (contact) size and HSD symbol size you can adjust in configuration - as usual.
“sometimes easy solution is best solution :)”
No sometimes the easy solution is just the easy solution …
now your bullseye circle is not big enough and your BE are out of place compared to the real
Have a look at your IFF contacts return , i bet your IFF boxes / circles are now out of place…
anyway …
we always have to jungle between realism and gameplay (readibility here)
i hope U1 will bring a better compromise for small fonts and MFDs
-
fly more what you build ……
-
@A.S:
fly more what you build ……
thank you for the advice , much appreciated
what about :
" build more than you fly ?" so i can fly myself ?
because i am not sure to have the good seat in this story at the end … maybe you forgot WHY we are doing this …
no need to answer anyway, welcome to my ignore list
-
i feel your pain… working so hard to “build” does not leave much time to fly …i was there too… but like in formula 1… driver needs to speak with engineers (a lot) to make best car - or be both ( like test pilots are ). no reason to “ignore”, your emotions are not of interest in your own goals (best possible result).
but if you want to hear why i said this… HOW can you work so hard and much… and then in matchplay you lose sound after pilot dies ? ONLY possible…if none of you ever flew in matchplay to notice it, correct? dont be offended… only truth. truth is good for all.
-
Jp: as we already discussed, let’s supress DF module, let ppl create TE they can use it the same.
So it will be one less thing painful to maintain, less to Btest, less complains when it don’t work as they would like.Win / win.
-
Jp: as we already discussed, let’s supress DF module, let ppl create TE they can use it the same.
So it will be one less thing painful to maintain, less to Btest, less complains when it don’t work as they would like.Win / win.
I am glad you did not become a doctor Dee-Jay. You would rip out all my slightly failing organs in no time
Cheers Obi1
-
I am glad you did not become a doctor Dee-Jay. You would rip out all my slightly failing organs in no time
Doctors do this every days with appendix. Instant Action and DF modules are rather pointless and requires special cases for Dev in parallel of regular TE/CAM. Instant action is not supported anymore (in case of issue it won’t be fixed and is kept alive because is work (so far) and can be practical sometimes for some Btest. DF modules, as discussed, is broken. So … Considering the effort required to maintain that shit, let simply remove it and let pll create they DF session in TE module. It works, and will transfer the effort from Dev to user, so Jp can fly a bit more, AS will not cry for bug in DF, I don’t have to care about special CTs for DF module which requires extra attentions … etc … everyone is happy.