Tj1376

Did this get snuck into the last open beta release? Post this latest patch, I noticed my testing for the F16 started failing the ammo depot again (where 2 GBU31v3 would not kill the ammo depot.) Someone then pointed out that no, I was wrong that you had to use GND fuzing (despite our previous conversation where this was not actually implemented.) Sure enough, loaded the F16 test back up, this time set it to GND and boom, 2 GBU31v3s destroy the ammo depot. I then also tested the inverse, and sure enough, 2 GBU31v3 in AIR no longer destroy the target. TJ

No. Satnav settings for blue are unrestricted. Basically someone once said "Russia will only be red" and a bunch of code was written around that. So once you put a non Russian airframe on red, you've gotta unrestrict satnav so the nato airframes on red can access the GPS data. You should have no issues following the same procedures on blue. But please confirm. TJ Sent from my SM-N970U using Tapatalk

Date doesnt matter - coalition choice does. If you happen to be flying RED, and unrestricted satnav is FALSE, your bombs are dropping via INS. You can also update this by just opening the mission in the mission editor, going to the checkmark on the left hand side (called 'mission options') and selecting both checkboxes for unrestricted satnav (enforce and value.) Then, save the mission file. Next, go to YOUR settings, go to gameplay tab, make sure unrestricted satnav is checked. Try again. Also edit, your steps are spot on accurate. Without being able to see your track (because your mission file requires some sort of mod), just verify you are flying red. Try flying blue and see if you have more success. TJ

In your mission, try turning ["unrestrictedSATNAV"] = false, to true and make sure in your game settings it is also set to true (by default its not selected.) It is located in Options > Gameplay page. In a single player mission, both the clients game settings AND the mission must have this value to true. I am unable to verify which color your AV8B is and I dont have the mods you have to verify or the time to decode the coalitions in your mission file.... But ["unrestrictedSATNAV"] = false, has caught many mission builders out and causes GPS bombs to drop with just an INS alignment which means they miss by just enough. TJ

Latest open beta Persian Gulf map Single Player (although reproducible in multiplayer as well) Scenario is one "Warehouses > Ammunition depot" unit - mission has both the Viper and the Hornet with GBU 31v3 (penetrating warhead) Fly to objective, release one GBU, do a jink, release 2nd GBU. (The jink is to make sure when the first GBU explodes it doesnt take out the 2nd GBU from splash damage.) Watch both GBUs hit target Expected Result: 2 GBU31v3's hit target - target destroyed Actual Result: Hornet - success (2 31v3s destroys the ammo depot) Viper - failure. It is inconsistent how many GBUs it takes, sometimes 7, sometimes 10, sometimes 9) Please review and advise, thank you for your dedication. TJ f18TwoGBUwithPenetratingWarheads.trk TenGBUwithPenetratingWarheads.trk

OK- im going to create a bug report. If you use the 31v3 on the hornet, it takes two to kill the depot. And while I thought you were wrong about the fuze settings, I even put the 31v3 on instant fuze in the hornet and still it only took two 31v3s to kill it. Really odd that the exact same weapon provides different damage values between the two platforms. TJ

hey @NineLine, I was going to file a bug report... Its taking anywhere between 8 and 10 gbu31s with penetrating warheads to destroy an ammo depot (the big bunker.) I think your response above basically says that the current fuze we have wont allow the GND DLY function to actually work, so even though I am selecting GND DLY, the fuze is triggering on impact and thus not penetrating. And then if I read between the lines, it sounds like the fuze is coming soon so this is probably WIP. Is that accurate? (so no bug report because this is WIP?) If you review the track below, ignore the terrible flying. I was in a hurry. Appreciate any feedback. TJ TenGBUwithPenetratingWarheads.trk

