I can’t seem to get F4Radar to work anymore.
Using BMS 4.37.3.2 on KTO and F4R v0.49, neither in 2D (with clock running and slotted in a non-airborne flight) nor in 3D (on the ground) does F4Radar show any airspace info. Bottom-left always reads “BMS Status: off”, no frequency/packages lists are displayed, no bullseye, no radar tracks.
Posts made by RUSHER0600
-
RE: [F4RADAR] Lightweight standalone radar application
-
RE: ITO 1.07.0v Bugs
Problem with ITO Red Line campaign. At day 1 about 7:30 game always crashes.
@vAiCon ?
-
RE: ITO 1.07.0v Bugs
@QuantumDream said in ITO 1.07.0v Bugs:
I’ve got a problem. Campaign crashes every time. In log folder there is text file “ErrorsInCampain.txt”.
~FlightClass 1334th Fighter Flight Squad 201st Fighter Squadron Pilot 0 - Col. Arad still in use!ITO or ITO80s?
Which campaign?
Does opening that campaign with MC and fixing/deleting the squadron resolve the issue? -
RE: ITO 1.07.0v Bugs
@SammySkycrafts Noticed that too recently, I believe the best solution would be an MC update.
-
RE: ITO 1.07.0v Bugs
Just to add, I also got wind speeds displayed like this today, aswell as aircraft callsigns (For instance NICKEL11 would be NICKEL 01-Jan
Sounds more like a code than theater issue to me, might be worth reproducing it in KTO and then reporting it using the official bugtracker
The A-6E has no access to the inbuilt TGP, and no external one can be mounted, therefore no laser based weapons can be guided.
I guess that should be an easy fix, are you referring to ITO or 80s though?
Chaff / flare are also loaded and can be used by AI but not by a human. This affects some other aircraft too.
Odd, you mean the CMs are loaded as per the CMDS indicators but CMS-Up / Slapswitch don’t trigger any CM release? Which aircraft are affected?
-
RE: ITO 1.07.0v Bugs
@unkindled Gotcha, no problem. I guess it’s the same old bug that happens sometimes in the ATC brain, unfortunately hard to repro.
-
RE: ITO 1.07.0v Bugs
@Bloodhound161 Thanks for reporting that, fixed in the next release
@unkindled Did it happen again and were you able to reproduce the CTD upon requesting taxi back to ramp in 80s?
-
RE: Israel Theater of Operations for BMS 4.37
@CloudWallace1981 Glad you like it, the inclusion of the Iron Eagle OST goes back to UOAF’s first 80s mod of the ITO theater for BMS 4.33, for tradition’s sake it has been maintained that way.
Maverick TERs not being available on Netz jets is in fact an oversight, will be fixed for v1.07.3
-
RE: ITO 1.07.0v Bugs
@unkindled Interesting… not sure what the cause could be in the theater, since afaik HARM tables are only set in the CALLSIGN.ini.
Does the issue appear in a specific campaign or TE, or when departing from a specific airbase? -
RE: Israel Theater of Operations for BMS 4.36
@depapier unfortunately the BMS campaign engine sometimes has issues fragging HVAAs like AWACS/JSTARS on the small Israeli territory, campaigns with a short conflict border like PfG seem to be more affected. It could also be caused by enemy territory being too close to the AWACS airbases, as a workaround you could try using Mission Commander to make Palestine neutral in the war, or give all its territory to Israel. I’ll do some experiments myself and try to make PfG work better out of the box for v1.06.3.
-
RE: Supporting native Tacview in BMS 4.36.1
How to apply the solution to your theater:
As explained previously, to write the coordinates in the .acmi correctly, BMS code needs to know the N/S lat and W/E lon of the 4 theater “sides”.
It was decided to let BMS read those values out of anAdd-On [theatername]\Terrdata\[theatername]\terrain\Theater.map
file, since it’s a binary file, you will need a hex editor (I used HxD) to add the values.- open the Tacview file holding theater data, located in
C:\Programs\Tacview\Data\Xml\Data-Falcon4Theaters.xml
, this will provide a quick reference for theater border coordinates that should already provide a proper alignment in Tacview (for most 64 tile theaters), for this example we’ll use the ITO values;
<West>30</West> <East>40</East> <South>25</South> <North>35</North>
-
open your
Theater.map
with a hex editor like HxD (might be better to make a backup of the file first), make sure you select “little endian” as Byte Order below the Data Inspector;
-
In HxD, “Edit>Insert Bytes”, set bytecount to 4 to insert 32 new bits, they will be highlighted in red. Mark them and use the Data Inspector to overwrite them with a new float (32 bit) value “20000”, this is some “max altitude” metadata that needs to be present;
-
Insert 8 new bytes (64 bits) like in step 3, select them and use the Data Inspector to overwrite them with a new 64 bit float, repeat this step a total of 4 times to write the WEST, EAST, SOUTH, NORTH border coordinates in order;
-
In total you should have added: “20000” as a 32bit (4 hex-value pairs or bytes) float and the WEST, EAST, SOUTH, NORTH border coordinates as 4 consecutive 64bit (8 hex-value pairs or bytes) floats, all totaling to 36 new bytes written since you started editing. Save the file and check alignment by creating an acmi using the new native export;
- open the Tacview file holding theater data, located in
-
RE: Israel Theater Of Operations for BMS 4.35
@df1979 most browsers seem to have issues opening that web-page, might have to do with the server’s .htaccess file.
Right clicking the link and selecting “save link as file” works though. -
RE: Israel Theater of Operations for BMS 4.36
@ccc1tw thanks for pointing that out, I completely forgot to add that important step to the README
The shared .7z has now been updated to include a revised README.txt (the download link is unchanged).
-
RE: RUSHER's web-tool collection
@ccc1tw I’m guessing that they are “empty” slots that will hold future mission types, though I’m not sure why they had to be defined at all in that case
-
RE: RUSHER's web-tool collection
ACData MissionType Selector has been updated to handle 4.36’s additional mission types.
-
RE: RWR <M> Fix for 4.35.3
<p>@airtex2019 Unfortunately this wasn’t made clear enough. I’m the author and first shared the source code on the UOAF discord (<a href=“https://discord.gg/U7UykYX” target=“_blank”>invite</a> and <a href=“https://discord.com/channels/582602200619024406/615631373968998435/908706086377357352” target=“_blank”>specific message</a> link), where I first noticed discussion around the issue. Later I compiled the same code into the .exe that was distributed to everyone. I also attached the source code in <a href=“https://forum.falcon-bms.com/post/334192” target=“_blank”>this reply</a> of mine in this very thread, though I admit I probably should have asked depapier to link it in his first post for best visibility.<br />In any case, as @airtex2019 correctly pointed out, my code just grabs the BMS path from the registry, finds the FALCON4_RCD.XML within every theater and only edits the 3 seeker entries mentioned by the hotfix notice. I didn’t make the script pause because it is usually bad practice when coding CLI applications, but if you open a CMD shell and run the .exe or .py from there you’ll see how it lists every file that it modified.<br />Python is one of the best languages available to quickly write short but powerful code like this, batch files are pretty limited when more complex logic is required. The python interpreter is also trivial to install and only going to become more useful in the future, even on non-coder PCs. For those who trust my word, there’s always the .exe.<br />Next time I’ll make sure to publish both exe and source code together in a more comprehensive way, along with an exe hash for good measure, cheers!</p>
-
RE: RWR <M> Fix for 4.35.3
@khronik The issue is that it’s not just a single xml file, it’s one for every theater you installed or plan to install (if it hasn’t been updated yet).
FYI, it’s also not reverse engineering, I simply shared the source code that I compiled the auto-patcher from. If you can’t execute the .exe, installing the python interpreter and executing the source code will likely still take less time and annoying repetitive labor than manually editing everything. -
RE: RWR <M> Fix for 4.35.3
@cag Which version of Windows are you running? From what I’m reading that specific DLL was first included in windows 8.
You could try out fix suggestions like this one from the microsoft helpdesk.Alternatively, install the Python interpreter and execute my source code directly, instead of using the compiled .exe.