Hi guys,
after last update 4.34u4 aircrafts on carrier are sometimes stuck in each other.
Is anybody observing same problem? it looks like that after going to 3d, ATO is generating few AI flights with TOT before my TOT and they stuck on the deck because they are waiting for their time to takeoff.
Latest posts made by MikeCZ
-
Stuck aircrafts in each other on carrier deck
-
RE: [REL] dedicated server for Windows with no GPU
hi,
great work. It runs perfect (I left it like 14 days in 3d :)), just one thing. When I press Esc + e to exit from 3d to 2d, BMS closes itself. It is not generating any error, there is no crashlog aor anything like this. Are any of you observing similar behavior?
I am using only dlls in this thread, no modded textures.
System is KVM based (proxmox) with 4 VCPU (intel 4790s), 12GB RAM, default emulated GPU by KVM.Thanks
-
RE: Key File Editor - Own Devices
So, I was testing few scenarios again and found this:
1. Own device as Additional device:
a. Copied cells from Saitek X-45 sheet to Own #1 sheet
b. Set Own #1 as 1st Additional device in DX settings sheet
c. Set Saitek X-52 as Primary Input Device in DX settings sheet
d. Ouput lines are ok. HOTAS config is there.2. Own Primary device as Primary Input device
a. Copied cells from Saitek X-45 sheet to Primary Own sheet
b. Set Own Primary as Primary Input Device in DX settings sheet
c. No other additional devices
d. Output of keayboard keystrokes is ok, but there are no HOTAS config lines from Own Primary.Copying was made by twice Ctrl+A and Ctrl+C in source sheet and Ctrl+V in first cell of destination sheet. Maybe you have another version of key file editor
I tried above with fresh Key File Editor from BMS 4.34 installation folder (Macros permited). Date in README is 14th March, 2019, Version : BMS 4.34.0.
Thanks.
Michael -
RE: Key File Editor - Own Devices
Thanks for your answer.
ok, but “Own Primary” can be selected in Primary input device,right? I copied X52 sheet to Own Primary and Own #1 sheets and set “Own Primary” as primary device and “own #1” as 1st additional device. When I defined DX buttons, none of them are actually in output section (only #N/A lines). Can I send you the xls file?
Firstly, I thought that I deleted something in Own devices sheets, but when I created them again, but now with the manual, it was the same. I tried to do evaluation steps and it looks like that it cannot find some values in S column in “Keystrokes Editor” sheet, which is locked, unfortunatellyM.
-
Key File Editor - Own Devices
Hi, I tried to create own primary and own devices in key file editor sheets. I’m trying to make sheets for T16000M FCS HOTAS. Unfortunately there are no output lines for these own devices when i attach them in dx settings tab as dx devices. it works for generic devices but not for own devices. i figured, that own primary device is not shown at all and own device #1 showing #N/A error in output tab. errors are in excel and libre office as well.
I copied all cells from another tab (x52) and edited button names and printed area only. after that i filled in callbacks.
Am I doing something wrong? thanks.M.
Sent from my iPhone using Tapatalk
-
RE: [Bug 4.33] TGP not loaded for wingmen w/ LGB as default
Hey guys,
i found same problem yesterday. Sometimes it works,but sometimes whatever i reset TGP is still off. I found workaround. if you end mission and jump into it again, TGP will be loaded and fully functional or i didn’t reproduce it when mission starts from taxiway. I didn’t test it too much (maybe 4x) but it worked for me.
It looks like a bugUpdate: or it is not,and i’m doing something wrong at ramp start
-
RE: Mouselook does not want work!
Hi,
i uninstalled opentrack,facetracknoir and panning works now. However, i had to install opentrack and then uninstall. maybe there is some key in registry or something.M.
-
RE: Mouselook does not want work!
Hi,
I have the same problem too. I have no trackir,facetrack,opentrack running. Using default - basic keyset. Mouselook/keyboard even POV hat on joystick doesn’t want to work for panning in 3d cockpit (3). In snap mode (2) POV hat works flawlessly. mouselook behaves same as described in 1st post - no panningBtw, i noticed if you press Shift+Num3 (basic keyset) view goes backward, which is right. other keystrokes for panning don’t work.
Do you guys have any progress with this problem?
thanks in advance.