Firehead

Go to your export.lua in SavedGames/DCS/Scripts. Open the Export.lua, adjust the following intervals, I use: gExportInterval = 0.0067 gExportLowTickInterval = .0067 Works flawlessly for me.

Got everything working. Sort of. Same problem others have described, a completely washed out LCD screen for the various displays, virtually unreadable. MFCDs are A-okay, but CSMC and RWR, etc are shat. Anyone make it past that point?

After fiddle-farting with it last night, I got the MFCDs working as intended. However none of my other exports are working (clock, RWR, UHF Freq, counter measures, etc). I figured out that 1.5 wasn't taking the old name of the MFCD (ED_A10C_LEFT/RIGHT_ MFCD) so I'm wondering if this is coming down to a naming issue. I'm going to play around with it now that I'm fresh and not tired to see what I can come up with.

I am still unable to get any of my exports working. I did essentially the same thing, and copied over my valid config that works for DCS. I even tried copy and pasting the contents into a new config. 1.5 refuses to use my exports. Anyone have any ideas?

To reiterate what others have said, use your commo/F10 menu to call in SEAD flights. I've never had an issue with them getting stuff done to reduce threats near my target area. Just orbit around the IP, locate and mark threats to you. You'll hear SEAD over the net killing targets, it just takes a minute. You should, by then, have identified any remaining threats and be able to engage them, or avoid them all together. Happy flying.

I used a program called Easy Monitor Configurator. Some people dislike it, I'm not one of those. Helped me ensure that I have the correct settings and files in place to use Helios properly, as well as my exports.

The "mark" setting will allow you to use Z-mark as a steer point, in addition to any other points that you set using TMS Right (short).

I was sitting here watching a movie, and NVidia Experience came up and notified me to install a new driver. Don't know why I didn't think of that first. I ran DCS again, same process as before and it came up just fine. So I guess we're back up and running. Mods feel free to close. Thanks.

I only have a single GPU, GTX760.

Okay, I'll describe in best detail what is going on, as well as fixes I have already tried. What I'm doing Open the launcher from the desktop. Select "Quick Missions", selected the very top missino for the A-10C Game pretends to launch, goes to desktop. Nothing happens after that. What I've tried I tried a fresh install. I tried the repair. I deleted the saved games folder. I deleted the temp folder in appData. Nothing works. Here is the log: Any insight here? I have already looked around at some of the other crash threads, and none have really been of help. Thanks for the assistance.

IIRC, when you get a final attack heading from the JTAC, you cut that azimuth in half. So 130 would have been the preferred attack angle from the JTAC. The reason why you get that 000 - 260, is because any other angle could potentially result in friendly fire, whether by accidental misidentification, or ricochet/outright miss. He is basically telling you your alley of attack. This gives you a large alley to allow for pilot discretion based on terrain or additional threats that the JTAC may not be aware of. Just FYI.

Yep, that is exactly what would happen :glare: The person who released it and is Discovered, who also happens to be a US citizen can get in trouble. Chances are, if they have the knowledge and the documentation, they have signed a non-disclosure agreement or something along those lines. We all know who Edward Snowden is. Granted, it isn't on such a scale, but the concept is the same.

If someone happened to have information like that and then release it, they would probably go to federal prison for releasing top secret information. You guys may not like hearing this "its top secret" stuff, but there is a reason. A lot of the current technologies on the market that protect both pilots and troops have a lot in common. If the information were to become available, the enemy will figure out how to work around it. They already have ways of working around it in some cases, but it is a primitive work around usually. Your hunger for information that doesn't need to be known can get people killed. Ever heard loose lips sink ships? It is true. There is a reason why they don't tell you that stuff. Why do you need super realistic modelling of such a system. The "arcade" implementation will suffice in 99.9% of the cases that you will need this kind of stuff. Would you put up your address on the internet for everyone to find? I'm talking you specifically, not "but you can google map it". I'm talking they know who YOU are. Where YOU live. Where You work. Specifics about YOU, nobody else. How about you tell me what time you're at work so I know when and where to rob YOUR house? Would you? Didn't think so.

