GRUNT -Shrek-

Die Probleme haben viele. Es gab ne IP-Umstellung, somit hilft vielleicht ein ipconfig /flushdns. Es ist ein Server-Problem. Bleibe aktiv im Forum oder frage im Teamspeak bei größeren Geschwadern, ob sich etwas getan hat.

Marry had roast beef, Marry burped. (MH + RB = MB) you are totally missing magnetic/true bearings, deviation and error. Basically you intersect two LOPs having best approximatly 90° offset, so the bearing will be most precise.

Positive: 4x Kh-25ML, 2x Fuel It's a Su-25 "T" (upgrade, not Su-25 as of FC3) you can tell by: - large rudder - missing gun in the hull portside - rear section does have the IR-jammer flat white circle instead of the long spike

Hi! This has been an issue, indeed. I am no pro in ME, but to my knowledge there was a similiar question about "guarding patrols" around an area. 1.) Quick and Dirty: never land really, but set lots of waypoints. 2.) If there should be a landing zone, maybe something like orbit/circle/racetrack? 3.) Or, more difficult, use groups, e.g. a chain of 10 support groups support 1 T/O -> land (deactivate) activate: support2 T/O -> land (deactivate) criss-crossing if they fly back and forth...

Solution near? Thank you! Yeah it could be that I am using wrong triggers. This is because I somehow got open beta in German and the translation is *unsatisfying*, while I am used to deal with English vocabulary in this context. I'll try, come back to you and maybe we can close it. I try to figure out the different triggers in German now. Thanks a lot!

ZSU-23-4 turns radar, shuts front hatch BMP-2 closes driver's hatch, opens two covers atop I can perfectly see the difference on those two.

Keyboard Layout For an overview of key commands: - Start singleplayer - go to "OPTIONS" - go to "CONTROLS" - select your desired A/C or Module on the top left layer selector - select "ALL" on the next layer selector - click "MAKE HTML" on the bottom right note: DCS will jump into explorer where several .html will be written down. as soon as you close the explorer, you will be brought to DCS back again. - take a look at keyboard.html (e.g. for printing)

1.) Did I not see any switch or is there non modelled, yet? 2.) WHEN will it be modelled (request! :) 3.) Does someone knowing the real plane knows where the switch is/how it is done? Better? :thumbup:

First of all thank you taking a look, but.. Well it is NOT about the "fire at point" (FaP) ... as stated that works for me with different units. (ZSU-23-4 also), I say again, that is fine! It opens fire as demanded and cease fire when flag 40 is set (0 or 1, cannot remember). Truly interesting, that it does not work for you. My problem is about not moving after state red.

Why not ask the program? I did some research. - flightplan distance 100km (so approx 240km in total including one go around). Anapa AB directed Krasnodar area, then return to Anapa AB, one go-around. - full spool up routine, taxi to 04 from N bunker, climb 4,000m en route, descend starts at 35km of initial landing point, one go around, full landing strip and taxi to opposite parking of airfield. - weather: nice/default, no wind - loadout: full internal fuel, no externals - timeframe: rougly 1hr = 60min. - fuel consumption: 56% = 1587kg seems legit. So I can spend another 1000kg on TOT/payload drag. :book: I did analysis yet, but my conclusions will follow later.:joystick: Stats listed here, comments appreciated: http://www.shreksquadron.org/documents/su25/fuel.html (most light, no gun, no externals) http://www.shreksquadron.org/documents/su25/fuel-most-heavy.html (KGMU, Smoke pods) HTH

*Russian accent* Comrade! What makes you think that? "In DCS" Soviet Russian befriends :thumbup: you and fight against the :smartass:*removed due to political correctness*:smartass: NATO troops. Grunt -=Shrek=- passionate Su-25 pilot. :pilotfly:

No OPFOR on map I have three different cycles active: a) move along route/hold b) alarm state red/alarm state green c) fire at point (stop condition flag)/flag set = CEASE FIRE Each cycle works perfectly on its own. Moving, stoping and again Alarm state red, green and again Open fire at point (auto alarm red), cease fire (after short time alarm green again) Whenever alarmstate red was engaged (either through b) or c)) no further movement took place, I tried also time zoom/acc. No enemy units were near. The attack was issued on a friendly airport building (blame me!). Further units: one friendly aircraft (as pilot steering) and one observing friendly ground unit. All to be seen in the .miz. I added a small briefing, the orders to verbose input on the screen if issued. I would appreciate if you take a look and tell me were I (or program) are (is) doing wrong.

Was that "weathertest.miz" by me? ^^ Nevertheless, due to openbeta 1.2.7. I somehow caught the German version again, still not fixed. The German translation is barely usable, if you are used to English terms. Also it's very difficult to orientate in the new ordered lists (German).

Dear community, I fly since some years and some questions/remarks/request have bothering me all the time. Now I want to put them online, to get a sense of the communities reception. In the Su-25 there are 3 stage switches for ext lights (navigation) and taxi/landing lights. But it seems they are not modelled, yet. It would be easy to check the status of ext lights if there was something like the Flaps switch, where you can check the position. However I understand the 3 stages are easy: Ext Nav Lights: stage 0 = off (switching on electrics) stage 1 = steady (at engine startup until leaving airport control zone) stage 2 = pulse (transit) stage 0 = off (fence in) stage 1 = approaching airport/landing Taxi light stage 0 = off (switching on electrics) stage 1 = near (at taxi to RWY) stage 2 = t/o and landing stage 0 = %? stage 1 = near (taxi to parking) Any help appreciated!

You are right, that automatic switching is not wanted at this point. I would prefer manual advance, too. But, your request is a bit odd. Usually a Su-25 pilot won't have programmed the attack site into his navigation system. You rather have an IP set up and do the rest per situation/reference. So my answer is a bit of all: - modelling the nav-system authentic (non-auto) - place the waypoint off to an IP (including attack heading/specs in the briefing) HTH, Grunt

[1.2.6][1.2.7 OB] [different units] Dear community, I am working myself a bit more into mission editing and I like to do some robust scripting. But I struggle alot. Today I started to control a unit in following its route and being in different alert states. I cross three swichted conditions that each perfom the desired action by applying the command, showing a test message and organizing the radio menu (remove given order, add alternating order). All three cycles (group stop/group hold and alarm state red/alarm state green and perform task fire at point/stop condition) seem to work properly and repeatedly. However the problem is, as soon as the alarm state red is applied once the motor is shut down resulting in a failing group resume (route). Applying the "perform order" results in auto set up alarm state red, with known flaws, although the alarm and fire cycle do still work. Question: Is it possible to apply alarm state red but let the goup resume the route again? Mission file for testing: http://www.shreksquadron.org/possible bug move and hold versus alarm state red INIT.miz Qualified comments appreciated.

You might check these datas for your planes: http://en.wikipedia.org/wiki/VNE# http://en.wikipedia.org/wiki/VNE#VNE http://en.wikipedia.org/wiki/VNE#VO http://en.wikipedia.org/wiki/VNE#VNO edit: I did some research, too. Most likely engines shut down occur a) under the influence of continious negative G-force (fuel does not reach chamber) b) stall conditions, if the stream of air intake into the jet engine is discontinuous or in any other way disturbed. HTH

Hi, I am working myself through procedures and learned that I cannot switch all lights, how do I turn on "Red light"? The two most left switches do not work yet, right? Lightspanel Overhead Copilot Right Side: [TABLE] [TR] [TD]Label[/TD] [TD]English[/TD] [TD]Remark[/TD] [/TR] [TR] [TD]ОСВЕЩЕНИЕ[/TD] [TD]Lights[/TD] [TD]Panel description[/TD] [/TR] [TR] [TD]ДЕЖУРН(ОЕ)[/TD] [TD]Dim/Saving/Low[/TD] [TD]Dim lights?[/TD] [/TR] [/TABLE]

Hi there, sounds like a mission to try in Multiplayer. Can you give more informations to the mission (filename, standard or 3rd party installed), so I can have a look at it? Basically you have to determine the type of thread, if you know what's down below, you can develop a strategy against it (in training missions) like 4,000m AGL against IR SAM Strela and Igla. Or diving weeds against a HAWK battery. Tim, I do fly 1.2.6 SU-25A and if needed maybe 1.2.4. Just check our homepage: www.shreksquadron.org come to our TS-Server and ask for GRUNT-

