-
should not be too hard to code. in the end all it changes is the ivc.ini file. though i’m not a coder but i can’t imagine it being to hard to change values in a file. i could code something in qbasic with a simple interface to do so so doing so with a proper GUI shouldn’t be to difficult.
i have no idea wether qbasic is even runable still in a windows enviroment since it moved away from being a dos based OS
Wouldn’t be hard to do in any language - a quick 10 minute job in VS is probably all you need to get a rough functioning program, the hard part is getting a “good” list of what each option does and ALL the possible options (Such as the external comms options that have several available inputs but no list of all of them and what each actually does)
-
“I was inquiring more about the remoteness of the possibility of modding it (for falcon purposes)”
is it broken ??? then don’t fix it ;0)
-
“I was inquiring more about the remoteness of the possibility of modding it (for falcon purposes)”
is it broken ??? then don’t fix it ;0)
Silly rabbit…tricks are for kids-- there were an awful lot of people who said F4 original was great and needed no fixing–that attitude we wouldn’t be here would we?
But more important to your question: Depends on who you ask…
-
so what is wrong with it ? being a kid its hard to see …
-
so what is wrong with it ? being a kid its hard to see …
There are a lot of people who don’t like the way the distancing is implemented, specifically the 2D/3D inter-communications (Particularly the GCI crowd out there). Most F16s out there, and all the other stuff flying in the theaters, has had SATCOM capabilities for some time so AWACS-Jet or GCI (Read 2D)-Jet comms should not be affected by the distancing or degradation. Settings are virtually undocumented. Range is not quite right the way it degrades between players who are both in 3D. Modern radios (Like the 210) have much better squelch and tone control, as well as better amps and some antenna trickery so you don’t get nearly as much gradual degradation from range.
None of that he would be able to fix without reverse engineering it…but you asked.
It’s hard to say one way or another because he didn’t say WHAT he wanted to mod.
-
There are a lot of people who don’t like the way the distancing is implemented, specifically the 2D/3D inter-communications (Particularly the GCI crowd out there). Most F16s out there, and all the other stuff flying in the theaters, has had SATCOM capabilities for some time so AWACS-Jet or GCI (Read 2D)-Jet comms should not be affected by the distancing or degradation. Settings are virtually undocumented. Range is not quite right the way it degrades between players who are both in 3D. Modern radios (Like the 210) have much better squelch and tone control, as well as better amps and some antenna trickery so you don’t get nearly as much gradual degradation from range.
None of that he would be able to fix without reverse engineering it…but you asked.
It’s hard to say one way or another because he didn’t say WHAT he wanted to mod.
this can be fixed by a simple tweak in the ivc.ini which can be located here “Falcon BMS 4.33 U1\Bin\x86\IVC”
# See chapter 14.5 of the BMS manual for detailed explanation of available options. # File to be saved in //localinstall/bin/x86/IVC/ #duplex = 0 #server = XXX.XXX.XXX.XXX #connect = 0 #nickname = Callsign #port = xxxx #key-hook = 0 # the line underneath this one activates havequick, it's an audible gimmick for UHF quick = 1 #word = password #capture = sound_device #nofx = 0 #playback = sound_device #tone = #loudness = 0 #fuzz = 0 #hum-level = 0 #hiss-level = 0 #toneVol = 0 #uhf = 307300 #vhf = 1234 #uhfVol = 0 #vhfVol = 0 #the line underneath this line affects 2d comms to the 3d, with this setting set to all there will be no distance propogation from 2d to 3d so 3d can hear it all over the map. outsiders = all #log = 0 #minimize = 0 #force-local = 0 selfblock = 1
the documentation for the ivc.ini can be found in “bms-manual.pdf” which is located in “Falcon BMS 4.33 U1\Docs\Falcon BMS Manuals” from page 251 to 274.
it’s pretty well documented though not all features are operable from what i could test, specificly squelch and distortion and such, but i’m hoping this is fixed in the next update. but there’s a decent chance that i tested this wrong.you are correct about distance propogation. real life is easily 200nm from what i’ve heard from airline pilots which use the same uhf radio instead of the 120nm which is the max distance in bms. which honestly is too little. but then again theatre’s arent that large so maybe artistic freedom?
i hope you apreciate the effort i went through to look up the specific locations and pages of where you can find what you want. so i now say to you with the best of meanings and intentions to RTM :rolleyes:
-
this can be fixed by a simple tweak in the ivc.ini which can be located here “Falcon BMS 4.33 U1\Bin\x86\IVC”
# See chapter 14.5 of the BMS manual for detailed explanation of available options. # File to be saved in //localinstall/bin/x86/IVC/ #duplex = 0 #server = XXX.XXX.XXX.XXX #connect = 0 #nickname = Callsign #port = xxxx #key-hook = 0 # the line underneath this one activates havequick, it's an audible gimmick for UHF quick = 1 #word = password #capture = sound_device #nofx = 0 #playback = sound_device #tone = #loudness = 0 #fuzz = 0 #hum-level = 0 #hiss-level = 0 #toneVol = 0 #uhf = 307300 #vhf = 1234 #uhfVol = 0 #vhfVol = 0 #the line underneath this line affects 2d comms to the 3d, with this setting set to all there will be no distance propogation from 2d to 3d so 3d can hear it all over the map. outsiders = all #log = 0 #minimize = 0 #force-local = 0 selfblock = 1
the documentation for the ivc.ini can be found in “bms-manual.pdf” which is located in “Falcon BMS 4.33 U1\Docs\Falcon BMS Manuals” from page 251 to 274.
it’s pretty well documented though not all features are operable from what i could test, specificly squelch and distortion and such, but i’m hoping this is fixed in the next update. but there’s a decent chance that i tested this wrong.you are correct about distance propogation. real life is easily 200nm from what i’ve heard from airline pilots which use the same uhf radio instead of the 120nm which is the max distance in bms. which honestly is too little. but then again theatre’s arent that large so maybe artistic freedom?
i hope you apreciate the effort i went through to look up the specific locations and pages of where you can find what you want. so i now say to you with the best of meanings and intentions to RTM :rolleyes:
That has to be done for EVERYONE in the theater in order for it to work, that’s not a solution it’s a cumbersome un-enforceable workaround. I’m well-versed on the manual and nowhere does it provide a comprehensive list of all the different options which are available and the differences in them, but thank you for the suggestion and the time it took to Ctrl-F.
-
so what if everyone has to do it… according to you EVERYONE had that problem. it’s not a multiplayer critical component so you can leave the settings as is no matter where you fly. and i would call pages 252-265 pretty damn comprehensive, every setting has a definition and explenation with lower and upper ranges for the variables.
-
" he didn’t say WHAT he wanted to mod. " - what’s all this then - your wish list?
-
" he didn’t say WHAT he wanted to mod. " - what’s all this then - your wish list?
Not at all. You asked a question and I answered it. All of those comments and/or arguments can be found through simple searches on the forums. For all we know he just wanted to simply supply a different skin to the UI, or change the way it acted in some way that has nothing to do with the underlying SDK or licensed implementation through TS.
-
so what if everyone has to do it… according to you EVERYONE had that problem. it’s not a multiplayer critical component so you can leave the settings as is no matter where you fly. and i would call pages 252-265 pretty damn comprehensive, every setting has a definition and explenation with lower and upper ranges for the variables.
I don’t have a manual to look at right this very minute, but the last time I checked, when 6-8 of us spent 20+ hours trying to find a better way to make it work as a whole for an entire MP community and not just for the individual who changes their settings, there were several options not listed in the manual which were valid for some of the config settings, specifically the one in question here. We found this out through the forums here when certain people associated with the program recommended we try some other options that were not listed in the manual (Hmm options not listed in the manual? I guess our definition of comprehensive is different)
If only one of us had your wicked awesome PDF searching skills and thought just once to look in the manual maybe a year later nobody would still be having this conversation… oh wait.
-
sterile
List these options which are apparently not in the manual, and if they work, maybe they can be added.
But as long as we don’t see them so we can test them and assess them compared to what the manual says, then it’s all urban legendBe constructive rather than sterile.
If the manuals are uncomprehensive (which is a very abstract statement and depends on many factors) it’s up to you to help to make them better
Sitting and criticising freely won’t make them any better, I can tell you that -
@Red:
sterile
List these options which are apparently not in the manual, and if they work, maybe they can be added.
But as long as we don’t see them so we can test them and assess them compared to what the manual says, then it’s all urban legendBe constructive rather than sterile.
If the manuals are uncomprehensive (which is a very abstract statement and depends on many factors) it’s up to you to help to make them better
Sitting and criticising freely won’t make them any better, I can tell you thatIt wasn’t meant as a criticism to you or your work Red Dog. And for most people it isn’t an issue, particularly since there isn’t a lot of mass-pvp out there. Squadrons and VFWs can do a little better at getting everyone to make changes to files like that, my point was that we HAD read the manual in response to his facetious RTM comment, and making that change does not always yield the expected result, nor do most people understand it only effects your local client, and has no bearing on other users in the 3D.