Teetwo

I did some more testing and it's not just the Hornets that have gone crazy but all the none AI aircraft. If I use any pay module as AI they don't act right.

I have noticed the something and actually came looking to see if anyone else had encountered it too. It's good to know its just not my AI that have gone crazy.

I don't think those are the server specs but rather computer specs needed to play the game. The dedicated server module does not require an integrated video card.

If I understand you correctly, you want to build a template in the mission editor, save it. Then load that template into another mission. If that's correct this might help. https://youtu.be/wBu0Dnj1Zaw

+ 2

I would like to see some night ops.

I know I go from a steady 80fps with everything maxed out in 4K to a steady 20fps as soon as I turn it on. The strange thing is that to my old man's eyes I could not see a difference with it on or off. I have not tried it in VR yet.

I truly hope we see something along the lines of the super carrier for the Tarawa.

You guys ROCK!

Very nice, thank you.

It was my understanding that Heatblur was not doing any more modules for DCS. I truly hope I’m wrong about that.

+1

Hi, I'm trying to implement the carrier script that Wrench put together [ https://forums.eagle.ru/showthread.php?t=213662 ] but I and it seems like a few others have run into an issue where the menu options are not showing up pilots in multiplayer. They work just fine for those same pilots in single player but not on a server. I was hoping someone might be able to help me sort this out because Wrench has done a really outstanding job with this script and I would very much like to bring it to my squadrons multiplayer server. Thanks in advance.

Still waiting

You might be interested in some of the info in this thread https://forums.eagle.ru/showthread.php?t=213774

Thanks, but maybe a little more info on where to put this for pilots like me who do not know.

