I think the discussion drifted away from acquisition to the general changes of the missile performance.
I remember the ranges that we were used to in 4.35. The tactics in BVR were a complete different story compared to now.
Today we (especially my squadron) complain about guidance behavior of the AIM-120C and we learned that this part seems to be mostly untouched since the old Microprose days.
So instead of wining and complaining because we can not apply the tactics of 4.35 any more we should wine and complain about the old guidance code, that’s still in place!
Best posts made by Razor161
-
RE: 4.37.3 AIM120 AQUISITION MODEL
-
RE: Why BMS team put a Link 16 device in Christmas message photo?
Maybe there’s a bug in the AI image generation…
-
RE: Block 50/52 pits
@FoxBMS said in Block 50/52 pits:
I think this is not as it should be. When you compare the real photos of F-16 cokpits, also compare with other games how it should look like, you will find that using these cockpits making the feel from the game a bit unrealistic. This is probably not so easy to fix, just wanted to mention.
The hud frame angle is aligned to the pilots head.
- If your head is in the natural position then you don’t see the inner or outer side of the HUD frame.
- If you move your head foreward then you see the inner side of the frame.
- If you move your head behind the natural head position then you see the outer side of the frame. You could argue that it should not be possible to push the head into the headrest of the seat in the 3D pit.
However I don’t see an issue here.
Keep in mind that many pictures are taken with the camere in front of the head. There are maybe not so much photos where the camera had the correct position.
Also… comparing to the other flight-sim/game… They mimic the perspective of a camera which is placed in front of the pilots head. That is not really something that I would call realistic. But these are just my 2 Cents.
-
RE: FOV on Triples too zoomed in
@Icer
You need to adjust two settings:
===group// Vield of view set g_fDefaultFOV 140 set g_fMaximumFOV 140 ===
-
RE: 4.37 killed the AMRAAM
@Mav-jp said in 4.37 killed the AMRAAM:
@Mav-jp:
and i never saw AI defend this way (and i’m the one who coded it) …Omg, the AI awakens…
-
RE: SDBs in Tandem: Using the Meter Sticks
@ericfa2a said in SDBs in Tandem: Using the Meter Sticks:
@Crassus I have just made a simple TE with JSOW-154A.
- First, the number for the meterstick is in meters and it’s the total length of the horizontal part of the cross. Here there is a difference with all the docs i have read for BMS
‘TO BMS 1F-16CM-34-1-1.pdf’
Chapter 2.10.3.5 NORTH POINTER / METERSTICK (page 148)By selecting N/M via OSB 19 in the Control page the longitude, latitude and elevation of the current System Point Of Interest (SPI) position will be displayed in the upper left corner of the MFD display along with an arrow pointing north in the upper right corner and a number to the right of the meter stick (cross-hair) which is the length in meters of each line of the cross-hair.
I think all should be clear according to the available docs for BMS provided by the BMS team.
-
RE: Pico 4 experience and settings
@ipetter
I’m in the office right now and can not check which app exactly I installed but I think it was this one
https://m.apkpure.com/de/hotspot-and-tethering-shortcut/com.pw.hotspotshortcutThe workflow is simple:
- Connect the Pico 4 to your wifi.
- Activate USB tethering using the app (Approve the connection if Windows asks if you want to use the new connection).
- Connect VD (works only on wifi).
- Disable wifi (Pico will shift all network traffic to tethering automatically)
- Run the game.
In case you lost internet connection on your PC after the network connection switched to tethering you need to change the network priority for your network adapter to a value which is lower than the tethering adapter. Here’s a guide for it:
https://www.windowscentral.com/how-change-priority-order-network-adapters-windows-10
Latest posts made by Razor161
-
RE: [BUG] XMT switch should not move
@airtex2019
I just did the test and the result is as expected:[04:38:39.737] 19416 INPUT: SimThrottleIdleDetentForward (DOWN) [04:38:40.293] 19416 INPUT: SimXMitDec (DOWN) [04:38:41.556] 19416 INPUT: SimXMitDec (UP) [04:38:42.238] 19416 INPUT: SimThrottleIdleDetentBack (DOWN)
In the BMS - Auto.key these three key bindings look like this:
#======== WINWING Orion Throttle Base II TGRIP-F16 ======== SimThrottleIdleDetentBack 512 -1 -2 0 0x0 0 SimThrottleIdleDetentForward 512 -2 -2 0x42 0x0 0 SimXMitDec 532 -1 -2 0 0x0 310
So I basically move my throttle out of the cutoff position and that also triggers SimXMitDec.
But why? -
PICO Connect - Godlike
Hi all!
For those of you who have enough GPU power and want to push the little Pico 4 a little more, there‘s a way to increase the resolution (and also bandwidth) of the new PICO Connect PCVR software.
https://www.reddit.com/r/PicoXR/comments/1bm1x62/newpico_connect_godlike_settings_guide_text_guide/Tested on my machine and works just fine.
-
RE: Varjo Aero and Foveated Rendering
@Icer
That‘s interesting. Picos new PCVR streaming software (Pico Connect) has fixed foveated rendering (at least it looks like that). -
RE: PICO 4 - Virtual Desktop - Wired Connection
@A-random-F
I have no idea. It works fine for me without any issues in my Pico 4. -
RE: [BUG] XMT switch should not move
@airtex2019
No I have g_bUseAnalogIdleCutoff = 0 in my config.
I have the Winwing F-16 throttle. It has a detent for cut off.
I just had another flight and I heard again a switch flipping. But this time it was not XMT. I have no idea which one it was. This is spooky… -
RE: [BUG] XMT switch should not move
@dumba
That was also my first thought. But My throttle has not detent when going into AB.
The only detent is the idle cutoff detent which is triggered when I move the throttle out of the cutoff position.
I checked my keyfile and the key id is only used for the idle cutoff.
At my last flight I heared a switch flipping again when moving the throttle while power is off. But I was unable to spot the switch. -
RE: [REQUEST] Do not fiddle with my steerpoints
@airtex2019
We had a training TE were we had IMC conditions when we come back to the airbaes. It happened as described. -
[REQUEST] Do not fiddle with my steerpoints
The situation:
I come back from a mission and tell ATC that I’m inbound for landing.
ATC responds that the airfield is black and not available for landing. It also tells me what airfield is availabe with additional infos like TACAN channal.
Thats fine so far.
But for some reason my steerpoint is magically set to that other airfield. What feature does the F-16 have here?I understand that this is nice for gamers but please don’t modify any steerpoints just because ATC tells me that the airfield is black. I think there’s something like an arcade mode in BMS. Such assistance might be fine there.
-
[BUG] XMT switch should not move
Version
4.37.3 (x64)Detailed Description
ECM XMT switch moves from position 1 to 2 when cockpit is cold and dark and the throttles is moved from cutoff to afterburner.Reproducibility Procedure
- Enter an F-16 with ECM panel in cockpit.
- Close canopy and do your preflight checks as usual and verify that the XMT switch is set to 1.
- Before setting main power to BATT or ON move the throttle from the cutoff position to full afterburner and whatch the XMT switch.
- The XMT switch moves from position 1 to position 2 while main power is still off.
Expected Behavior
When cockpit is cold and dark nothing should happen regardless what I do with the throttle.