-
Posts
3173 -
Joined
-
Last visited
About Tholozor
- Birthday 03/24/1990
Personal Information
-
Location
Georgia, USA
-
Occupation
General Aviation Line Service Technician
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Countermeasures are loaded through the data cartridge function now. Editing the lua is no longer required.
- 1 reply
-
- 1
-
-
Specifically, aircraft system in since generator power-up, displayed in minutes and seconds (MMSS). Only displays with weight-off-wheels.
-
correct as is Unknown HUD symbol after cold start.
Tholozor replied to Moxica's topic in DCS: F-16C Viper
Is it the same reticle as this? -
Have you tried inverting the brake axes?
-
AFAIK, the 300ft metric is applicable regarding horizontal position error. ACAL for vertical error provides either GPS-only, DTS-only, or BOTH options for vertical position (BOTH being the default, and the MMC picking whichever of the two is more accurate based on specific parameters). ACAL-provided vertical position error shouldn't ever be more than 100 feet from what I'm reading (unless a system has failed).
-
F-16 Waypoints off by 20nm after 1 hour flight?
Tholozor replied to MeanJim's topic in DCS: F-16C Viper
Looking at the first screenshot, you forgot to Cursor Zero (denoted by the CZ option on the HSD). -
Radar in any RAID mode - are max and min range values wrong?
Tholozor replied to Razor18's topic in Bugs and Problems
I concur with Razor's findings; in SCAN RAID, the L&S should be centered on the scope, which becomes a 10nmi by 22° field. The max range value is incorrectly adopting the L&S range. The scale of the scope in SCAN RAID scope is correct, just offset by 5. -
AGM-154A JSOW-A wind-correction does not account for bomblets
Tholozor replied to Northstar98's topic in Weapon Bugs
Interesting, I thought that had been addressed in this patch: https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.15.9408/ Maybe the problem is more-so dependent on the amount of wind. -
Correct, check the description.lua and ensure the filenames match.
-
Looks like either the normal map or roughmet textures in the description have a typo.
-
Gunsight still WAY off after IHADSS Boresight
Tholozor replied to brettt777's topic in Bugs and Problems
Keep in mind that Auto ranging only uses the radar altimeter and helmet angle to determine slant range, so if the elevation of the ground below you and the target are different, the ballistic calculation will be off (Early Access Guide pg. 311). Utilizing the WAS on the CP/G's cyclic also automatically invokes MAN RNG; setting it Auto only applies after a weapon has been actioned, and isn't a permanent toggle. -
Gunsight still WAY off after IHADSS Boresight
Tholozor replied to brettt777's topic in Bugs and Problems
You have to align the IHADSS crosshair with the center of the rings in addition to ensuring all rings are visible and centered in the unit. Also keep in mind the CP/G's default Manual Range is set to 3000 meters. -
Correct. When you press the SEQ option on the HSI, it goes from SEQ1 to [SEQ1] (boxed), then the same for SEQ2 and 3, then back to SEQ1 on a loop. Doesn't matter if a sequence is empty, pressing that button will always cycle through sequences, as that's also how you select a sequence for programming.
-
Think of Sequences like routes. If you're familiar with the F-16's steerpoint allocations, it's like steerpoints 1 through 20 for the navigation route. With the Hornet, however, you can create three different routes using any waypoints in any order. When a sequence is boxed, the avionics assumes the intention is to navigate to those waypoints (possibly automatically and/or if coupled steering is desired). Since the Hornet has no way to edit waypoints in the cockpit without first selecting them for command steering, the only waypoints that can be scrolled through when a sequence is boxed are the ones inside that specific sequence, otherwise you could end up inadvertently steering to a waypoint outside the desired sequence. Regarding markpoints, those exist outside the standard 60 waypoint (0 through 59) allocation, and therefore cannot be selected when a sequence is boxed.