Discord keeps asking to join :(

beyond-visual-range (BVR)

This might help

Thanks, FIX. It does look like there is a mistake in the KC130.lua file that's causing the issue. I appreciate you pointing that out. An integrity check is not necessary on our squadron server so we might be able to fix this by manipulating the lua file but, I'm hoping maybe someone from ED will see this and fix it officially. I found some pretty good info on the subject. Specifications Primary function:In-flight refueling; tactical transport Manufacturer: Lockheed Power plant: Four Allison T56-A-16 engines Power: 4,910 shaft horsepower per engine Length Aircraft: 97 feet, 9 inches (22.16 meters) Cargo compartment: 41 feet (12.49 meters) Width of Cargo compartment: 10 feet, 3 inches (3.12 meters) Height Aircraft: 38 feet, 4 inches (11.68 meters) Cargo compartment: 9 feet (2.74 meters) Wing span: 132 feet, 7 inches (40.39 meters) Maximum takeoff weight: 175,000 pounds (79,450 kilograms) Ceiling: 30,000 feet (9,140 meters) Speed: 315 knots (362.25 miles per hour) Operating weight: 83,300 pounds (37,818 kilograms) Total fuel capacity: KC-130T and KC-130: 13,280 gallons (50,331 liters)/86,320 pounds (32,715 liters) KC-130F: 10,183 gallons (38,594 liters)/ 66,190 pounds (25,086 liters) Range Tanker mission: 1000 nautical mile (1150 mile) radius with 45,000 pounds of fuel (20,430 kilograms) (KC-130R/T) Cargo mission: 2875 nautical miles (3306.25 miles) with 38,258 pounds (17,369 kilograms) of cargo (KC-130R/T) or 92 combat troops or 64 paratroopers or 74 litters Landing distance: Less than 2,600 feet Crew: 2 pilots, 1 navigator/systems operator, 1 flight engineer, 1 first mechanic, 1 loadmaster (total of 6) Introduction date: KC-130F: 1962 KC-130R: 1976 KC-130T: 1983 Unit Replacement Cost: $37,000,000 Inventory Active: 37 KC-130Fs and 14 KC-130Rs (51 total) Reserve: 24 KC-130Ts [As of December 1995] he KC-130 is a multi-role, multi-mission tactical tanker/transport which provides the support required by Marine Air Ground Task Forces. This versatile asset provides in-flight refueling to both tactical aircraft and helicopters as well as rapid ground refueling when required. Additional tasks performed are aerial delivery of troops and cargo, emergency resupply into unimproved landing zones within the objective or battle area, airborne Direct Air Support Center, emergency medevac, tactical insertion of combat troops and equipment, evacuation missions, and support as required of special operations capable Marine Air Ground Task Forces. The Marine Corps' inventory of KC-130s contains primarily F-variants, which are approaching 40 years of age, and there were concerns that plans to replace the aircraft with KC-130Js might result in a shortfall of 15 aircraft as early as 2001. The active KC-130F/R fleet comprises 45% of DoD rotary wing aerial refuelers. However, the fleet will probably be unable to support the increased missions warranted by the MV-22 when fielded. Further, the fleet is deteriorating faster than the replacement aireraft, KC-130J, is scheduled to be fielded. The inventory requirement for the aircraft was previously established at (79) airframes, however as of March 2001 there were only (77) airframes, with availability continuing to decrease due to fatigue, corrosion, and obsolescence. Between 1994 and 2001 five airframes were stricken for corrosion, with one additional airframe pending a decision as of early 2001. At the current rate of airframe attrition, the Marine Corps will need at least four KC-130J's per year to maintain the Inventory. The current fleet has some Congressionally mandated programs, to include: GPS, GPWS and TCAS. There are several pending Safety / Enhancement programs, however, the required modifications will lead to excessive out of service time and reduced availability. The average fleet squadron has only five "up" aircraft on any given day (PAA 12). Studies have found that squadron cannibalization rates have increased 57% in order to support current readiness figures. The KC-130 is a multi-role, multimission tactical tanker and transport aircraft, well-suited to the mission needs of the forward-deployed Marine Air-Ground Task Force (MAGTF). The Hercules is the only long-range assault support capability organic to the Marine Corps. This aircraft provides both fixed-wing and rotary-wing tactical in-flight refueling; rapid ground refueling of aircraft or tactical vehicles; assault air transport of air-landed or air-delivered personnel, supplies, and equipment; command-and-control augmentation; pathfinder and battlefield illumination; tactical aeromedical evacuation; and search and rescue support. The KC-130 is equipped with a removable 3,600 gallon (136.26 hectoliter) stainless steel fuel tank that is carried inside the cargo compartment providing additional fuel when required. The two wing-mounted hose and drogue refueling pods each transfer up to 300 gallons per minute (1135.5 liters per minute) to two aircraft simultaneously allowing for rapid cycle times of multiple-receiver aircraft formations (a typical tanker formation of four aircraft in less than 30 minutes). Some KC-130s are also equipped with defensive electronic and infrared countermeasures systems. Development is currently under way for the incorporation of interior/exterior night vision lighting, night vision goggle heads-up displays, global positioning system, and jam-resistant radios. The KC-130 has 2 drogue equipped refuelling stations, one mounted on each wing outboard of the engines. Each refuelling station consists of a Sargent Fletcher 48-000 refuelling pod, 26 m (85 ft) of hose, MA-2 coupling and a 1.2 m (27 in) diameter high speed fixed-wing or 2.4 m (54 in) diameter low speed helicopter paradrogue. Helicopters may not refuel from a high speed drogue. Fuel flows when the hose is pushed in 1.5 m (5 ft); flow continues provided the hose is maintained in the refuelling position, between 6 - 24 m (20 - 80 ft) of hose extension. Hydraulic pressure provides 90% of the force required to rewind the hose during refuelling to reduce hose slack and whip. The hoses are marked each 3 m (10 ft). The MA-2 coupling requires 140 ft lb of pressure to make contact (2 - 5 kt closure) and 420 ft lb to disconnect. The aerial refuelling system is comprised of two independent Sargent Fletcher SF300 refuelling systems. These systems currently are used on the wings of KC-130F/R/T aircraft. Each system includes a 93-ft long hose. In full trail position, the hose extends 80 ft from the point at which it exits the aircraft to the drogue tip. The white refuelling hoses have black markings that designate the refuelling range and provide hose movement cues. The two reels are installed side-by-side and cannot be used simultaneously. The reels are hydraulically powered and operate independently, allowing for a redundant capability. The air-to-air refueling [AAR] height band is from 500 ft to 23,000 ft; speed range for the high speed fixed-wing drogue is 200 to 250 KIAS and for the low speed helicopter drogue is 105 to 130 KIAS. Maximum hose extension/extraction speed is 120 KIAS. Total fuel loads are normally up to 32,660 kg (72,000 lb), with an overload weight of 39,460 kg (87,000 lb). Transferable fuel is dependent on sortie duration; around 18,140 kg (40,000 lb) is available for transfer during a 4 hr flight, assuming a fuel burn rate of 2720 kg/hr (6000 lb/hr). With the removable fuselage fuel tank fitted, transfer rate is about 1850 kg/min (4080 lb/min) with the 2 AAR pump configuration or 925 kg/min (2040 lb/min) with the single AAR pump configuration. Without the fuselage tank, the transfer rate is about 460 kg/min (1020 lb/min). The lower transfer rate can be selected on request. Red, green and amber lights are located on the trailing edge of each AAR pod; these are AAR pod status lights. The light signal commanding a breakaway is the tanker's lower rotating beacon being switched on. Before a receiver is cleared for contact, the beacon is turned off to indicate the tanker's AAR checklist has been completed. AAR during EMCON constraint requires additional light signals from the tanker; these are provided by hand held ALDIS lamps. These lights will be seen in the paratroop door windows located at the rear of the fuselage on both sides of the aircraft. A steady light signals clear for contact; while in contact, a steady light signals disconnect. A flashing ALDIS means no more fuel available or the tanker is experiencing difficulties. Receivers should disengage and move to a position outboard of the hose. Drogue illumination is provided by refuelling lights located on the outboard leading edge of the horizontal stabilizer. There are 6 equally spaced luminescent paint spots are on the drogue to assist during night operations. The C-130 is 80% employed in the air-to-air refueling mission and 20% in the logistics mission. The air-to-air refueling capability enables a theater based day/night in-flight refueling capability for both tactical fixed wing (i.e., F/A 18's, A/V-8's, etc.) and rotary wing (i.e., CH-53's, CH-47's, MV-22's, etc.) aircraft through a pod mounted hose and drogue system located on each outboard wing station. A removable cargo bay fuel tank provides an additional 3,600 gallons of fuel. Ground refueling capabilities enables a mobile tactical aircraft pressure refueling capability at unimproved landing sites. The logistic mission enables the transport and delivery of equipment (i.e., light amphibious assault vehicles, Hummers, trucks, etc.), people (i.e., combat troops, parachute troops, Medevac, support troops, evacuees, etc.) and supplies (i.e., ammunition, food, medical, tents and housing, etc.). Cargo can be delivered by either air drop or to unimproved landing sites. The KC-130F and R can be configured to contain an Airborne Direct Air Support Center (DASC), but lack SINCGARS antennas. The KC130J has no DASC capability. There are different types of platforms that perform various aspects of deep battle management - the AN-UYQ-3A equipped KC-130 deep battle coordinator and the killbox manager or TAC(A) in an F/A-18D. The deep battle coordinator is a critical link between the Deep Battle Cell (DBC) that actively manages the execution of the deep battle and the killbox manager/TAC(A) aircraft for the execution of the deep battle. A deep battle coordinator in an AN-UYQ-3A equipped KC-130 (DASC(A) configuration) will have a more robust communications capability than an F/A-18D and can manage a much greater area. However, the deep battle coordinator mission is considerably different than the DASC(A) mission, which assists the DASC in the management of air support for the close fight as an airborne extension of the DASC. One aircraft probably cannot and should not do both roles due to the different missions as well as communications and personnel limitations of the AN UYQ-3A. Since there are limited numbers of KC-130 platforms and its primary mission is inflight refueling, relying on a KC-130 as a deep battle coordinator is problematic. References FY2003 Report for the Office of the Director, Operational Test & Evaluation [19 MB PDF] KC-130J NATOPS Flight Manual (NAVAIR 01-75GAJ-1) KC-130T NATOPS Flight Manual (NAVAIR 01-75GAL-1) The KC-130 and Expeditionary Operations USMC Command and Staff College USN/USMC AAR Operations ATP-56(B)

I don't think you will see any difference in the basic operation of VR in DCS with 16 or 32GB of ram when using a very basic mission. The real issue with the amount RAM in my opinion arises when you start adding lots of trackable objects into the missions. This, however, is not unique to just VR. Join a server with a good number of players and trackable objects and you will definitely see a benefit from having more RAM. I have a setup pretty close to yours imachen and it's my opinion that you could get away just fine with only having 16GB but, if you have the means to get 32GB I would go with 32GB. It might be overkill but that headroom can't hurt.

Salute, I'm fairly new to the DCS world so I'm not sure if this is a known issue or something I might have to compensate for but I'm finding that at night my performance is dropping quite a bit. This seems to happen whether I am in a rural or urban area, the NTTR, Persian Gulf or Caucasus map. The issue I am having is that in my Rift I am seeing the images in each eye going out of sync when I move my head left or right. It's a blurring effect that looks like the image is about 1/8 of an inch offset from the other. If I stop my head movement the images sync back up. I have a pretty good system 6700k (OC to 4.7Ghz), 32GB RAM, 1080Ti, a dedicated 1TB SSD for DCS and, a 500GB SSD for windows. From my reading on the forum, I'm not running what I would consider to be high settings, MSAA 2X, PD 1.2. The thing I don't understand is that if I run the same mission during the day I don't have this issue at all. The number of vehicles, map used or aircraft flown does not seem to make any difference as far as I can tell. It's strictly a day/night issue. I've tried turning off ASW both with a registry command and using the keyboard shortcuts but they do not seem to make any difference for me at all. I always seem to run a steady 45fps according to the DCS FPS counter no matter what. I'm really hoping some of you more knowledgeable and experience VR players can point me in the right direction to solve this issue. As a member of a virtual Marine squadron, we do a lot of work at night so I would like to find a solution to this if possible. Thanks

Salute Cubanace, I don't know you or your work but that does not stop me from realizing that the community is losing a valued asset. Lossing any member of this small community that has been willing to give their time free of charge is just a shame. I don't know why you feel like you failed or the reasons for your departure but I would like to say "Thank you". I hope that after some time you will come to miss the DCS community and reconsider your departure. Even if your involvement is not the same as it once was I'm sure our community would be better off with you being part of it then not. I wish you luck and hope we see you back in the DCS sky sometime soon.

I found that when I have a problem with NWS that if I cycle it off and on it seems to work well afterwards. It's just the initial implementation that seems to have an issue for me on occasions.