Wheels for Krauts There was I in my P-51D at 100ft, when I jumped... *hey, wait a second*

Hi there! It is quite sad that a bunch of people is able to capture high res videos, but has few knowledge of how to cut nice stories. A common mistake is to focus on your own experience, showing where you have been cool and put a stress on that in temporal context. Short: You create a 10min video for one excellent 30sec weapon run. Noone will take a look at that, well, and if... once. The next video will not be viewed in full extension but instantly fast forwarded. Here are some thoughts (well after graduating in arts, this might not be too selfish but should help the whole community on the long hand. And of course, I am looking forward to critical/controversial comments rather then praying the commandments. Defining the goal Spend some time to precisely define the outcome. Should your video achieve a tutorial, promotional function or is it just entertainment. Focus, focus, focus: What is the core message? Is it a procedural behaviour (e.g. setting up a weapon run)? Is it a single action (cluster bomb destroying whole group)? Is it weather, missile dodge, teamwork, or the great achievement of a mission? Helpful is also to write down the completed sentence (multiple facts possible): After watching my video the viewer [knows/feels/wants to/is inspired to do]... but remember the focus! Play with moods As old a theatre: developement, tension, surprise, ending. Or in terms of Hitchcock: tension and suspense. Develop a story that raises tension "what will happen?" and do surprise the audience "nice weather ... nothing bad... RWR tracking unit". Or milkrun on convoy... an Igla appears. landing run, bird strike one engine off. Generate: relaxed moods, happy, bright weather, procedural actions, all gauges in norm. tension: new thread, faults, missile incoming, weather change, audio request, an enemy grouping/setting up action action action: quick movements, explosions, fire fire, flares, shootings, near misses, canyons, high speed salvation: peace again, no thread, nice weather, situation stabil Make it viewable First of all: make short cutscenes, short short short. While older films (80ies) had longer timespans, it only takes up to 3 secs for a viewer to get most visual informations out of one picture. This means, if scenes are cut longer, you have a high chance to annoy the viewer. Make a story, make the story consistent. Well I know for tech geeks being proud it's difficult not to rest in front of your hardware. Give it a try. You do not need to draw a whole storyboard, but fixing on the storyline (words) adding some important visual aspects does the job. e.g. attackrun on AAA, approach into sunset overcast cloudcover, camera low rear (7 o'clock low) into the sun. Try sketching. If you like movies, you'll enjoy re-working your animation in game. Storyline is also important to avoid errors. (e.g. payload after attack run is different/not spend). Not to get me wrong: cutting together different captures is possible, but please do not cheat on that viewer, he'll quickliy find out. Be honest and cut it like its a collection and no single story. Keep in mind: short. Spend time on how to present and tell one situation. Well now, I think it is time for an example. Example: Attack run on AAA through the clouds. Bad example: cockpit view, 2min to target. You see the sun, you click around. RWR goes of, you dive. You show full weapons release in externals. Focus on destroyed unit for 1min. Bad. Very bad. WORSE. Good example: focus on exorbitant weather (see section moods), dive through the clouds, hit with one burst, maneuver after engagement. Playing on the axis of detail. (Camera distances to motive, different views of same situation/object, perspective). Playing with time (rhythm change: quick, slower). EXTERNAL Openning scene beautiful weather, flight into sunset 7 o'clock low. INTERNAL Cockpit view pan from HUD into sun/3 o'clock wing. INTERNAL close short: RWR on (only clicks), close shot Lights off) aka "fence in". EXTERNAL fly by view (not whole flyby max 5secs) ... "time passes" INTERNAL wide... another pan looking out of the canopy TENSION INTERNAL: close shot RWR [A] AAA indication tick tick tick. EXTERNAL "reaction": F2 bank 60° left (RWR!) away from sun. Crash dive through the clouds. INTERNAL: forward view. white out clouds... RWR active 3-4secs. EXTERNAL: AAA tracking turrent movement, elevation of barrels. INTERNAL: breaking through cloud cover, aligning target. EXTERNAL f2 front shot: small burst. EXTERNAL target, but camera as "journalist/observer" bit away. Only impacts -1sec wait for famous groahhh sound. (different view angle: explosion of unit if not happened, 2secs) INTERNAL: banking (only the first second) EXTERNAL F2 from rear: banking to 90° dropping flares. EXTERNAL F3 turn and flares (4 secs, longer if audio confimes the kill. e.g. "Mission complete, target destroyed, Whoo-hooo, ....") That's it. That's it, why there are cut programs. I know that's hello of a job but if you know the storyline and plot it WILL BE FUN to record these scenes focused on that message. Finishing Audio! See moods, choose different music/sounds for different moods. E.g. epic "nero - united we stand" beginning is not suitable for an relaxed opening scene. Feel the musics mood and speed! Use it accordingly to the scenes. (In our example with the RWR/AAA aligning, crashdive but not before that event). If you play one track for 3min filling visual material, you will end up with something else: a music video. Go back to "defining goals", start up again and seek to express the musics moods with the mean of DCS. But again, start over at defnining goals. Do not wait for radio to happen. Record it and mix it into the images... you do not want the audience wait for 10secs feedback after you requested takeoff. Seek music, radio coms (which is a good behaviour anyways). Having a storyline and a pre defined goal (remember that?), this one should be easy. If you spend time creating... do mention you, an appropriate title, the music used (copyrights? legal usage, try: jamendo and/or freemusic) programs and save the teamwork by mentioning helpers. And even contact (webpage), where to find more videos regarding one can download and do not see those videos in youtube. e.g. youtube channel. Looking forward to comments, discussions and - of course - stonishing videos. Have fun flying'n'recording! Words of the master: "Alfred Hitchcock On Mastering Cinematic Tension"