I want the Mig.

I think this is very fair, and is exactly what I was talking about from my posts above. I personally have no problem interfacing it myself, when the price is right to have a nearly completed panel.

Ian who I also share a name with: His prohibitive upfront tooling costs are a risk that must be taken if he wishes to have a business based on using it. I'm not saying he needs to go out and buy a $20K CNC unit, but a home unit for personal projects with a small cutting space isn't ultra expensive. It isn't something I want to spend my money on, as I don't intend to make a business out of creating this product. Small market, I know, but its a risk that must be taken if he wishes to sell panels to other people. Wanna start a delivery service? You need a truck right? I am referring more to the simplistic switches and panels, however. Can you give me a valid excuse why a fairly simple panel that provides 3 switches, a push button, and a single gauge(with motor) is $860USD? Go ahead, I'll wait. At this point you've paid more for interfacing than anything else, since the panel I refer to was CAN-BUS. He needs to figure out what market he wants to sell to, and that is up for him to decide. If he wants to sell to guys who know absolutely nothing about the stuff, DCS certainly isn't the game for them in the first place. The people that make these panels for this outrageous price better have Honeywell switches in them. Oh wait, I don't need Honeywell switches because my cockpit doesn't actually fly. I completely expect to pay more for a CDU, just not $1000+. The numbers I have thrown in are purely for example and argument sake. Some parts of the cockpit will be more expensive than others, I have admitted that. There are many things in the cockpit that should not be expensive either. The pricing is ridiculous in a lot of cases. Here is an example of several panels in the cockpit that should cost less than 120 bucks complete, just requiring a bit of work on the user end to install: - Breaker panel - Lighting panel - SAS panel - Electrical panel - Armament panel I have Electric Power Panel that cost me around total of $70 bucks, and it is fully capable of being back lit(I have chosen not to at the moment). I have not counted the board used to interface, only because it runs several panels simultaneously. I also have another switch panel(I can't remember the name right now) that turns on the CDU, and changes waypoint related info, cost me around $70 bucks as well. Also great quality and extremely reasonable cost, as I was given a slight discount purchasing from a friend. Now, I received the painted acrylic panels and installed the switches, performed interface myself. He does the panels in batches, several at a time, so this made for short work on that portion. It didn't take that much time, and while I have no direct experience with a CNC, a simple project would only require you to start the machine and walk away(in some cases, not all), presumably to work on other panels and fill other orders. Another option for him would be to have different levels of product? One being plug and play, another being self install, or just the panel. Give the person making the purchase a little bit of say in how much they want to spend and why. Something like that might entice users who have a lot of money to blow, or users who don't mind doing a bit of leg work. He has to make the business/economic choice for himself. I'm just saying, as a slightly above average user, that he will need to make them reasonably priced if he intends to sell any at all. edit: Refined some wording.

The problem I've noticed with any pre-built pit parts is price. An example is a landing gear panel that costs over 800 dollars. Eight. Hundred. Dollars. That is retarded. I'd pay 70 or 80 bucks, depending on how it interfaced, but no more than 100. Hell, I just want the prebuilt panel, I'll wire and connect it to DCS myself. CDUs? I saw one for 1100 bucks. F*** off with that crap, it cost them maybe 120 bucks of material plus time spent making it. I would expect to pay maybe 3 to 400 hundred for it, at most. I also understand that it took you a while to create and design the part, but that should be factored into how many units you can sell. Math example: Joseph took 15 hours to design the part, and 3 to build it. It also cost him 120 USD to get the required parts. 1100 - 120 = 980. 980 divided into the 15 hours is 54.4. Joseph has valued his time spent to be $54/HR. Joseph also sold no units, thus all the effort was in vain. Clearly I'm just throwing numbers out, but I did it to prove a point. Once you've made enough parts and know what you're doing, cost and time spent will go down and in the end you'll make more money because more people can afford it. Seems like I'm being a cheap ass, but I don't think that most parts warrant any serious expense. Obviously the higher the complexity the cost should go up, I understand that. Also a factor would be quality and realism. Personally I'd settle for decent realism and quality of the parts, average person will NOT want professional grade simulator hardware. You'd sell a lot of pit parts if your average adult can afford to buy 2 or 3 at a time. A semi-realistic cockpit for a game shouldn't cost more than my car that has 500HP and can go 174 without a problem. Want to try and make a little cash or a side business out of it, fine. That is your perogative, but don't be greedy or you'll fail.