From his post - i cant figure out the quote system here when trying to go from one thread to another. This is his work, not mine: Hi guys, I have just done another climb test with the latest flight model update. The results are very interesting! The original test was this and I have added the latest figures in BLUE: Reading in the NFM-400 performance manual you get the following data for a climb with these conditions: Engine = 408 Drag Index : 17.7 GW at start of climb : 22,000 lbs (7200 lbs of fuel) CLB Speed : 300 KCAS / .75 M Max thrust climb, this is 109% / 710 degrees C JPT for the -408 engine Test carried out in ISA conditions, winds calm EXTRAPOLATED DATA FROM THE CLIMB CHARTS VS DCS : TIME TO CLIMB - DCS - NEW FM / FUEL REMAINING - DCS - NEW FM / DISTANCE - DCS - NEW FM SL to 10,000 ft = 0:48 mins / 0:25 / 0:35 / 7040 lbs / 7094 / 7016 / 3.5 nm / 2.5 / 3.8 SL to 20,000 ft = 1:42 mins / 0:54 /1:27 / 6850 lbs / 7010 / 6855 / 10.5 nm / 5.1 / 9.1 SL to 25,000 ft = 2:30 mins / 1:13 / 2:04 / 6770 lbs / 6967 / 6771 / 16 nm / 7.1 / 13.2 SL to 30,000 ft = 3:24 mins / 1:35 /2:57 / 6660 lbs / 6922 / 6671 / 24 nm / 9.6 / 19.8 SL to 35,000 ft = 5:00 mins / 1:56 / 4:25 / 6580 lbs / 6881 / 6545 / 32.5 nm / 12.0 / 30.1 SL to 40,000 ft = 7:34 / 2:24 / 7:46 / 6430 lbs / 6836 / 6363 / 53 nm / 15.3 / 54.4 Comparing the BLACK figures to the BLUE figures Razbam have done a really good job at making the flight model more in line with what NFM-400 says is possible. The fuel burn in particular is very accurate as is the distance. Unfortunately I know the FM change may annoy some people out there that were enjoying the really powerful engine/low drag FM. On the positive side, the overhead break has become more realistic and doing a VNSL is also much better now. TJ

you leave ground chocks in? Gotta remove em first... TJ Also- did you see this thread? TJ

OK, I am plum out of ideas. Prior to the latest 2.7 patch, I could easily deploy walleyes on target without any issue. See example here, showing an attack of a ship with the walleye: https://drive.google.com/file/d/1WFTS51rT5AYQIuN4Qx4hTLUU3yhIulyC/view In the good example (above), notice that the WE symbol in the hud the moment you select walleye is unboxed (indicating the walleye can be released whenever you depress the weapon release button.) Post this latest patch, now I am having issues with WE unboxing in the HUD (and thus the walleye wont release:) https://drive.google.com/file/d/1L9qwt4HWRUujCETmUIBuq6k84ksUHabv/view?usp=sharing Are there any tips here on why WE is not unboxing in the HUD (what parameters are not in check for weapon release?) I'd like to be able to modify my approach to make this work, but am stumped. Any help is appreciated. TJ

I got back into the viggen today now that the hotpatch has fixed the CTD in multi-player. Man I've missed this plane. Nothing is more fun than planning your route in, popping up, dropping ordinance and getting back to the deck while the ground units attempt to fire at you. A very specialized airframe indeed. But learn how to master its specialty and the rewards are very gratifying. TJ Sent from my SM-N970U using Tapatalk

Yep, i just spawned in on Hoggit and can confirm its now fixed!! TJ

Any of you copy your modules over from somewhere else? About three weeks ago I ran into an issue where win10 wouldnt boot and I couldnt repair. Had to do a fresh install of win10. Get win10 setup and download DCS beta... After downloading my favorite airplanes from the module manager, I got irritated at the time it was taking to download everything. Found a really cool solution to go to the windows.old directory (from my previous win10 installation) and pulled the terrains out of OLD win10 installation and copied them to the fresh beta install. Everything worked (I was amazed at all the time I saved from downloading the maps!) But then after update, I ran into this issue Im wondering if maybe some of you did something similar? TJ

I deleted the failing modules and redownloaded them and I am back in business. May work for you too. TJ

