Wesjet

I have completed this but my server as well will not autostart a mission. I have to open the WebGUI and click the start button. Missions were added to the list and for good measure I saved the list file too.

Delevero, you need to convert coordinates from decimal to arc second. See my guide here: https://forums.mudspike.com/t/f-a-18c-jdam-paveway-targeting/8325

I just wanted to add, that in the case of a warm start - there is NO volume for the AIM-9 or Sidearms, even though the AUX volume knob is all the way on. Clicking the volume control will turn the sound on.

Can't run DCS repair as I am installed via Steam - however steam has a file integrity check. Ran that, it fixed a couple files. Issue persisted. I thought to check graphics options - the VISIB RANGE field was blank. Reselected HIGH and problem resolved. Thanks!

Typically you cannot see "inside" an aircraft however, something has gone wrong with my DCSW and now I always see inside them..... I am lost. :helpsmilie: It was fine, I exited to change a couple buttons on my HOTAS for the F-15 and now it does this: "][/url]

At the time of the Fly-In I recorded many hours of video. Since then, when I have had time to sit down and do some editing undisturbed - I would do as much as I could. However, I has HOURS of video to look through! Here is a link to my youtube playlist with the 5 videos I created from the footage: Going forward I will do more spectating in larger events so I don't have to worry about my own aircraft while recording, and keep more notes to simplify the editing process!

Serial: 22522 Location: Brampton, Ontario, Canada

If the cost is reasonable, definitely. The less buttons I have to click on screen the better!

When I was playing A-10C standalone, selecting JTACs was easy..... But now in DCSW it's not.... Anyone got a way to go back to the old style of listing callsign/freq?

Indeed! And price compared to the Saitek ones? My Saitek left pedal just broke - so if I can't fix it, it will be time for new ones and the Slaw ones look GREAT.

Wit the latest patch, CTTS has stopped working for me. On mission start I get the error: DCS: Mission script error: : [string "C:\Users\Wesley\AppData\Local\Temp\DCS\/~mis000039B1"]:1: unexpected symbol near 'ï' Loading the file shown in the error, it is CTTS as configured for my mission (worked perfectly before patch). The given character as stated in: "symbol near 'ï'" - is not even in the file. Anyone else got this bug, or a solution?

Some movie and games have touched on an invasion onto American soil, but I am Canadian. How about Toronto & the Greater Toronto/Hamilton area? That would really be "bringing it home" for me. :thumbup: I could make a mission to save the CN Tower! :joystick:

