darkman222

Same here. Located in Germany. Unfortunately I took the update. Now the authorisation is gone. Cant even play offline now. What now? Go outside and meet friends? I dont have friends, and whats this so called outside?

Of course the way the mission is built makes a huge impact on CPU frame time. But what happens, same mission, same server, better CPU? Quite some time ago was hoping to get better frame times when I run my single player mission on a second PC. So I made a SP mission a MP mission running on a separate PC with my gaming PC being the client. Turned out, CPU frame times stayed almost the same. So every client has to do its own calculations, which sounds very very VERY unoptimized for a multiplayer game. Edit: I ordered a new CPU. I hope I can do some research on this exact topic when switching to the new CPU.

I have now set the mission date to 1980. Time flown 35 minutes and 350 nm. The drift is not bad, but quite noticable. With some minor aerobatics too So i guess for pre GPS missions kind of important, but for missions with GPS irrelevant. Correct me if I'm wrong. Not really sure which waypoint is which, but my guess is that: I might do another in depth test now as I can confirm that changing the date disables GPS and INS drift is modelled.

Earlier variants of what aircraft had less thrust? The Viper? I did some reasearch and math, and its like 5% difference between models up to block 52. But just quick research, feel free to correct me. Talking about DCS only, not real life. The only chance on guns only dogfight servers in an F16 against F18 is to turn around as quick as possible after merge and shoot it in the face. If the F18 survives the first merge, you have to be really creative in the F16 against a competent F18 driver. What Mirage dudes do is to jink like crazy, so you gotta slow down with them. Then you overshoot, maybe try to go over the top, but then the Mirage already sits in your turn circle and stays. And after the Mirage FM change, it will just sit in your turn circle and wont stop pointing at you, while not bleeding enough enery for the F16 to turn the tables. Edit: And if I switch side to the F18, I absolutely know why people pull the paddle. Because that thing just does not stop to speed up. If you want to conserve energy you need to pull the paddle to stay in the 370 kts area. Or use speed brakes or throttle down. But why would you do that if you can use the speed, for better turn rate with the padde. As stupid as it sounds, but its understandable to adapt that habit.

Question about FIX taking. How much can the INS drift in DCS in a regular mission. How is it possible that GPS is not available to take permanent care of INS drifting? I did a travel of 350 nm with an airborne spawn F16 and the INS did not drift noticably. The waypoint on the tip of the peninsula was more than good enough to kill a pre planned target here. I am talking about that FIX taking turorial. When will that be necessary in DCS?

You could have had an easier time. My predictions how ED will react to this were on point

You can do whatever you want and take up the time of whom ever you want. Youre a free man. Good luck with your bug report. But consider two things: Put things in relation to what major bugs in the F16 are still needed to be adressed and dont mistake your personal preferences or liking to how you want your plane to be set up as a bug. And consider a third thing. Lots of your the "bugs" can be solved by simply using the sync hotas at startup function. If you did so, you could have had a lot more time flying the jet compared to the time you have spent complaining. And as side effect you'd have all the functions you seem to want to have control over quickly accessible on your Hotas. My time is too short for that minor topic. My participation is over. I will again focus on testing and reporting bugs like incorrect JHMCS locking behavior, Incorrect uncage of the AIM9X seeker head, Incorrect NO RAD function and symbology of HUD and FCR, G modelling for the F16 pilot, FCR Look down penalty, DCS not modelling pre-emptive flaring, just to mention a few. Over and out.

This is really splitting hair and we have a lot of other issues in the F16 already that should be adressed first, before we discuss whats correct or incorrect for an airborne spawn. Please dont eat up the time and resources from ED on that, before all the other more important stuff is fixed and adressed. Just to begin with, how realistic is it that you spawn mid air in a jet?! If you did a "realistic" cold start, everything you were adressing should be set to your liking by yourself. Speaking of which is, for example, CAT I or III. Some real F16 pilots dont set it at all, because they dont like it, and JHMCS is the same thing. Other different example is the audible morse code if you fly over a TACAN station. Its realistic that it is on. But its annoying. So I did the exact same thing as moonshine. Just bound it to a switch on my throttle that turns down the volume on spawn. And in the F14 the gun is set to low and the master arm to off. Pretty annoying on a dogfight server. Bound it to the same two switches on the throttle, as for the TACAN sound, and enabling JHMCS, in the F16. Synced the controls on start, done. Saved time for people in the forum and for the ED developers.

