FlyingTaco21

next time that I played it had stopped. may have been a installation issue requiring restart. I dont know, but it seems to have resolved itself for now. i'll keep an eye out

its not I had an earlier issue which that was the remedy to, but it is not a factor here.

after the last patch a issue popped up where in a mp server (i have not tried running it as single player yet) The cockpit is rendered twice. There is a stationary version and then a version that reflects the inputs of opentrack. this happened in both player aircraft in the mission. In this case a A-10 and a bronco. they appeared to be overlayed with one another and to flash in strobe type effect. r7 3700x r5700 xt (upscaling active from 1440 to 3280 or whatever the highest is. this resulted in a higher frame rate for me than just running it at the high graphics setting for some reason) The mission ran fine prior to the last patch, so my feeling is that something changed with the update. Is two cores in the gpu rendering the same image a thing? can cpu multithreading even do that?

nullthe last patch might have introduced contaminated oxygen. not sure. when I was on the ground this issue seemed to be isolated to the sky above the horizon, but as i got up in the air it seemed to effect the jet as well. static stuff on the ground and the ground itself seemed to be unaffected. movement and zooming of the view made it worse or dissipate depending on the angle. it seemed most apparent when there was more sky in frame. i am running open beta multithread build R7 3700x with a R5700 XT 32 gb of ram.

Well when it runs it is better. I managed to undervolt it successfully... sort of. The pc works fine in dcs and then stops after about 45 minutes mentioning something akin to driver timeout or driver lag. I've never really tried to tune a gpu before primarily because I've never had one that presented me with so many options as the AMD software does. Are there any 5700 xt users out that that have settings that work for them? ( ie settings for the card and dcs itself)Think the first thing I will do next is turn off the card provided enhancements that are activated by slider. The Temps are actually very good for this card so I don't think it is throttling. But it is crashing none the less. I'm such a neophyte to all these options that I don't know where to really start outside the card voltage and speed settings. I've tried to adjust mine in like with what everyone on yt says for undervolting.

might be it if it reset that option I was was in an A though went through the updates and didn't find anything after burners specific so I bet that is it. Edit: yep that was it.

Yeah I don't really use them . I didn't start looking at them until I noticed the odd behavior and thought the hashed areas indicated AB. The rest still applies I hear the click normally associated with AB activation but its on the axis rather than with the AB gate button and I can't really tell when I am at mil. Either mil is in the same place but the animations have changed to resemble AB (though this wouldn't explain the bump/click that is the audio cue for the the AB). Prior to this mil was the upper stop of the physical throttle axis and I could only after afterburner by using my gate button. There are supposed to be something like 5 zones but to my knowledge these are not in yet. Just AB or not. I have not played much for the past 3 weeks though, so I may have been from a previous patch as well.

