Search the Community
Showing results for tags 'investigating'.
-
Hi, Running a test to investigate the issues trying to maintain on-speed during turns in not-auto flaps up operation, I noticed the following: 1. Started test by setting on-speed (~152 KCAS) 2. Entered turn, applied aft stick input up to maximum (limited to 3.55 inches aft in not auto flaps up logic, and also to a ~70% of travel in DCS) 3. Noted that pitch stick command and pitch trim bias allow to pull up to ~14º AOA (stab deflection up to 24º teu). All within expectation. 4. Accelerated to ~230 KCAS, trim untouched, entered turn attempting to capture on-speed. 5. Max pitch stick command won't achieve the previously trimmed 8º AOA, max resulting stab deflection is now only 6º teu. 6. Finally, accelerated to ~243 KCAS to force transition to auto flaps up logic. On transition, noted big AOA and pitch rate spikes as the FCS command transitions between 6º teu and up-to-24. (Note that these spikes will also happen in case of only applying the ~70%/3.55" stick limit mentioned above, and smaller deflections too -- this is not in the attached track, where I used full deflection, but the result will be similar) I'm unsure of what exactly is wrong here. The pitch stick command, trim bias, and aircraft sensor feedbacks are scheduled by airspeed in not-auto flaps up operation, and the gains and limits may benefit from some tuning. I couldn't find a reference to the 6º teu limit observed above at higher speeds anywhere. The aircraft seems to have very little pitch authority in the above test conditions with the current gains. I'd appreciate if you can run this report by your dev team FCS expert, as this particular test case may have slipped through them. FCS_PA.trk
-
I found that there was no difference between HI and LO in the gun's rate of fire settings in air-to-ground mode. (I know its fire sounds are same). In the original HI mode, it takes 5 to 6 seconds to consume all ammo, but in air-to-ground mode, it takes 8.6 seconds for both modes. However, it works well in AA mode. is this normal?
-
As per the thread tittle. It seems to randomly lose handed off target. EDIT: it is not related to hemisphere change, thus the edit. Added second non-maneuvering track where it also happens. Hornet_TOO.trk harm-nonmaneuvering.trk
-
investigating Possible to enter impossible ACM scan mode.
Rissala posted a topic in Bugs and Problems
To reproduce: -switch to guns -go BST -then go vertical scan -then switch to AIM7/AIM-9/AIM-120 -observe that the GACQ scan pattern is on the HUD even with missiles selected and that the radar is doing a weird scan pattern with almost +-90 deg scans ACMpattern.trk -
investigating Loosing lock in ACM sometimes exits ACM submode
some1 posted a topic in Bugs and Problems
If you lock a target with VACQ or HACQ, then after loosing lock the radar is back in ACM VACQ or HACQ respectively. But if you lock a target with WACQ or BST mode, then loosing radar lock kicks you out of ACM back to RWS. Seems inconsistent. ACM lock.trk- 1 reply
-
- 3
-
-
What it currently looks like in a vehicle. No amount of tweaking can make this look like anything decent or even remotely resembling a modern-day MBT's thermal imaging package. And what's up with our binoculars now? There was a very brief period where we had decent thermals for vehicles but that time has long passed. We've been stuck with this for ages! It's awful and un-usable!
-
For a while now I've felt like the mil power performance of the F-16 was a little low, though I chalked it up to the DCS version being Blk 50 as the GE engines favor AB over dry thrust. However I did finally get around to do some testing and it looks like there is a lack of thrust/overprediction in fuel flow even taking into account the F110's. I have tracks attached, though due to forum rules I am not posting the source info. I can send it via message. Summary of the issue: Testing at DI 102 at 34015 lbs weight to compare to data at DI 100 at 34000 lbs weight DCS shows increased Delta between speeds when accelerating under full mil power. This not only impacts acceleration, but climb and cruise, so the F-16 has a harder time getting to optimum altitude and uses too much fuel when cruising. DCS fuel burn at 510 knots is approximately 4200 PPH while the actual value should be just under 3900 PPH. Ideally some more testing is needed to see if this is more of an engine issue or drag issue, and it should be tested at more speeds, altitudes, and weights, but the condition that I did test is an important one as it's relevant to the F-16 in a CAP role. F-16CFuelFlow_35000FT_102DI.trk F-16CMilAccel_30000FT_102DI.trk
- 9 replies
-
- 10
-
-
-
At mission start the AI Harriers should be heading north as per the not locked.miz. After making some changes I saved the mission and in all subsequent saves the AI Harriers all face south but show a path of 05 degrees in the F2 view. This mission actually has 60+ triggers so has a huge amount of work gone into it....and it's ruined as the aircraft have to start facing north. Is there a way to fix this? Harrier Locked.miz Harrier not locked.miz
-
Hello does anybody know is there is currently any bug causing the laser to not fire or if I am doing something wrong. I have been trying for almost a week to get the laser and hellfires to work. I have read them manual and watch just about every video on YouTube trying to get this figured out. I am in cpg seat, ihadss is boresighted (dont know if that matters or not for lasing with the hellfires) using tads on manual track, missile is was'd and armed I have used both fxd and ghs, the LRFD and missile are on the same channel and the Laser is turned on in the utility tab but when I press the LRFD second or first detent nothing happens at all no new symbology no constraints messages nothing. I have managed to get everything to work right 3 times but about 95% of the time nothing happens. I am starting to think it might be bugged as I have followed multiple tutorials on the topic step by step with no success. Any help would be much appreciated.
-
Hello folks, I noticed a mistake regarding the cockpit textures of the F-16C. In the zip folder "F-16C-CPT-TEXTURES.zip" there are these three main files for the seat: f16c_cpt_seat_NRM.dds f16c_cpt_seat.dds f16c_cpt_seat_RoughMet.dds Unfortunately, the normal map "f16c_cpt_seat_NRM.dds" is not loaded. It is also not possible to manually assign the normal map to the livery file. I suspect that the model was not exported correctly. Can someone please take a look at the problem? Many thanks in advance. Cheers Homelander -
.thumb.jpg.4bdd9821192c10235482cd93c5541168.jpg)
Subject. I do not have any real data, but these oscillations look and feel weird when doing a basic crank maneuver. Oscillations are less violent when you are slower. Added: on 0.9M it feels nice and smooth. I think the current FCS implementation can't keep up on 1.4+. Have added second track with full stick deflection. F-18-oscillations.trk F-18-oscillations2.trk -
I'm using the following in my ATIS script local weather = env.mission.weather local cloudCover = api.TUC.GetCloudCoverAsString(false) local cloudBase = api.TUC.MetresToFeet(weather.clouds.base) local thickness = api.TUC.MetresToFeet(weather.clouds.thickness) local visibility = weather.visibility.distance local fogThickness = api.TUC.MetresToFeet(weather.fog.thickness) local fogVisibility = weather.fog.visibility local dustDensity = api.TUC.MetresToFeet(weather.dust_density) Everything looks okay except that the THICKNESS which I'm led to believe from the documentation on hoggitworld is for the lowest cloudbase, ALWAYS reports the same amount of 656ft, regardless of the weather preset used and how thick the cloudbase is to fly through. Am I using this correctly or is this a bug? Cross posted in the Weather System bug list just in case it's not a scripting error. -
investigating Radar can still lock targets while off
Maverick806 posted a topic in Bugs and Problems
The F-16Cs radar can acquire targets when NO RAD is displayed on the HUD and HMCS The simplest way to test is: Enter Dogfight Override Mode Press TMS FWD to enter BORE mode Press and Hold TMS FWD - Note HUD and HMCS both say NO RAD. Hold the HMCS Cross over a target within range for a couple seconds. The radar will lock the target while you're still holding TMS FWD. This causes issues if you're trying to lock a specific target out of a group and the radar just grabs the first one it passes over This even works if your F-16 is on the ground (although the radar stops tracking immediately) F16_NO_RAD_Ground.trk F16_NO_RAD_MultiTarget.trk F16_NO_RAD_SingleTarget.trk -
Hi, I was trying to make a mission that had a sort of automated/AI Navigator, my idea was that at some point at the start the Navigator would set up the Direction finding radio. The problem is that when you are occupying the pilot seat, some switches/controls are not available to you, eg the power switches for the Navigation radio, and the navigation radio itself. This also carries over when you try to script these actions in the mission editor, the actions are not completing because I am in the pilot seat. I would like to see at least the scripted actions being able to complete without changing seats, possible? Thanks
-
I'm having a problem with this mission. All the triggers seem to be working from taxi, takeoff, and departure but I can't seem to figure out why none of my wingman are taking off to help me? I flew all the way to sally and didn't see one jet take off or ask for taxi. Including my wingman who said he was ready to taxi. Is this a bug with one of the vehicles blocking an aircraft? The briefing has them as starting up their jets, just not taxing, so this would explain it. Any input or advice would be greatly appreciated.
-
For some reason, after completing the A/G tasking and you are told to hit the tanker before RTB, seems like the script stops working. I'd get told to switch to the tanker freq, then absolutely nothing. I rejoin and do normal tanking, but no triggers or radio calls. The wingman doesn't tank. I had to skip the mission to advance because I flew the long mission three times and experienced the same issue.
-
As the title says, after echo 3 calls for help and you say you can help it says to contact warrior for the nine-line. Tried using every channel available (142.3, 255.5) but he doesn't respond. -
Hi, Just finished for the second time, raven one and decided to jump to this new set of mission. A bit disappointed because it seems that i could not have cajun move from the tanker...so i could not refuel myself. Not enough fuel for the case III recovery with everyone... I missed something or AI messing up again ?
-
Hey, Apologies if this has been reported already, but I did a search and didn't find this one: Following screenshot is taken from the Fighter Intercept Instant Action mission. The AI wingman seems to fire AMRAAMs from station 1 and 9 even when stations 3 and 7 still have some loaded. Should this not be the other way around (because of flutter), such as with player-controlled F-16s? Thanks! -
Hello All. I believe I have found a error in the scheduling for the FCS. As you will see in the track I provided, performing the loop when I achieve less than or equal to 270kts, I immediately loss a G. Then on the backside of the loop after hitting around 360kts, the jet added the G back. At first I thought this was just due to the alpha ramping up and down but I was incorrect. I decided to do a horizontal turn to confirm my theory and yes, after 270 knots decelerating I noticed a drop in G and alpha. You can see this in the track. I have shown my controls indicator to show that I am not moving the stick at all during this test. Now what leads me to think it is a scheduling error is that if I speed up over 270kts but do not exceed 360kts, it does not have this weird behavior. My guess is that there is a hard edge in the schedule which is causing a rapid transition. I could be wrong about it being a scheduling error, but it's a starting place to investigate. Cheer's, Panic Hornet FCS Schedule Bug.trk
-
Our current Auto Flap Up FCS implementation is using sideslip feedback to control the rudder, which I consider as a bug, because the feedback is erroneously applied to the rudder rather than to the aileron and differential stabilators. The sideslip and sideslip rate feedback should be fed to the aileron and diff-stab above 20 deg AOA, as in FCC OFP v10.7 IRL. For now, I'm seeing rudders move with sideslip changes even if AOA < 20°. Test procedure: 1. Set an extremely turbulent weather. 2. Flaps to auto. 3. Press F4 to get a closer look at the rudder 4. Check if the rudder is moving with turbulence/sideslip changes. Use active pause so that there's no lateral acceleration and yaw rate interference to the rudder. Test with AOA below or above 20 degrees. References: 1. Park, David J., "Development of F/A-18 Spin Departure Demonstration Procedure with Departure Resistant Flight Control Computer Version 10.7. " Master's Thesis, University of Tennessee, 2004. https://trace.tennessee.edu/utk_gradthes/2312 2. Mitchell, Eric John, "F/A-18A-D Flight Control Computer OFP Versions 10.6.1 and 10.7 Developmental Flight Testing: Out-of-Controlled Flight Test Program Yields Reduced Falling Leaf Departure Susceptibility and Enhanced Aircraft Maneuverability. " Master's Thesis, University of Tennessee, 2004. https://trace.tennessee.edu/utk_gradthes/2372 3. Simulation Model of a Twin-Tail, High Performance Airplane, NASA TM 107601, including a set of FCC OFP v10.1 block diagrams (https://ntrs.nasa.gov/api/citations/19920024293/downloads/19920024293.pdf) 4. NATOPS manual which is not quoted here but contains relevant info. According to the Directional Auto Flap Up CAS block diagram from reference 3, there's no sideslip or sideslip rate feedback in v10.1 as there was no sideslip measurements available to the aircraft. The feedbacks were only included in v10.6.1 (a test version of 10.7) and v10.7, together with the sideslip estimator. From reference 2 describing the sideslip estimator: From reference 1 describing the sideslip and sideslip rate feedback: Also from reference 1: Hronet rudder moves with sideslip.trk -
reported S-300 Missile Flight Path Issues
Shadow KT posted a topic in Ground AI Bugs (Non-Combined Arms)
When defending against HARMs (I suspect the result will be the same against other weapons as well), the SA-10 consistently flies its missiles substantially higher than their target. Meaning the SA-10 missiles arc high, when engaging incoming AGM-88Cs (difference between missiles and target altitude increases with range). The delta can be in the tens of thousands of feet. I've attached two tracks (with stationary and mobile radars), as well as an example Tacview file. SA-10 Miss High #1.trk SA-10 Miss High #2.trk Tacview-20231118-173404-DCS-VX NTTR .zip.acmi
- 20 replies
-
- 1
-
-
- investigating
- s300
- (and 1 more)
-
So the S300 detection/tracking range is still very low...at my example it detects a F16 at ~30k ft, Mach 1,7 only at 22km and engages at 18km an that over bone flat terrain..the patriot SAM for comparison detects and engages the F16 at 52 km regardles of skill level....something seems still wrong here with the S300 Performance. S300 detection attack at 18,4km.acmi S300 low tracking distance.trk patriot SAM.trk -
99% of people won't notice this but see screenshot.null
-
I ran into this issue working on another mission, then made this simple mission as a test to verify the problem, and the problem persisted. I asked a buddy to check it out and it was happening for him, as well. The mission has 10 aircraft in it, each with their own DL IDs. When you load into any slot and go to the MBR DIR to add other members to a preset group, you should see 2 pages of members; 8 on the first page, and 2 on the second page. Instead, you only see one page available, showing you 8 members. The last 2 members would be on page 2, but there is no option to flip to page 2. If you add an 11th aircraft to the mission and try again, you get the option for the 2nd page, and it contains 3 members, as it should. The same problem repeats itself if there are 17-18 aircraft in the mission which should overflow to 1 or 2 members on a 3rd page, but the page is not available. Mission is attached for testing. Data Link MBR DIR Test.miz