I've been keeping up with this for a little while, though never bothered to install it. Until now. This is super cool, and with the lights working adds a little bit of flare to the game. Keyboards will be a thing of the past when I fly. Thanks for the hard work, it is appreciated.

There is a setting, something along the lines of "Cockpit Resolution" or something in your graphics settings menu.

I believe you have to set the area where the TGP is pointing to the SPI as well, in order for the aircraft to be able to calculate proper release points/angles. Always put them on target for me. Try setting the laser to "latch" as well, I prefer to fire the laser for the entire duration until impact, provided that I can do so.

Well, there are quite a number of things that can wrong in the aircraft obviously. Some of the things I would learn how to deal with would be: Loss of a single engine: Loss of the right engine specifically is the worse of the two. You need to know how to milk her home without a lot of normal assets. I lost my right engine and IIRC the right engine is associated with a lot of systems because it runs the power for them. I believe I had lost EAC, CADC, and Autopilot as a result of some 23mm punching my engine. Very difficult flight home, for about 50 miles. Fuel leaks: What do you do when you're leaking fuel? Turn on cross feed and disable the fill to whatever tank is leaking. Fire: Look at the fire pull handles, which ever one are blinking pull them out. Then hit the "discharge" switch to the right, that will put your fires out. The engine will probably be gone, so you'll want to turn off fuel flow to that engine, set it to idle, and just run the motor. Another fire can spark up pretty easy if you take additional hits. In flight start procedures for an engine: Rarely works, as most cases engine loss is a result of explosion or ground fire, but it won't hurt you to try. Set the engine to idle(0% throttle but not past the detent), Fuel flow to "override" for that engine, and then "ENG OPER" press it up to "IGN", which it will try to start the engine. If that fails, ensure to flip ENG OPER to "Motor" so that it isn't trying to produce thrust(in case of a fire), and just runs the motor to power systems. Those are the major things I can think of off the top of my head. Everything else you might encounter will be easy for you to deal with as they come with experience and basic ability to fly the aircraft. If I'm missing anything on my procedures, feel free to chime in and tell me I'm wrong.

I want a Hawk

I have the R3volution. My room mate has the Ozone.

Did you do it my way? or did you have another solution?

The method for fixing that will be similar to that of making home built panels work. You should be able to set it as a momentary button, that way when you release the switch from the "on" position, it knows to simulate another key press. It has been quite sometime since I've played around with it, but I know it is possible, since some switches aren't an On/On, some are "On/Off" like you describe We'll use the APU as an example: 1.) First off, set the switch to do what you want in game, through your options. Then go to the user/savedgames/DCS/Config/input/Whateverthedevice is called 2.) Find whatever command you modified, it should look like this: {down = iCommandPlane_APU_Start, name = "APU Start", category = "Engine Control Panel"} 3.) we need to tell it that releasing that button aka "up" to do a different activity. In this case we want it to go off. We need to add to that line: {down = iCommandPlane_APU_Start, up = iCommandPlane_APU_Off name = "APU Start", category = "Engine Control Panel"} Now when we release, "up", the APU will shut off. There might be more info in the line but the principle remains the same. Maybe some stuff has changed, but that is how I remember doing it. Let me know if it works.