BaronVonVaderham

Did another attempt just now. Recorded the tracks for each attempt. I suspect the inability to start up again may have been associated with me switching to idle just a tat too early. I will include bindings in a follow up post as I couldn't grab screenshots for some reason ( I don't have a printscreen button and for some reason the win-shift-S button doesn't seem to work, maybe because by default dcs launches full screen on the main monitor? As for the TQ, its a winwing F-16 quadrant, 10th anniversary edition. I set up the sync controls now. Not sure I'll like that as I tend to forget to set up the HOTAS for the start of the mission configuration (and some trainings and missions start in flight, which means with sync on, the LG will extend, and the speed brakes could deploy, depending what I did before) king of the hill early throttel start no hotas sync reattempt.trk king of the hill early throttel start no hotas sync.trk king of the hill ly throttle in idle start hotas synced.trk king of the hill ly throttle in off start hotas synced.trk And here are the bindings note that I didn’t spot an “on/else…” for the throttle controls I did see them for other controls though

All good . I think it’s easy to get wrong when mixing virtual with real controls. Unfortunately it did with me. Switching the aircraft off in mission and restarting the aircraft from scratch didn’t work, closing and restarting the mission from scratch also didn’t work. The only thing that worked was restarting DCS, hence I believe it’s a bug. I’m not using on/ else off/on in any bindings, and I’m fairly certain there are no double mappings of devices for the same binding (I am fully aware of this one, because with each device update, multiple devices automatically get mapped to the same axes. I’ll have to check the sync with HOTAS option. I’ll do that today. I’ll get a track at the same time.

But this shouldn’t be persistent. If I close the mission and select it from scratch, and start with the throttle in off, it should be able to perform a start. In other words, it looks like the situation is latched in dcs memory. And that to me is a bug.

I don’t think I did, but I will check. as a beginner it’s an easy mistake to make, to not set the throttle back to idle before attempting to start. I wouldn’t expect the game to remember the problem for a particular mission until I restart the game though. If I restart the mission with the throttle in off, it should work normally again. Soo to me that seems like a bug. another consideration is that when a training starts in flight, and my throttle is in idle, or off, rather than in mil, this does not become a problem. In fact, I tried starting up with auto start with the f-14 once, with throttle in max. And once I let go of the brake, it launched me into the ocean .

I’ll do some more investigation tomorrow. I just noticed that it started happening with another mission too when I tried it a second time. The constant is that I left the physical throttle in idle during startup. doggies that becomes an unrecoverable error as restarting the aircraft won’t help. I can recover it by restarting dcs with the throttle in off. I’ll try to reproduce it tomorrow and post a track.

The mission does not allow the aircraft to start up, either manually or via auto startup. When start 2 is selected, the engine spools up to 20%, but after that nothing else. The JFS light does not go off, and moving the throttle to idle out slightly beyond idle, does not start in the engine. For info, my throttle quadrant has the idle switch set up for idle, and the off switch for engine off. also note that during auto start up I have the throttle on idle. The auto start moves it to off, and to idle when needed.

I found the dial of my antenna was completely to one side. After that I had a problems I had to troubleshoot, so it took me some time to try the mission again. I managed to get all the bogeys show up consistently. But I believe the radar is modeled quite realistically, as in, at 80miles it doesn’t work very well, haha! At 40 miles things show up. So the first one I get. Insistently at 30-40 miles. The second sequence, a pair of sun’s, I actually have to get to the waypoint quickly, or they will gone way passed the waypoint, and I won’t spot them until I’m right on top of them. I managed to get them consistently. Somehow the radar struggles more with that pair, maybe because they fly perpendicular to my trajectory. If I rush things I can just about shot them down in line with the given instructions.

I found the issue. Somehow the afterburner detent was set to on in the f-16 special options menu. I think I’ll write a document on the ab issue. The main info is available, but it’s easy to get lost if you don’t know where to look. Plus I would like yogi e something back to this community

“Mate”, if nothing to contribute, keep quiet. No need to respond with arrogant comments that don’t help anyone. If you don’t like the post and/or think beginners are stupid because they don’t know everything yet, then ignore the post.

I was actually not able to find the “cycle afterburner detent on/off” controls on the F-16 control bindings. however, I did find a similar option (not control) in the special options tab when the f-16 mod was selected. Turned out this was somehow switched on. After turning that off it worked as expected again. @mustangsally, the attitude does not help (a simple “check this link” would be more friendly, more helpful, take just as much effort as your reply, and leave a better impression), and the information isn’t exactly accurate. for example, if your ab isn’t set up and working, you cannot determine the throttle position at which ab engages. Much easier is to check what the value at the detent is in simapppro , which identifies the value on the top. also, as far as I’m aware there’s no actual need to perform ab calibration in simapppro. in addition, unless you know exactly where to find each of these options and controls in both simapppro and dcs, you will struggle finding what you need. Note this would not be a problem of either was logical and intuitive, but they aren’t. (Detent on/off option on the special page of the adjust controls menu, AND needing to select the mod before it shows up, it’s not exactly intuitive, nor is the determination of the ab ratio).

It may be worth noting that this was always with missions for the f-16. Specifically the amraam mission and the landing during clear conditions from this training pack: https://www.digitalcombatsimulator.com/en/files/3328308/ I’d be surprised if missions can be limited to the use of afterburner, but maybe this is possible? For example, I just found out that there is a “Cycle Afterburner Detent ON/OFF” option somewhere in dcs. Maybe there was an update that was installed without letting me know, or maybe this was set for those missions? I also read something about “afterburner gates”. Is this The same as “cycle afterburner detect on/off”? Does anyone have a screenshot for finding these options, so I can locate them easily? Finally, I read on another thread that there is a way to calibrate afterburner. I’m rather annoyed about the lack of clear step by step instructions on how to set up throttle quadrants that include every single step and option and control for both dcs and for simapppro. Because without knowing absolutely every option and setting and control and calibration that must be in place for throttle and afterburner to work as intended, it’s impossible to get it right.

FYI, simapppro required me to update firmware for both the throttle and the stick. After update the dcs settings for the throttle we’re wiped out and had to be reprogrammed. i checked the ab ratio and adjusted it slightly. I calibrated the rx/Ry going through the full range including afterburner range. I then calibrated the afterburner position by rocking it between mil and full ab and ending calibration with the throttle at full ab. nothing changed. here’s footage of what’s happening. As you can see, the throttle lever dies not move beyond the mil point IMG_1071.mov

Hey guys, overnight my afterburner stopped working. looking at my throttle in the cockpit it looks like it’s not going to the full afterburner position. But when I look at simapppro or the axis controls in dcs, nothing has changed. The afterburner point is still at 75% where I set it originally. since I’d rather hard to set up without extremely detailed step by step instructions, can someone remind me how to set the afterburner position both in simapppro and in dcs? Note, I’m aware that in dcs an axis can be set to slider or not and that could affect things, but I tried changing that but without effect.

I’m not touching antenna elevation actually, only the mfd. how do I get tracks/videos from dcs?

Before actually reporting a bug, I’d like to check if this is something I’m doing wrong. I’m doing the aim120 amraam mission that comes with the f-16. In this mission you first do an stt shot on a single bogey, I. The second part you engage two bogeys and are supposed to fire the first amraam before it becomes active, wait for it Togo active, the. Unlock and target the second bogey and fire a second amraam, and the third part is a mad dog shot on a single target. I noticed that I don’t always get bogeys on my radar. Sometimes the first bogey does not appear, though out of the twenty attempts that happened once, at most twice. The two bogeys on the second part however, often fail to show up, maybe once every two times. now I do rush through the briefing and switch settings before the in flight briefing is finished. And I also noticed that the highlight box for the map range button never goes off. I also notice that if the two bogeys are not within my amraam steering error circle, my radar will not pick them up, which is weird when I use max azimuth and max elevation. I know that this means the radar is slow to refresh and detection is tougher, but it does avoid missing the target due to wrong heading or pitch. In any case I found that I lose locks very quickly in the second part when chasing the two bogeys, and often I have to reacquire a lock. so… since it seems as if I’m not using the radar correctly, I wonder if missing the two bogeys once every two attempts is a flaw with me, or a flaw with the mission. note, sometimes I see them visually right in front of me at 5nm, but my radar still doesn’t see them (this happened twice). Changing radar range did not make a difference in this case, and I could only use the mad dog approach.

Check the second half of the second post on this thread: This is where I got my information on Razbam kneeboards. As a note, in practise you may only notice if you try to export the kneeboard.

I read on these forums that Razbam vehicles have their own kneeboard implementation. This came to light when people tried exporting the kneeboard. I suspected this might be the case. I think those are with the aircraft mods in the saved games directory though.

I’d imagine missions and trainings are also considered mods, and should be in the saved games directory? I’m aware some config stuff is in the saved games directory (eg monitor setup), but other config stuff might not be (eg Helios outputs). the same applies to those using DCS bios. The trick with cockpit builders is modifying config files such that a valid IC is achieved, but that does involve file modifications. i think kneeboards may also be affected in different ways, especially sins Razbam uses a different kneeboard than ED.

Out of curiosity, which mods are installed in the DCS world/beta directory? I’m assuming different mod categories go I different areas? I recently had an update, so I’ll need to check to see what got thrown off. Haven’t done much yet other than install missions and new aircraft and terrain (mostly the official pay ware once, plus a few freeware aircraft). Oh, and today I updated the monitor config lua.

Thanks, I’ll give that a go. one question (before I google it and give you the answer how can I ensure the monitors are perfectly lined up?

Question: having read the very first post briefly, is it Still necessary to deactivate all installed mods?

No worries. not sure why this is happening either. Maybe some peeps at work can explain. Maybe I’ll need to reinstall some drivers, or maybe it’s the monitors I’m using. got another problem now: i seem to be getting a few pixel lines of the desktop seeping through on the bottom, which is a little weird. maybe if the displays had more pixels?? This would explain why there is a profile with 7 extra vertical pixels. not sure of this is the widows alignment (which snaps to certain locations), or maybe I need to stretch the image for the right mfd. Edit: fixed it: it was the windows alignment…

I’ll give your suggestions for probleem 1 a go. I agree with problem 2 being a non issue in practice. Just would be nice to know what happened there. as for problem 3, nothing un -standard that I’m aware of. Using an rtx 4080 card with Nvidia latest drivers. mfcd monitors are connected with hdmi and usb (usb for power). I tried again but swapping their location in widows but I can still follow the mouse from left to right. Maybe it’s the monitors themselves? They’re cheap-ish 8” (ones from Amazon. “ELECROW Mini Monitor, 8 Inch Raspberry Pi Display, IPS Screen, External Screem with HD Resolution, 1280 x 800 Portable Monitor for Laptop, PC, Raspberry Pi, Game Console”, see screenshot. I’m using 2 hdmi connectors on my gpu. It’s not really an issue as long as I number them and use them consistently in that physical order.

Hi all, i seem to have some degree of success with this. But I’m not sure I did things right completely. i didn’t change the config.lua in the save games directory, so multi monitor is still set to 1camera. a couple of things that may or may not be important: 1) I’m using a 4K as main display and 2 1280x800 displays for mfcd (I think their resolution can be set higher, but this is the recommended windows setting) 2) I put them horizontally in line; display 3 is 4K and main view, display 1 is the left mfcd, and 2 is the right mfcd. 3) The order of the displays in Windows from left to right is 3-1-2, with display 3 being the main display. See screenshot widowed display setup. 4) arranging 1 and 2 in windows doesn’t have any effect. In real life the physical units are still arranged the same way compared to the main 4k display. I have to swap displays 1 and 2 physically, before they align in windows. I don’t understand this. it is as of windows always looks at the physical port and ignores the number. 5) based on my calculations I should have a total resolution of 6400x2160, but for some reason there is a 6400x2167 resolution in DCS available as well. I double checked the monitor lua, and there’s no Y position or height that would in some way result in 2167. See screenshot lua file. 6) In DCS I selected the correct resolution, and I selected for monitors “3monitorsetup” Which is what I named my monitor lua file. See screenshot DCS options. Problem 1: on display 2, my right mfcd, the windows task bar appears, but not on my display 1 the left mfcd. See screenshot desktop. How do I get rid of that task bar? Problem 2: where does the 2167 come from? Should I worry about this? Problem 3: how can I ensure windows sees the left mfcd as display 1 and the right mfcd as display 2 without having to swap them physically? (They are correct note, but when I start building my cockpit I will forgot which one is which, and I don’t want to keep troubleshooting this over and over again.