@eddropper Many thanks to all who worked on this theater!
Posts made by Gunz_ProSkies
-
RE: Afghanistan 128 Theater OFM 2.4.2 for 4.37u3
-
RE: BMS SteamVR supersampling (Reverb G2)
@I-Hawk
g_fVRResolution can also be set in the “falcon bms.cfg” from the “VR Settings” section at the bottom of the file. It is set to 1.0 by default. -
RE: Error after updating Alt Launcehr
@Jumpstart5179 said in Error after updating Alt Launcehr:
Hey everyone. I got an error after updating the Alt Launcher. The “Flight Arrow” in the key file was the culprit. I fixed it by adding the quote for the command. This is what caused the issue I had:
FlightArrow -1 0 0XFFFFFFFF 0 0 0 1 "FLIGHT
Corrected it to:
FlightArrow -1 0 0XFFFFFFFF 0 0 0 1 “FLIGHT: Go Arrow”This resolved the issue for me.
I encountered the same error message. The steps I took that resolved the issue was (1) using @MaxWaldorf post Alternative launcher for 4.37.3 to update my launcher. However, I still received the same error after this step. I then (2) opened the “BMS - Full.key” and copied the line from FlightArrow -1 0 0XFFFFFFFF 0 0 0 1 “FLIGHT: Go Arrowhead” and all the text until the end of the file. I then paste that content into “BMS - Auto.key” to replace the “FlightArrow” line in my “BMS - Auto.key” file which I found was incomplete and was where the error message was referring. After saving the updated “BMS - Auto.key” file and then running the AL again, it worked. Hope that helps anyone who has the same issue.
-
RE: Need help getting BMS to run in VR
@Tempest7MR said in Need help getting BMS to run in VR:
I cannot get BMS to recognize my VR configuration.
I’m running Steam VR with a Varjo headset. Open VR is enabled.
The install folder is in the same path as both falcon and BMS, and it simply will not run in VR.
There’s no option on the launcher to select VR. I’ve tried changing the config file to “force” it to run. Any help would be appreciated, thanks.
Just to confirm, you performed the steps in the “BMS-VR-Guide.pdf” as well? (\Falcon BMS 4.37\Docs\01 Input Devices\04 VR Guide) There should be an “Enable” option visible and next to “Virtual Reality:” on the Alternative Launcher when Steam VR is being recognized. Since “There’s no option on the launcher to select VR.” it seems to be an issue with your Steam VR setup and BMS not recognizing it. According to the “BMS-VR-Guide.pdf”: “Note: If there is no Steam VR installed or not recognized by BMS, the VR option in the BMS launcher is not visible.”
-
RE: problem with the last update
@jack333 said in problem with the last update:
hello everyone, my problem is that after the update when I try to switch to theater in Israel I get this ad. This does not happen to me neither with Korea nor with the Balkans, in case anyone notices, I have the original Falcon 4 disk installed and also before the update I had no problems. The update to which I refer is to the one of the theater of israel with its hotfix. Greetings and thank you
I have experienced a similar error prompt (Please insert the Falcon 4.0 CD), but it was not related to a problem with the Israel theater or any of the BMS theaters. After an update, my issue was eventually traced to a “Config.exe” issue. This may help solve your problem. I recommend opening your “Config.exe” either by clicking the file directly in your “…\Falcon BMS 4.37” root directory or by clicking “Config” from the Alternative Launcher screen. After the “F4Patch - Falcon BMS - 4.37” window opens, check the path where the “Executable:” is pointing. It should be “…\Falcon BMS 4.37\Launcher.exe” and not pointing to your “…\MicroProse\Falcon4” folder, which was the reason I was getting the error prompt. If the path does not point to “…\Falcon BMS 4.37\Launcher.exe” (presuming you are using the Alternative Launcher) then use the “Browse…” button to update the path and then click “Apply Changes”. Hope that helps.
-
RE: Getting sound but no image in ReverbG2..
Just to confirm, you also reconfigured your Windows Mixed Reality for SteamVR settings after your reinstall (+ set room boundary using the seated and standing option), and the Windows Mixed Reality Portal is running in the background (which should also will trigger SteamVR if G2 is hibernating) when you launch BMS?
-
RE: Head translation in VR not working properly (FIXED thanks to community help)
@GhastlyTT has the correct solution. I had the same issue using Reverb G2, but re-calibrating using the seated option solved that issue for me.
-
RE: Allied aircraft do not respond to IFF interrogation
@RingoSurf
Another item during your ramp start you can check is to ensure you are coupling your SCAN/LOS (two separate pages) interrogator code to/from your transponder codes via the DED’s “INTG” page (active since 4.34). Reference T.O. BMS1F-16CM-1 BMS 4.35 Change 3.00, 1.3.16.10 INTG page (RCL).If not, you may observe random times when you are not receiving IFF replies (because the change criteria has occurred). Since your IFF codes will change every hour (reference your “Iff” schedule from your package briefing), if you are airborne when the next IFF schedule change does occur and your IFF interrogator was/is NOT coupled to the change criteria then your interrogator will continue to use the previous hours codes. This is also dependent on other factors such as which codes are being used for IFF, packages airborne during change criteria, etc. This may not be your situation, but you can at least eliminate it as a cause.
Excerpt from the -1:
Entering “9 – ENTR” in the scratchpad couples or decouples the SCAN/LOS interrogator code to/from the transponder codes. When coupled, all changes made manually or through the change criteria (POS/TIM) to the IFF transponder pages will be automatically copied to the IFF interrogator pages. If decoupled, interrogator pages will not reflect any changes made on the transponder pages. -
RE: JTAC says Unable
@arkady86 said in JTAC says Unable:
@Micro_440th No worries Sir, thanks for your time and patience. Gotta say it went just as I wasw anticipating TBH… The same thing happened in a couple more TEs I tried to put together and I still can’t find the bottom of it. Weird. Will post more updates should I stumble upon anything new. Thanks again!
EDIT: just for completeness’ sake, when testing the TE I tried both flying the whole mission up to JTAC check-in and just jumping in mid-flight right before the S&D STPT, same result…
We (ProSkies) experienced a similar issue after building a JTAC training TE. Our resolution may work for you if you’re still receiving “Unable” from the JTAC. We discovered that the STPTs for our CAS mission only contained one target STPT (a S&D STPT) within 10 NM of the JTAC’s posit. We changed the next STPT (previously a Nav STPT) into another S&D STPT, so that we had two S&D STPTs relatively centered over the CAS area. Confirm that your target STPT attributes are “Enroute: Nav” and “Action: S&D” and that the next STPT is also “Enroute: Nav” and “Action: S&D”. I believe this will resolve the issue.