@airtex2019 I have this, left and right are just two up and down buttons, middle one is a mini-throttle/axis.
ID in DeviceSorting.txt for me is this : {0200231D-0000-0000-0000-504944564944} " VKBsim Gladiator EVO R "
@airtex2019 I have this, left and right are just two up and down buttons, middle one is a mini-throttle/axis.
ID in DeviceSorting.txt for me is this : {0200231D-0000-0000-0000-504944564944} " VKBsim Gladiator EVO R "
Wanted to quickly test how MICA IR missiles work with the LOAL changes introduced in 37.3 so I got into a quick dogfight match vs the AI.
Theater: Default KTO
Version: 4.37.3.2 build 1358
Repro steps:
This happens on both sides, whether I fly the Mirage or the AI does.
Crash log and dump for human controlled : https://drive.google.com/file/d/1egeXM_fIMBd-iaxPCY3D8H21E6nT0bga/view?usp=sharing
Crash log and dump for AI controlled : https://drive.google.com/file/d/1NGW-N7Q2YHSZlOR5xgia4M7z7tqhao2d/view?usp=sharing
@JP Hm, maybe check and tweak the FOV settings in the Falcon BMS.cfg file located in User\Config folder. You could increase maximum FOV to your liking.
@JP Idk how a a higher resolution monitor would help tbh. I currently have 1080p monitors so idk.
I also have the Grassmonkey camera about 60-80cm away depending on if I’m flying BMS or playing some other game with headtracking, don’t know if that could help you.
@JP Have you tried to recenter when you are at your desired position by hitting the keybind that is bound in Opentrack?
Don’t think this is a game issue but a setup issue, either physically on where the sensor and you are sitting or on how things are set in Opentrack., so FOV and zoom changes in game probably won’t help.
@regev Remember to also switch the HUD brightness to “Night” in the right console.
It’s located with the other HUD switches near the stick.
@Radium Pretty sure he’s giving a compliment to kouzi and saying that his afterburner should be the default in BMS as it is better than the one we currently have.
@RUSHER0600 I haven’t managed to fly ITO80s lately as I’ve been mostly flying in UOAF, so I can’t help unfortunately.
@Sneakpeek Why do you need the in-game HUD frame to be visible when you have a real cockpit?
There is a specific view for those who have a real life full cockpit, called “Empty Cockpit Shell” and can be toggled with “Shift 2”.
It is mentioned on page 105 of the User Manual.
Wouldn’t that work for you? Or am I not fully understanding the problem?
@Killroy I also have it set but it doesn’t always work. What it seems to do is basically hide the overlays at the same time it’s taking the picture.
So sometimes when I might be taking 2-3+ screenshots in quick succession the green text on the left or the bottom overlay in external views might appear on some of them.
This is pretty minor but thought I’d report it.
When hiding overlays by using Ctrl+` (also called pretty filming in the mapping) it seems like taking a screenshot with Print Screen doesn’t register and no picture is saved in the Pictures folder.
I’m not 100% sure but I think it only happens in MP and not in SP.
Had a crash while dogfighting on the FO TvT.
Started stuttering a lot as soon as I locked an enemy F-4 in dogfight mode and then crashed.
Crash dumps : https://drive.google.com/file/d/1sF9zKvqfxCqzNxdNBkRREWxbD0OK0Jsw/view?usp=sharing
@sasah320 If I’m not mistaken even if a single runway section is damaged/destroyed you can’t frag flights (you can still frag if only the threshold is damaged/destroyed), so it’s quite hard to find a case where you can take off from a taxiway.
Maybe if you land on the taxiway of some FOB/alternate just to refuel and take off again from the taxiway. But it also wouldn’t make sense gameplay-wise. You would be forced to pretty much carpet bomb airbases just to make any flights unable to take off as persistent people would certainly find enough space to take off even if you bombed the taxiways and runways.
@Kavelenko What do you usually use as the STPT? Middle runway section? Opposite runway threshold from the heading you will be attacking?
The drop from 3600MHz to 2400MHz might be quite substantial.
I think you will probably need to find the balancing point of least performance drop while avoiding AMRAAM shenanigans.
Maybe drop to 3200 first and do some tests, then to 3000 if you still have issues, then 2666 and lastly to 2400 if there are still issues at 2666.
I remember someone in the FL discord also had some issues with BMS and OC’d RAM, not about AMRAAMs though.
I think speed matters too. You can’t be going 100-120kts+ from my experience.
@nerdman Are you aligning the HMCS?
@cougar56th Yes. CTD was with everything updated. Haven’t managed to try it in KTO, Balkans or plain ITO yet.
First flight in ITO 1.07.2 and 4.37.2 and got instant CTD when requesting taxi back to ramp in ITO80s.
Crash dumps : https://drive.google.com/file/d/13FIB3c-CgTQciotTMNVSDJa5QbC59B_q/view?usp=sharing