I don't see anything in the patch notes about afterburner but I'm getting (or think I'm getting an uncommanded switch to burner as part of the throttle axis now rather than with the button I have assigned to the afterburner gate... or maybe the animation for mil power was changed to better reflect reality but the fuel consumption etc seems to suggest that it afterburner.

Does athe 54 prefer to loft even when it isn't necessary? The pattern i have noticed is that shorter range pal/stt locks don't seem to loft but like a switch at some point they will just try to loft sight up and thrn try to drop down vertically.granted I dont know thr exact scan zone for the seeker. But it seems like a more lateral travel would increase the chances of the missile seeing the target for a longer period of time. Thinking flatter trajectory arty fire vs a mortar. The motar shell has smaller cep, and doesn't really get a chance to see a moving target unless the target passes directly under it, but a arty shell has potentially spends more time "seeing" its target because they are moving almost in the same plane. In many of my tests my phoenixes are doing reverse maverick from the recent trailers where the missile just drops almost vertically to one side of the target . It has energy but its just not guiding or seeing the target. Most hits I do achieve occur 45 degrees or less. The steepness of the arrival angle seems to matter here, and I don't recall it ever being as aggregated as it is.

The feed switch balances fuel by forcing depletion of the selected set of tanks forward and right or rear and left . There is no transfer, its just that one both engines feed off of one set until a near balance is achieved and then the in the norm feed setting one engine is fed by each set of tanks. I have noticed the forward and right always seems to have more fuel but when I set feed to that tank set and forgot about it for a bit I definitely drained that tank set. More than rear and left.

Had this happen as well on an A during field landing. Throttled down and then no more inputs were accepted i switched to manual throttle mode and that didn't work. Can still cut the power and start engines again, but it acts like the aircraft is not seeing the axis. Actually cleared and rebound my bindings and got no response. Had to restart thr mission to get it to work again. Edit read or heard something about a mechanical linkage that could only be reset by the ground crew, but that specifically effected the auto pilot itself, not the throttles. If the link broke you just couldn't use autopilot as I recall, but I mention it here because I thought it might be associated in some way

Would not be surprised in ye olde tymes capacitors were often made of paper and even wax coated paper degrades. there was an antifungal coating put on radio components that served in the tropics but I'm also thinking about batteries many of thr older missile such as those used on earlier talos missiles were single use and could actually mess up the electronics if they sat on the rail too long (that is assembled armed loaded onto launcher and powered) .. not saying that us the case because I know more about radios from the time than missiles, and what I so know tends to focus on ship launched but just knowing about the components available at the time .. lots of points of failure. There was typhon system before the aegis system that most us warships carry, but it was canceled because the concept outpaced what could be achieved reliably with what was available at the time.

The ault report pointed out many missile failures were due to issues associated with tropical settings and that no one really knew how to take care of missiles that return on aircraft. Vietnam was really the first war where missiles were used and everyone was doing stuff for the first time in combat conditions. Tech around that time was tube based in a lot of cases and the batteries were a bit questionable. No standardized reconditioning practices in place etc

Snap views for the fuel quantities would be nice.

Maybe I missed something but everything found indicated it inoperative that is, the scr 522 worked so long as you set channels via ME but the bendixhoming set worked as a iff but did not have full functionality.

Seems like with all the work that was done to the mosquito along these lines it could be retroactively added to the 51 pacific version. .. think thats the 30? Would be nice to have radios as a substitute for way point markers on the f14 etc.

does this have anything to do with why I cannot bind trim controls in the mossie? The bindings are still there but I cannot bind anything to my joystick. The keyboard ones still work but ..well there are quite a bit of previous bindings missing. no axes at all except for views

I do not use thrustmaster, Am using a VKB set up with the sem and THQ modules have two duplicate input sets for the same controller. The latest is that the DCS is confusing the Throttles for the X axis of my joystick and is not letting me bind my physical X axis to anything. Going to try to recalibrate everything before I do that, and then just try a clean install of DCS... Though I am not at all convinced the issue is DCS since MSFS is showing two duplicates of the joystick/modules as well.

I ran across this too. I have been using a ... what is it.. trimmer maybe? where when the wheel is spun up its a series of button presses and not an axis? I have been thinking about creating a virtual one of those as a work around. dont know if its doable with VKB software yet, but that would theoretically require a different profile for the stick software altogether because it would be changing the inputs to the game on the stick end rather than game end. I have one of those rotary wheels that acts as two buttons already, but it is at the opposite end of my control set up. kind of frustrating. Also might be able to program voice attack to unlock the control with a virtual key press but again I dont know how many presses of page up it takes to unlock the throttle. The last solution that probably will never happen is a binding similar to what some of the jets have that moves the ingame throttle out of the cut position and into a start position. Many of jet throttles will not respond until you do that. seems like they could have done it here.

in my case DCS and MSFS seem to be seeing two exact copies of the same hardware. So It might not be a DCS issue. Both controller tabs are mapped to the same physical device. Sorry i missed these replies.

By this i do not mean binding profiles associated with a module, but the columns in the bindings menu that are associated with a given controller. I have two of these device columns that are associated with the same physical device and wish to delete one of them, but cannot locate anything other than my saved bindings for the software modules. I have rescanned and it did not rid me of the duplicate

Typos occur on phones, and I had been editing some of that didn't catch everything. And I had cw in there. Cw is transmission type not associated with Morse code the meaning of it is a bit out the realm of relevancy to a dcs player. The point was to translate what might be found in period manuals that user might resort to into something they can relate to and not drag them through tube,capacitor, and trimmer functions

Depending on the fidelity of the model they are using, thought I might clear up some stuff with receiver at least. The set is a hetrodyne receiver which means it mixes a locally produced signal with the received signal to create a intermediate frequency that the radio then works with. Any deeper and you get into radio theory etc but it gives context for the get hetrodyne switch on the lower left. This is misleading because this switch is actually a beat frequency oscillator. The BFO is on when this switch is flipped on and really only deals with CW or Morse code transmissions. The British called this wireless radiotelephonery and it is the presence or absence of a signal. Since there is no data in the signal, just being a carrier wave, the BFO is used to translate the absence or presence of a signal into an audio signal. When you leave that switch in the up position the set is basically an AM radio set. This was called radiotelphone by the British so if you see wt or rt anywhere, this is what it means. (I’m not sure about the overriding tone that is present with the BFO switched on. I do not have experience with that particular set in real life, but this behavior is more common when the BFO is switched on when you are receiving am rather than cw. The BFO only works in the presence of a signal so the result is a constant steady tone that overrides the regular am signal. Morse code transmissions using a BFO are generally very clear unless the airwaves are very crowded. ) The filter can help here. I’m not sure of how much it cuts out or even if it is operative here in dcs but it limits amount of the radio spectrum being listened to. omni setting on the master switch probably best used for cw type beacons and maybe resistance operators using parasets. AVC was said to non operational earlier… I’m not sure because the I’ve not picked up a AM station to try it out on. But, I’m really struggling to find a use for it absent direction finding using broadcast radio where signal strength would vary so much that you would be in danger of getting your ears blown out moving from weak to strong signals. If you were to be listening for a very weak signal I would not use it at all as it tends to limit sensitivity. im not familiar with the antennas are modeled beyond the loop in the cockpit , but you would want to use a more Omni directional antenna like a dipole that receives symmetrically along an axis rather than directional antenna that would be great for finding single signal and providing a bearing for the pilot. The visual mode of df probably uses some element of the antenna set up to analyze multipath reception and signal strength. Can’t do that with the directional antenna. there are notations for low frequency medium etc… this is because antennas are turned for specific frequencies. Would have to have the aircraft manual to have the specific to figure out the optimized combination of antenna settings for a particular use. the color bands on the receiver match the controls on the transmitter for the same frequencies. The radios use the old units of mega and kilo cycles rather than hertz. that’s all I’ve got for now.

ive notices it quite a bit but only after the tail raies. aircraft will draw right and then then when the tail lifts there is a strong left tendency a left roll when off the ground

so this happened i have a track.. at first i thought it was just the blades rotating around the fuselage, but no apparently the model is goofy was trying to fuze bombs atc and the never ending trim battle ended badly. feel like we need a micrometer trim function