Hey guys, I'm diving into the mission editor and going to work out a CAS oriented, primarily co-op with some H2H - mission. I'll outline it here, hoping to gain some input and with good luck and enough spare time to finish it - create a well polished MP mission that we can all enjoy! Mission Title: TBA Primary Mission: CAS, ground assault by BLUE. Objective: City of POTI and Sukhumi Airfield (Secondary). Season: Summer Weather: Partly cloudy, light winds, 22 degrees C. Mission Start Time: 6:00AM Local. BLUE Start: Batumi (Fixed Wing), Grigoleti (Ground), FARP 'Dallas' near Grigoleti (Helo). RED Start: Sukhumi (Fixed Wing), Poti (Ground), FARP north of POTI (Helo). BLUE Force: 6x A10-C 2x A10-A (for those that like things 'old fashioned') 1x Tanker 2x Ground Command 2x Su-25T (SEAD) 4x Helo (KA-50, UH-1H - 2/2 or 4/0...not sure yet) 4x F/A-18C (AI Controlled SEAD flights) 2x2 RED Force: 4x SU-25T 2x SU-25 3x Ground Command 4x Helo (Mi-8/Ka-50, 2/2 or 4/0) Description: The mission will open up with RED force occupying the city of POTI, with enough ground units to defend it from attack, and enough SAM/AAA to keep CAS away. AI Controlled F-18s will take off from a carrier off the coast to fly SEAD, there will be 4 aircraft in flights of two - I hope to work in a lot of partner work, this is a hint. The F-18s will be tasked to remove the big threats, and shouldn't delay the mission for players but much if anything as I plan to use all cold-starts for player slots. After these flights, there will be some remaining SAM and AAA threats (nearly all AAA). BLUE force players will have access to Su-25Ts and Ka-50s to work on the remaining air defences. KA-50s will also be useful for recon I hope. However, I do plan to give RED helicopters aswell. I am leaning away from KA-50s to avoid accidental fratricide, but the element of identifying friend or foe intrigues me. Ground command on BLUE will have access to a large supply of units to assault the city - however, minimal collateral damage is key aswell as keeping casualties as low as possible. Re-supply would be limited, and should BLUE take Poti, they can roll out to Sukhumi - where the additional units are a benefit. RED forces will have ground command to break the predictable tactics of AI, SU-25Ts to run their own CAS and either Mi-8s or Ka-50s. BLUE would be required to capture a RED FARP on the way to Sukhumi. RED will start out with superior number in ground units - however between BLUE CAS and reinforcement, the tide will be in BLUEs favor the entire time. Essentially, RED won't win unless BLUE players get extremely frustrated or have to leave for other obligations. RED force's primary objective will be to hold POTI and use aircraft and ground command to interrupt BLUE's work and make an otherwise easy day hard. So if you like ruining somebody's day - play RED. If you like coordinated teamwork, pick BLUE. I am considering AWACS, and Fighters (both sides, very limited) but am unsure how to implement this with it creating a small impact on the CAS. I would like the mission to run smoothly even without a lot of players - and in this case even 1 fighter could be too many. So fighters are likely no-go. The battle for POTI will be a coordinated effort, I hope to see A-10s in pairs, sharing SPIs, buddy-lasing, and generally using PGMs. Ground units will be moving into the area to assault - so watch danger close! Once POTI is secured, the run to Sukhumi will be rather long but feature sporadic, uncoordinated RED attacks. This is the open killing field, A-10s would be free to attack at their own discretion - with safety of only friendly force movement and aircraft to keep in mind. At this point, there would only be the odd AAA unit. BLUE helicopters can fly close to ground troops and provide talk-on to A-10s or mark targets. Throughout the whole mission there is chance for A2A engagements. Be prepared to cancel that gun run and dogfight! Blue force would be making use of the following routes: E70, E60 & E97 Link to mission planning photos: http://s277.photobucket.com/user/ApacheC424/library/DCS%20World/ME%20Project Anyhow, that is all I have got for now! Going to do my best to take my time at this and make sure it turns out good. Which also means there will be lots of testing! :joystick:

I'll just ruin that point by saying that I am 19 and CoD to me is childish and boring to play online. I used to fly FSX a lot starting in about 2009, the guys I stuck with to fly though were all over 40. It was the only way I could enjoy the game. I did screw around with the F-18 though, like the "kids" - but I kept distance and flew formation with the guys in the airliners, landing with ILS with the group and such. When I tell my friends I like sims, they call me boring. :joystick: I tell them their attention spans are too short to understand what I find enjoyable. :music_whistling:

Great stuff. Does anyone have information on preload radius settings? Is having it maxed really advantageous? Max setting being 150,000m (80.99352 nautical miles) - seems pointlessly large.

I have gotten some similar ACCESS_VIOLATION crashes with the A-10C from varying DLLs. Noted so far: A10Cgui.dll and A10Cprotect.dll (not exact file names). However, those came during multiplayer.

Odd thing was that the gun fired fine, it was just the visual of the barrels spinning that was slow. Only noticed it this week, but after reboot it seems to have stopped.

After flying in DCS: A10 for a while I looked around to see what else was available and long story short moved to DCS: World. Both have been installed via steam. However, when I use an external view I have noticed that the cannon's rotation in DCS world is so slow it's barely moving. If needed I can make a video for reference - but DCS World I only see it spinning a couple RPM. This isn't a illusion due to speed either, and I see it decelerate - it just never goes over about 4-5rpm spin speed. The animation seemed fine in DCS: A10C however.