blueskunk

so there is a 1.5.3 open beta, a 1.5.2 and a 2.0.0 version? cheers

+1 for carrier ops! :-)

massive respect! big thx :-)

been through a couple of your vids now, great camera work and excellent choice of soundtracks! awesome :-)

that did it. cheers :-)

there are 6 paints in the liveries folder but nothing shows in editor. i fly on dcs 1.5 (2.0 stutters badly). ideas anyone? cheers

took me a while to figure jsgme out but i got it working :-) thx a lot for all the help! :-) ... still trying to find out how to release weapons (i did map all su33 controls...)

pardon my ignorance, but can anyone refer me to the respective lua file? the one i found in mods/aircraft/fa-18/input/fa-18c/joystick folder doesn't show // or --. just a ton of text... also, anything i need to consider before making any changes? default planes won't be affected, right? i never did that before... cheers :-)

thanks all for the help :-) also: how do you "un-comment" the weapon release in a lua file? thx

after some more experimentation: controller settings and weapons aren't working (none of the weapons apart from the gun can be employed...). the f15c controller settings dont affect the f18 at all (with the cockpit being that of the f15 i assumed the controls etc would be coming from the f15c). the f18c controller settings don't seem to work with the f18. there's no effect. what does work somehow are su33 controller settings. but without a su33 cockpit its also confusing... not sure where the problem is. with the f18 being so refined and detailed i do assume there's something wrong on my end... not sure what it is, though. i dumped all the unzipped folders into the respective folders of the main dcs directory. same what i did with the a7 mod, for example, and that one is working fine in all respects. any help is appreciated, i'd really love to get this bird to work properly :-) cheers

hi, I downloaded the F18C and love it! thx a lot! One problem, though: When i select the F18C it comes with the standard F15C cockpit and HUD, but the controller settings are those for the SU33. Now how can i get the functions of the F15C working that don't exist in the SU33? Secondly, when i select the F18A it comes with a F15C cockpit which is all powered down though, i.e. black MFD's. Also it comes with a SU33 HUD. I think i installed it all correctly but I'm not sure, tbh. Any advice?

works perfectly in dcs 1.5. many thanks :-) Install: Create a folder named "SU-27S-CPT-TEXTURES", put all unzipped files into it. copy that folder to: /DCS World OpenBeta/Mods/aircraft/Flaming Cliffs/Cockpit/Textures

REDFOR Callsign: Skunk Lone Wolf Preferred Aircraft: Su-27 thanks :)

indeed! very impressive :-) how did you do that?

hi are there any mods that use the su27 as a base? as in flight model and cockpit? many thanks

- split fighters, sead, cas, helos into separate channels. keep numbers low (2-4) - assign a mission commander in an awacs slot, i.e. east front cdr, or west front cdr, or whatever with whispers to all squadrons he is responsible for - mission commander assigns tasks to squadrons, cap, sead, cas, trsp, whatever depending on situation - manage airspace, update squadrons with relevant info - monitor developments a second commander might be neat to back the main one up and share the workload, like managing late-joiners/lone-wolfs, etc. brevity or full on voice procedures won't be much of an issue then, as any discussion, banter or just different style of communication and tactics will not negatively affect the other squadrons. established squadrons can still stick to their procedures, randomly created squadrons just wing it (what they are doing now already). you still get everyone who's motivated on board no matter what their experience level. seems very little effort to me for a whole lot of benefits. again, i'm not telling anyone what to do. but i do ask for some understanding for those squadrons that prefer to have a closed channel. :-) skunk edit: +1 on channel structure overhaul

take this video for example and just play it off twice at the same time, simulating 2 elements in an engagement. (please, don't think i'm exaggerating here. some squadrons fly like that) so, how does that enhance anyone elses situational awareness? and how much space is left for cas, helos, awacs, to get a message in? how would that benefit the fighters in their engagement? if you want to simulate air combat and want to fly like that you want separate channels. that will prevent anyone interfering with non essential info. a chain of command is there to coordinate all actions but also relay important info. the mission commander will tell the helos where to go or where to hold without anyone else being disturbed by that. awacs intel to the mission commander will be used to task the fighter patrol to barcap at a certain grid or give a heads up of threats to inbound cas. etc. whenever any element engages their battle coms won't disturb anyone else while they coordinate their actions. the one main drawback of it all is really only a matter of organisational effort. that's why so much time and effort goes into training and practise. jacks, i do respect your opinion and i'm not telling anyone what to do. i do encourage you, though, to maybe just give this concept a fair shake. just for the experience. onwards. skunk

anyone who thinks 20 dudes in one channel can work efficiently has never experienced a working chain of command and proper voice procedures. it may seem to work all right because it's better than any random chaos, yet still far away from what's actually possible. i don't understand why established, competitive units shall drop their standards to cater for the more uncoordinated rest. if anything it should be the other way round. support your strongest assets. and noone is surely denying the fact that those squadrons that lock their channels fail to support the overal goal. unless there is one established overall commander i wouldn't go out and blame anyone for not supporting their team. either way, no offence, just my 2c :-)

an awacs isnt really a commander. but either way... my experience: noones reading stuff kick dudes that dont teamplay be persistent, people will adapt commanders are needed who push everyone things don't work like a charm from the start. not if you incorporate concepts that are new to most. commanding a whole campaign is something different than commanding a squadron. but i'm sure some guys would be up for that. here's where some staff work and a coc would work wonders. but most importantly: bluflag is the closest i've seen to a proper combined arms campaign in dcs. i think it's way cool and definitely a huge improvement over regular online pvp. i like it a lot :-) and despite all teething problems it's surely worth sticking with it. cheers

no ideas about player balancing, but: 1. how about adding a commander channel on ts? 2 dudes who will be overall campaign commanders? squadrons follow orders. these 2 dudes are in the tactical commander slot watching over the f10 map and its developments with whispers to all squadrons? i never know whats the big picture and to find out is a hassle. certainly not effective. 2. how about making being in ts mandatory? those with their wife and kids sleeping in the same room can still be on ts but just listen and not talk. worked well with other games.

sitting in nalchik about to take off. i never made it... ${1} edit: why does embedding a video not work? click youtube icon, insert link... fail... ?

Hi Registering for Blue Flag 2: Please add TAW 1st Aggressors Squadron to redfor: TAW_Skunk_1AGG TAW_PastorJoe_1AGG TAW_DutchBaron_1AGG TAW_tkiD_1AGG TAW_WesLoeffler_1AGG TAW_Garud_1AGG TAW_redacuragsr_1AGG Thank you very much, Skunk

i have a question: would it be possible to add more waypoints to the flight plan? the kneeboard map isn't useful much without getting full coverage of the operational theatre. we fly flankers, not sure if that would be an issue for other jets. cheers

hi, we would like to register on red side: TAW_Skunk TAW_PastorJoe TAW_DutchBaron TAW_Garud TAW_WesLoeffler TAW_tkiD TAW_redacuragsr Su27, please cheers :-)