I am also having the same issue, just with different modules. Post the update to 2.7 I see the following in my log: 2021-04-14 21:37:41.850 INFO NET: Login success. 2021-04-14 21:37:42.703 INFO NET: Got auth data. 2021-04-14 21:37:43.037 INFO DCS: Successfully got authorization data. 2021-04-14 21:37:43.045 INFO Dispatcher: Loading installed modules... 2021-04-14 21:37:52.305 INFO Scripting: plugin: SKIPPED 'F-15C': disabled by 'Flaming Cliffs by Eagle Dynamics' 2021-04-14 21:37:53.742 INFO Scripting: plugin: SKIPPED 'MiG-29 Fulcrum by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics' 2021-04-14 21:37:53.781 INFO Scripting: plugin: SKIPPED 'Su-27 Flanker by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics' 2021-04-14 21:37:53.782 INFO Scripting: plugin: SKIPPED 'Su-33 Flanker by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics' 2021-04-14 21:37:53.802 INFO Scripting: plugin: SKIPPED 'Nevada': not authorized 2021-04-14 21:37:53.802 INFO Scripting: plugin: SKIPPED 'PersianGulf': disabled by user 2021-04-14 21:37:53.803 INFO Scripting: plugin: SKIPPED 'Syria': not authorized 2021-04-14 21:37:54.065 INFO Scripting: plugin: SKIPPED 'A-10A by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics' 2021-04-14 21:37:54.081 INFO Scripting: plugin: SKIPPED 'Su-25A by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics' (I disabled Persian Gulf and relaunched, then enabled it and relaunched to see if that would kickstart DCS. No bueno) I did want to add that I do have plenty of successful authorizations - so its not a problem with clock, etc... All of my other modules work great. Just these modules (listed above) do not. TJ

I misread your post. #ignore TJ Sent from my SM-N970U using Tapatalk

I wonder if dcs server has anti cheat systems that review the UDP traffic and if anomalies are found it terminates the servers UDP to the specific client it believes is cheating. I would imagine getting out of order UDP packets would be a great way to cause warping, which would sure make it hard for an attacker to hit you. This dropping of UDP due to best effort routing (no QoS) would look exactly like this. We may not have to test. Just ask the netcode team if such a feature exists. If you get a solid confirmation, then the netcode team just needs to identify why the bursting of UDP occurs on the Syria map to resolve the problem (no need to respond here, as we dont want to tell cheaters how the anticheat systems work.) TJ Sent from my SM-N970U using Tapatalk

Hey@Flappie ! No. QoS resolved the issue. I analyzed the traffic flow of the router (a nearly 10 year old but very high end Netgear router.) With extremely high unit counts you can see bursting of UDP traffic in sporadic spots. This behavior is only seen on the Syria map. The theory is that the bursting of traffic was causing the older router to not process all of the traffic. And while UDP is designed to come in any order and can be lost, it appears that DCS does not follow that standard. Somewhere during the bursting the DCS server doesn't receive the right UDP packet and the DCS server stops communicating with the client via UDP only (TCP is not impacted which is why the f10 map allows you to chat and you can see missiles and player deaths.) Two minutes after the dcs server stops sending udp, the connection is terminated and the user gets a ping timeout warning. I have a sneaky suspicion that the engine Netgear uses in its routers are prone to this. Setting QoS is telling the router to stop "best effort" routing and it stops dropping UDP during the bursting. Most of the above is my speculation based upon Wireshark analysis and ping plotter tracking to the dcs server. In real life, I've spent nearly 15 years in troubleshooting network and applications in a large scale and global organization, you learn a thing or two. :) If you ever want to setup a test to prove the theory, im all ears and have several recommendations. But we need a server, a Wireshark installation and a mission file that has scripting and high unit count. I recommend BlueFlag Syria modern mission for this from xcom. :) TJ Sent from my SM-N970U using Tapatalk

Do you know the procedure for this? I saw this yesterday and thought - must be a neat way to update the coordinates and then redo the alignment to improve accuracy but I was unable to figure out how in the middle of a few sorties on Blue Flag last night. TJ

It just changed with one of the most recent patches. Im a long time flyer of the JF and even I missed it last night during a sortie. Also, dont forget to turn HNS (button located on the UFC) on and set it to INS + GPS as drift is now modeled and will effect (affect?) the precision of the weapons. TJ

Environmental is not on by default - it must be turned on during startup. If you forget to turn it on, you will overheat the MFDs and they will start to act strangely. TJ

I second this. Seems to have appeared with the hotfix to the previous open beta. Now I notice the throttle also disappears when you hide the stick, which is awesome. But the click spot on the throttle is now gone. :( Admins, please move thread to bug reports if it is indeed a bug. TJ Sent from my SM-N970U using Tapatalk

so um, how do we fix it now that its actually drifting. Seems to be impacting INS weapons. TJ

caution light panel on your right knee has a light for when the speed brake is extended. TJ

I really appreciate thr rb75 fix as several multi-player servers banned it awhile ago because of the cringe worthy performance. Thanks HB! TJ Sent from my SM-N970U using Tapatalk