@Bikeman large FOV with the 8k X is still problematic, use “normal” in the Pimax Play settings with that offset setting I listed. I know it’s not everything the 8K X can do but it works better than it did before. and still wider than any other headset out there.

@drtbkj said in landing gear and NWS problem......Please Help!: Hi, @Rosario84 , lets see if we can get you sorted out. When I read the above and the one-time gear, the first thing that occurred was Alternate Gear. Is it possible you have Alt +G mapped instead of G? Also, I assume you’re flying a Viper If so, have you turned the cockpit NWS switch on? Also, do you have BMS-Auto selected in the UI Controls section? Thanks Thanks and thanks again, you are right, I mapped alt + g instead of g, now the landing gear works perfectly, I can take off and land without problems! Thanks again. Yes I am flying the Viper, and yes in the ui controll section BMS-Auto is selected

@Lyndiman said in Error could not create device on adaptor: Ah, you’ve got it. I booted up into safe mode and BMS loaded successfully, so either the driver or services etc are at fault. After playing with the drivers I compared the services in safe mode and not and started BMS after stopping each service that isn’t used in safe mode. I identified this service at fault: Connected User Experiences and Telemetry [image: GThMA3f] After stopping it, BMS loaded. I toggled it 3 times and every time this service is on, BMS complains about debugging being on and fails to load. Every time it’s off, it loads fine. Just got hit again just today!!! Fortunately I was pointed to this thread and it goes away. This should be put in the FAQ. Thanks.

@H0RN9TT said in How to use F-15E?: @chihirobelmo thanks it works now but i cant select “RWR” on mfd (same problem in harrier so we cant use RWR at all) edit: nvm i changed AC type to 9 (f-18 avionics) but i can use RWR now There is a “RWR on MFD” entry in the Falcon BMS.cfg under Falcon BMS 4.37\User\Config. You have to enable it changing the value from 0 to 1. I recommend to copy paste this entry into the Falcon BMS User.cfg which isn’t overwritten during updates.

Solution here https://forum.falcon-bms.com/topic/30379/error-could-not-create-device-on-adaptor/8 Disable Connected User Experiences and Telemetry service.

@airtex2019 said in 4.37.8 WPN - Repeated 'A' characters not displayed in SPICE target string: Probably an uppercase vs lowercase problem? (Wrong mfd font glyph for lowercase a?) I’m just trying to imagine what else could cause something like that… that’s all I got Yup…

@MaxWaldorf Made some more tests today on KTO with the F-16 RDAF. I have noticed that the issue is relative to the aicraft heading as well. Positioning of the FCR TAC should be ground stabilized, but instead it is re positioned at slew begin in reference to range/bearing from the ac position. In the video you see the throttle cursor controller position on the left of the screen. at 0:13 the TAC is positioned approx 20NM in front of the A/C. A/C heading is North. at 0:24 performed right a turn to heading 020. Cursor is moved and to the right. The TAC jumps to the right just as slew begins. at 0:28 TAC is re positioned and left turn performed. at 0:35 turn is complete and cursor is slewed to the left. TAC jumps to the left and away. at 0:39 right turn test is performed forcing TAC outside of radar display. After turn is complete cursor is slewed and TAC jumps to the right. You can better observe TAC position by looking at the SPI on HSD. at 0:50 cursor is slewed to the right border of the FCR display. The TAC cannot be moved past an “invisible wall” approx 1/4 display with from the right side of the FCR display. Notice the cursor controller input demonstrating limited TAC movement. at 1:39 I have performed some FCR range change to illustrate the same TAC jumping behavior. Please feel free to reach out if you need more details, another test scenario, or additional footage to investigate further.

@R is there a DMP?

Bug found and fixed, check 4.38 when released.

Was always there but before HMCS AG capabilities hardly noticeable in the HUD

AI state is different than human played ones… Minor subject

@TOPOLO Confirmed. A full uninstall and reinstall corrected the issue. Not sure how I messed with the cockpit model, but apparently I did. Sorry to take your time on this. Thanks!

Forgive me if this was covered already but I couldn’t find anything on it. I have come to find that when I try to fly anything but the above mentioned air frames, I can’t use updated radar or HSD, I just get the green screen radar and an HSI. It seems like it might be some sort of glitch or bug, and actually I should mention that the F4 phantom also has the updated AAR and HSD and that is in the Vietnam campaign. Is there anyway I can fix this? I’ve tried selecting MFDs in my data cartridge but it still just loads the same ones .

Hi there, at last, after some busy days, I was able to try the solution, which worked very well, indeed; so, thanks a lot to the guy who provided it by the fixing file I found at the link given me by airtex2019. Just a couple of other things on this topic. First of all, the remedy works well for the F15E-220, but the problem arises also for the F15E-229; one possible solution is to make a copy of the good file, naming it “F-15E-229.txtpb” and putting it in place of the broken one. The other possibility could be to simply copy at the end of the broken “F-15E-229.txtpb” file the lines found at the end of the good one (I mean, the lines starting from “mechanical {”, which is the 3267th line in the good file); but this is not enough, it is also necessary to change in the very first line of the broken file the value specified to the parameter “fmtype” which, I think, specify the flight model. In fact, in the broken file the value is “FM_OFM”, while in the good file the same parameter is specified as “FM_AFM”, so in the broken file must be changed putting FM_AFM, otherways the simple adding of the missing lines at the end of the file is not enough (this is the result that came out from some tests I made last night). I have seen that the broken file “F-15E-220.txtpb” and the good one are almost identical for the lines until the 3266th one, but in some parts many numeric values specified for various parameters differ a lot; for this reason I think it could be better not to use directly the good “F-15E-220.txtpb” in place of the bad one, but to use it simply as a source to modify and correct the broken one in the way I explained. At the end of this long post, the second aspect I would like to expose is that even if with this correction it is now possible to steer the F15E while on the ground, I found that the Paddle switch does not work at all, thus it is not possible to unlink the nose wheel from the pedals, making the control of the plane during the take-offs and the landings a very hard work. I have no HOTAS system, so for the Paddle switch I use the key combination “ALT+A”, but it is completely uneffective. I don’t know if this is due to the fact that I am using the F16 set of keys combination, but in any case also the combination “SHIFT+/”, which is perfectly functional on the F16, does not work at all. As for the ramp start, as I said before I have not yet any possibility to try it, maybe in the future. Thank you all very much, and sorry for the length of this post and for my not very good english, but anyway I hope I have been clear enough, and hope that what I have written could be useful for someone else, too. Greetings.

Hi all, I have a question. When playing a campaign and using the F-16C-52+ PXIV (HAF) which I manually created in Mission Commander, I get air task orders as to be expected but I can’t create a manual package for this airframe. In the drop down box this aircraft is just not there, Every other aircraft is working. I tested various theatres and so far it always works in KTO & Balkans but for some reasons not in Nordics or in Kuwait 64 (both OFM). I took a look and found in the editor that in these theatres the aircraft has a different name (F-16-52+ CFT), I assumed this might cause the issue so I changed the entry in FALCON4_VCD to F-16C-52+ PXIV as in the ‘vanilla’ theatres but still, manual fragging is not working. any ideas? EDIT: just downloaded and tried Mideast 128, there it works also…seems to be related to OFM…I guess