I am not saying that this behavior is correct. I just assume it makes sense. But talking about the video from Gaffer the original poster is referring to, the procedure was as follows: Use HAD to slew the TGP (box) to the approximate position of the SAM. FInd the exact location of the SAM with the TGP. Create steerpoint. Then UNLOCK the SAM on the HAD. Use the HARM own POS EOM mode without the HAD which is working purely with steerpoints, as you can see in the post-launch HARM symbology on the HARM WPN page. HARM might be an exception. I am not too familiar with JSOW or JDAM. Maybe there is differences between them and HARM in usage which is causing confusion.

Related to this. Maybe merge threads?

You guys are playing too much 90ies sims with a target designator box on the ground. locking targets, as well as in the air the same way. But yes, related. And, I am not a pilot, but I'd assume this as correct. The Harm wants to go to the steerpoint. And the box with the bomb fall line is just CCRP symbology on top. Here is a video for illustration. See that the created steerpoint, its 28 in my case is represented by the diamond. If the TGP box is on top, the diamond disappears. See how I can move the TGP box with the CCRP bomb fall line around? Also note when I switch the steerpoint, and then back to STP28. Maybe you also try to do a CCRP tutorial, so this symbology will become familiar. Video:

Yeah I guess so. I think that was the way the kneeboard was meant to be used. In the real world you would not sit with your aircrafts manual in your knee pocket. If you'd need that, something went seriously wrong in your pilot training

Quick test here. I just created duplicates of my PNGs in the kneeboard folder to exceed 256 and it wont show more than about that number. I dont know the exact number beause it also loads the airport diagrams in , which add to the count. But, nope. Not more than about 250 pages. Tested in the F16. For me 30+ pages are enough, so I cant tell, but maybe this could help lowering the page count by sectionizing manuals as it shows on the start page. https://dcskneeboardbuilder.com/ Good luck

255 or 256 if the first page is 0 or 1. Do you fly in VR, so you need it on the kneeboard? If youre using a flat screen and track IR you could use some program like "always on top maker" to superimpose he PDF in a corner of the screen. ... of course not as convenient as a kneeboard, but if its a limitation I doubt that you can mod it.

Do you want to read a novel book while flying the Apache? 256 is not a random number in the digital world. ( 16 bit etc) I would not wonder if the pages count was clamped at a certain amount of pages.

Great news. Well that would be nice if we could get rid of the extra step of installing SRS for use in virtual squadrons. @BIGNEWYIf we get some kind of the "awacs mode" SRS offers for ATC Controllers and if it works with Lotatc too that'll be great. Not really sure what part SRS plays reading out squawk of the aircraft and sending it to Lotatc

Is it working with the aircrafts radio like SRS already? I mean like dialing in the UHF and VHF frequencies and youre done and read?!

I'm afraid I am not quite getting your question. Why did you not show your MFDs in the screenshot too? Hard to judge that way. What he does in his video he is using the HAD HTS to find the SAM site and create a steerpoint. You wont get a target designation box like in AA mode. What you might call a target designation box is when he used HAD to slave the TGP to the estimated position of the SAM site. The box is where TGP is looking. It will move with your TGP. As soon as the steerpoint is created the box can be wherever you want it to be, by slaving it around with the TGP. He uses the HARM without the HAD just in PRE EOM. So the HARM will fly to the selected steerpoint, no matter where the TGP or the box is looking. EOM mode is so precise you can just fire at targets that sit behind you. You just need to see that the carret is in the DLZ staple next to your altitude indicator in the HUD. EDIT: If you want to see something as a target designator box, it is the steerpoint diamond (in your screenshot) As long as the HARM is programmed on that steerpoint it will go there and look for the SAM type you selected in the TBL before launch.

Well, that was a detailled explanation from a professional Thanks @mbucchia

Looks like this is the one maxed out core

what about local dimming of the Pimax Crystal?

I am using DCS-MT. The ST test was just for comparison, and performance is much worse. Its the second part of the video. CPU frame times explode when using VR. Even with a high end PC. I hope for more MT optimisation from ED. Also interesting is that in MT if you watch fpsVR closely there is one Core that jumps up to full load. Whereas in ST there is no single core in full load.

Very interesting. So wait, what youre saying is that the radar cursor mini stick is force sensing like the F16 side stick too? Which means it does not move, or just little as the side stick? Are you a pilot or F16 maintainer and share some more insight?

Sure. But its the CPU frame time that improves drastically, which is the bottleneck on my system.

And its faster slewing Maverick seeker heads around, makes it really a challenge not to overshoot with the crosshair, while the speed on the TGP is slower. Dont know if this inconsistency in speed is realistic or not. But its impossible to assign an input curve to the mini stick / radar cursor that is convenient for all sensors.