Hi there. I was browsing through the ground unit's list and discovered, that the mighty German Mercedes-Benz "Unimog" truck disappeared since FC2. It's a pitty and a request. How can one create new units? - .ac Modell (blender)? - .lua Script (behaviour/weapons/actions/tasks/options)? Looking forward to replies!

New Map What about Germany? Well the idea bombing Germany isn't too nice, well. But, Germany is/has been a possible scenario for the A-10 vs Warsaw Pact Forces. Germany is/has been/was a scenario in WWII P-51s/Spitfires/Bf109s and what to come. To me it would be rather weird having a T-34 and a Mi-24 fighting against a P-51 and A-10 and M1A1. So it's less the geographical issue, rather the time factor.

Please leave a comment! QFE: altimeter zeroes on specified airfield (currently published by ATCs) QNE: default setting in A-10C 29.92inHG (1013hPa,759.6torr) QNH: current MSL pressure (altimeter shows field elevation) Since ppl dial in QFE or leave QNE their altitude readings differ: from aircrafts takeing of from other airfields reading a different elevation from all AI aircrafts either set to MSL or AGL If QNE is left dialed in (no manipulation on altimeter) furthermore: altitude is neither field elevation nor zeroizing on that runway My question is: What would be a propper setting. Idea (to keep it simple): Use QFE in pattern/procedural context (as already published via ATC) As soon as A/C leaving traffic pattern of airfield: QNH (needs to be published in Briefing in torr/mmHg/inHg), to match up: AI altitudes, common altitude settings, altitude over MSL readout. Comments welcome!

http://en.wiki.eagle.ru/wiki/Mission_Editor:_Weather_Modelling I started some studies on weather in that region and realized, that usually there are up to 2 cloud levels. I am not sure how complicated that is (esp. in overlapping) but I think having two distinct cloud layers would improve the realism for high altitude flyers and optical reception, since wind layers are modelled already. Also the weather settings in general are demanding a lot of re-calculation (wind from/to m/s kts) and seem not to be affected by [x] imperial units settings. Also setting fog to maximum thickness, it won't reach Beslan AF, since its attached to MSL and not AGL. Is this a true weather behaviour? Is there never fog at Beslan because of it's height?