Leaderboard

Description Currently with DCS-A10C (1.1.0.6) the Master Server connection is necessary for playing the game in all multiplayer mode (also LAN). This issue has already been mentioned in the TechSupport thread but was closed by a moderator. Requirement Master Server connection is not necessary for LAN mode. Possible solutions Remove this connection completely for LAN mode If you connect to Master Server you can play the game the next 10 days in LAN mode without connection to Master Server. ! Note for all the other users (non-ED members) ! Please do not use this thread to tell ED how angry you are because A-10C has this feature or your general concerns with copy protections. This issue has already been mentioned in the TechSupport thread but was closed by a moderator. Use this thread to tell ED that you also want this change (a simple "+1" post should be enough). Let's tell ED this way how much people wants this feature. If you have friends who want to buy this game but don't buy it because this master server issue add a +1 in your post for every friend. UPDATE I've made some calculations from Post #1 to #240... We got currently a +339

Here the main improvements in this release: DCS: A-10C Warthog is now supported New HUD (F/A-18 like) Mach Number, Indicated G and AoA telemetry Charts tools (Professionnal Edition) GPX file support (Home Edition) ETOPO2 worldwide basemap (Home Edition) Optimized DCS and Lock-On LUA exporter to be faster on low-end computers Numerous improvements and fixes Enjoy! http://tacview.strasoftware.com follow the dev blog on Facebook

Alternate future number 862,586: Ring Ring ED: 'привет' TFC: 'ello chap, been flying that military A-10 sim much?' ED: 'Da, I can't sleep. We should give this to the people, much fun.' TFC: 'Sorry chap, we just don't have the staff to do something like that. Besides, the military contracts are too lucrative. If we made it available to civilians we'd barely break even against the cost of development. Let's just sell the declassified sections of the source code to EA Games.' *Meanwhile at the EA Games cave!* EA Games Producer: 'Sure we'll give you millions for that. No, thank you. Goodbye.' /hangs up and redials Ring Ring EA Games Developer: 'Yo, what up?' EA Games Producer: 'Yo, DookieJ, we have a new project for you and your staff of thousands. The source code is in your email. Can you put this together to ship in say... two months.' *pause to read* EA Games Developer: 'This the shiz nizzle shizidy pop. We would have to scrap about half the code, and bring the key commands down to about 15. That's the latest projections from marketing on the average attention span. Yeah we could do it. This will be complex, we could charge for phone support and just have them reinstall windows.. or blame it on nVidia if there are problems mwa ha ha!' *Two months later on Zomba's PC* M for autofire maverick E for autoevade missile !!Bloop bloop bloooooooooo!!

Did i hear the word just? Does anybody else feel the need to tatoo the word 'just' on one of his limbs, saw it off and utlize the so created blunt weapon to beat the lavish use of that word out of people? Ah, that is just me, you say? Fair enough. :D

I have found a way to create all indicators of DCS viewports like MFCD. As you can see in the screen shot it's possible to create viewports for all the DCSW Indicators. Here is the way to do that : - First go to S:\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit - Then go to the indicator folder you want to use (Eg : AN_ALR69V\indicator - then open the init.lua file of your indicator (Eg : AN_ALR69V_init.lua here) - find this line : indicator_type = indicator_types.COMMON-And just paste below this code : [color=Red]-- Code below is used for the rendering when no viewport has been created[/color] purposes = {render_purpose.GENERAL, [color=DeepSkyBlue]-- Rendering in 3D View[/color] render_purpose.HUD_ONLY_VIEW,[color=DeepSkyBlue] -- Rendering In HUD only View[/color] render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, [color=DeepSkyBlue]-- Rendering in External View[/color] render_purpose.SCREENSPACE_INSIDE_COCKPIT} [color=DeepSkyBlue]-- Rendering in In cockpit view but NOT in 3D cockpit [/color] [color=Red]-- End of rendering configuration[/color] screenspace_scale_initial = 3; screenspace_diplacement = {0,0} local x_size = 1 local y_size = 1 function update_screenspace_diplacement(zoom_value) screenspace_scale = screenspace_scale_initial + zoom_value; if screenspace_scale < 1 then screenspace_scale = 1 end local screen_height = 2.0; local screen_width = screen_height * LockOn_Options.screen.aspect; local scaled_width = SelfWidth * screenspace_scale local scaled_height = y_size * scaled_width -- for indicator all sizes is function of width scaled_width = x_size * scaled_width screenspace_diplacement = { 0.5 * screen_width - 0.5 * scaled_width, -0.5 * screen_height + 0.5 * scaled_height} screenspace_diplacement_arcade = {screenspace_diplacement[1], 0.5 * screen_height - 0.5 * scaled_height} end update_screenspace_diplacement(0) function set_full_viewport_coverage(viewport) local w = LockOn_Options.screen.width local h = LockOn_Options.screen.height local a = LockOn_Options.screen.aspect local x = (-1.0 + 2.0 * (viewport.x / w)) * a local y = 1.0 - 2.0 * (viewport.y / h) local width = (viewport.width / w) * a local height = viewport.height / h local scl_hgt_K = y_size * SelfWidth -- size always function of SelfWidth local scl_wdt_K = x_size * SelfWidth -- size always function of SelfWidth screenspace_scale_x = 2.0 * width / scl_wdt_K screenspace_scale_y = 2.0 * height / scl_hgt_K screenspace_diplacement = {x + width, y - height} screenspace_diplacement_arcade = screenspace_diplacement[color=Red] -- The code below is used for rendering When you use viewports comments are same as above for rendering[/color] purposes = {render_purpose.HUD_ONLY_VIEW, --render_purpose.GENERAL,[color=DeepSkyBlue] --Uncoment this line by removing the "--" to render in 3D cockpit.[/color] render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always [color=Red]-- End of rendering configuration[/color] render_target_always = true end -- try to find assigned viewport local multimonitor_setup_name = "Config/MonitorSetup/"..get_multimonitor_preset_name()..".lua" local env = {} env.screen = LockOn_Options.screen local f = loadfile(multimonitor_setup_name) if f then setfenv(f,env) pcall(f) local vp = nil vp = env.[color=Red]RWR_SCREEN[/color] if vp ~= nil then dbg_print("ok we have directly assigned viewport to CDU\n") set_full_viewport_coverage(vp) end end -Change the red value name to set your viewport Name -Go to \Config\MonitorSetup\YourMonitorFile.lua - And add Viewport like this : RWR_SCREEN = { x = 1000; y = 1245; width = 170; height = 170; }Enjoy!!! No cockpit avionics display render and ready for export in DCS-A10 1.1.1.1 and a Example LUA.zip

New upload with improved README file, 4/20/11: README for Speed’s chatIOlibv1 NOTE: THIS SCRIPT ONLY WORKS IN MULTIPLAYER!!! NOTE #2: notepad++ is highly recommended for reading lua files. It is available for free download on the internet, and has no evaluation bull!@#$ to deal with. It’s high quality, 100% pure freeware. It is available for download at: http://notepad-plus-plus.org/ Speed’s chatIOlibv1 is a script inserted into a mission in the A-10C mission editor that allows clients and hosts in multiplayer missions to receive data from a mission in the form of multiplayer chat messages, and also allows them to send commands to a mission through chat messages. For example, with the right function calls in the mission editor, the current position of a moving group of enemy units could be displayed at the top of the screen, or a client could type in “helpme” and a group of F-15s could spawn and come to the rescue. This script sets up a number of global lua functions that can do things like this and are called through mission editor triggers. Furthermore, this is obviously open source, so anyone can make their own functions if they want. I can also take requests for new functions if they are needed. The very first time that the init_IO_lib() function created with this script is run, it modifying the server.lua file so that it writes multiplayer chat messages to a certain text file, and also outputs as chat messages any text seen in a different text file. This code is INSERTED into the server.lua file, so any mods (such as a future version of servman for A-10) are NOT disabled/overwritten. Furthermore, a backup is made of server.lua into server_old.lua, before this operation is done, just to be safe. After this is done, then the game CLOSES. So the very first time that init_IO_lib() is run, the game will appear to CTD (it is not really a CTD). With server.lua now inputting and outputting text from these text files, the game runtime is able to interface and read and write from those text files as well, allowing things such as setting a flag based off of someone saying “getupdate”, or outputting a group’s average position in MGRS as a multiplayer chat message. Note that the script ONLY inserts code into the HOST’S server.lua file. It does not modify clients in any way; indeed, to my knowledge, modifying clients is impossible. I intend to eventually create a youtube instruction video for scripting. In the meantime, this document describes how to use the chatIOlibv1. Basic setup: 1) In your mission, create a ground unit, and hide it far away from the action in the corner of the map. For this example, call him "scriptman" 2) Create a triggered action for "scriptman" of type Command->Run Script, and insert the chatIOlibv1 script in the text field. If desired, add your function calls to the END of the initialization script. 3) Create a trigger to run this script. Make a ONCE->TIME MORE (1)->AI ACTION(Run Script(scriptman, <name of chatIOlibv1 script>)) 4)Now create another triggered action for scriptman. Make it another “Run Script” action, and insert the text “init_IO_lib()”. This will call the global lua function that will install the necessary code to support these scripts into server.lua. 5) Create a trigger that will run THIS script now. You might want to include a warning to the host that his server.lua file is going to be modified; that is why this is a separate function. Regardless, common coding sense plus testing indicates that these modifications are harmless. The trigger type needs to be a ONCE -> TIME MORE(<some time greater than 1 second) -> Run Script(scriptman( <name of script that does init_IO_lib()> ). 6) Now you are ready to insert your function calls as more “Run Script”-type triggered actions for scriptman. See the example mission and the descriptions of the global functions below for more information. chatIOlibv1.zip

Solo comunicaros que he subido una nueva y posiblemente ya definitiva version del DCSExporter. Esta herramienta permite exportar los logs de una mision multijugador en formato .xml y con mas detalles. Muy util para los escuadrones que tengan tablas con puntuaciones de sus pilotos etc. Si a alguien le interesa el codigo fuente en (C++ y C#) que me lo comunique. Por cierto, estoy metido en un proyecto (una especie de campaña dinamica online) que involucra el DCS y silverlight (C#), si a alguien le interesa participar programando un poco puede contactarme. PD: Link de descarga el DCSExporter: http://files.lockon.ru/en/161/ Archivo en .xml de ejemplo (para que veais como queda el resultado): http://rapidshare.com/files/453873003/Example.xml

Refueling Training Mission Nevada, Beta 2

I've posted Wags' profile and mine here: http://forums.eagle.ru/showpost.php?p=1153314&postcount=3

Id anyone is interested here's some video lessons on different systems on the A-10c their very well explained http://www.youtube.com/user/Tigerpwrr#p/u/9/vdn9aHS9ZO0

Ход ручки замеряй по ее центру, у тебя как раз примерно и будет 170мм.

+1

Doesn't matter - as in wouldn't have made a huge amount of difference. Not 'later'. It was known all along in terms of its WEZ - but it didn't help anyone ... including those MiGs that got into BFM with eagles. Wrong again. R-77 may have been equivalnet to a 120A/B, but the C left it squarely in its dust in every parameter that matters. And when it comes to the A/B, the R-77 couldn't match it in production anyway ;) Not really. The Su-27 is an excellent low-altitude dogfighter with great turning characteristics at slow speeds. Up high where the eagles like to fight, it lacks in energy. It all depends on whose fight you're going to fight. ... but rather lacking in avionics and BVR/SA capability by comparison. The MiG-29 has its own advantages in terms of aerodynamics, but it is once more very much a 'depends when and where' question.

+1

Well, the server ran the free-flight mission for testing purposes. So we thought it's not that important to get the pilots on comms. ;) Great you had fun!

Bingo! :D That was great session on Jabog32 server IIRC. No TeamSpeaking and fun ;).

You have to contact ground crew via intercom (or shouting if engines are off and cockpit door open) and tell them to re-arm and re-fuel using comms. menu. Theres a switch in left panel that controls which radio you are currently transmitting, it has three positions, VHF2, VHF1, and intercom. Turn this to intercom and you can contact ground crew when landed on a farp or a friendly airbase. Only repair is made by waiting 3mins with engines off. When repairing it's handy to leave the door closed so when it opens you know repair is done. If you have no damage nothing will happen. You can shoot Vikhr just fine during darkness but you can't lock targets with Shkval without artificial illumination. You need to have scripted illumination or bring your own illumination rockets or a buddy with them. Or you can just hover very steadily and point the Shkval to the target without locking it and it will stay on target as long as you don't move. Hover hold keeps the chopper in one place very well but the altitude hold is a little bit trickier and might need some babysitting. If the designator is fried you will simply not get laser range as if the designator was turned off. There's no indication if it's working or malfunctioning. TPEHAX means targeting computer is in training mode and won't allow firing. NAY3A means laser cooling cycle is in process and it's inadvisable to use laser during the countdown. It doesn't really do anything but tell you to wait a little. If you have to you can still use laser.

Fly the Shark with only one Engine gives you also a new feeling of that Sim.:thumbup: :lol:

I was in that formation (Harcust). I think I'm on the far left. It was on the free flight server the other night. I believe that is me in the bottom picture also. My screenshots don't compare though... very nice.

Graphics look amazing but there's something wrong with the roll rate :P

Eventhough your setup is very impressive, I would probably go for smaller screens (if I could afford it) since the virtual cockpit is now bigger than the reality. It feels like my 2 years old is flying the hog (size wise of course). Maybe you can adjust the fov so you have a 1:1 cockpit size and huge surround vision of the landscape? That would be really cool.

+1 +1

In my book : no TS=no immersion=no fun because everyone is lone-wolfing It's as vital as having TrackIr.

All medium to large helicopters, and many small ones, have some kind of stability augmentation system. Pilots practice flying without it in case of emergency. The other 99.99% of the time, they fly with it on. Why? The power steering analogy is best so far, I think. The beauty here is that it's your game and you can play it however you want. If it makes you feel more in control to fly with AP off, more power to you. Just don't go telling the rest of us that we're missing out on something by using the AP all the time, because we're clearly not.

It is great tool but *Yes I am boring with that* most servers have forbidden ACMI recording due to some bugs in game... Hope ED will take care of that to have ready acmi after flight without replaying whole hours of game again :(

False sense of accomplishment :music_whistling:

I try to welcome rookies and push them in the right direction of learning a hardcore sim and I'm not the only one. It obviously takes some time and effort. This kind of ideas and frivolous attitude towards training makes it harder. This is why I will welcome such initiatives with a caring although firm :smilewink:

Ein Screenshot wäre hilfreich. Ansonsten kann ich nur vermuten, dass du eine seltsame FOV Einstellung hast, eine andere Erklärung hab ich dafür nicht.

Well, the two photos with the C-47 were rejected for being 'soft'...right. Anyways, I'm thinking of putting this photo on there: What do you guys think? Regads, Diego

Here is a shot I got this Saturday: Regards, Diego

Bump - added Fun with Cities Part 2. Link at the top. :-)

New update: (tails almost finished: working on some missing parts and animation axis)

Latest & greatest....

High res ? :thumbup:

Its only $500.00. You can get any joystick. The more buttons the better. You can always setup modifiers as well. I use CH products. Its a bit cheaper than the Thrustmaster and I have had it for 5 years now with no problems.

reworked some details

Потому что нужны Фантомы и МиГ-23МЛД:music_whistling:

Да он издевается над нами! :D

You don't have to be a rocket scientist to figure that out! It's where they keep TrackIR when they're not using it.

If you want to know all there is to know about trim in A-10C then you need to watch

maybe you mean something like this: wich nozzle looks better? 1- grey plates or 2- dark grey plates and some screens: here added blood to the canopy The pretty sea flanker :thumbup: Combatace: I edit some files let me know if you want it

Thanks guys! Glad some people are liking it. I'm away in Dallas until late wenesday. When i get back I'm going to implament a script by Speed that will allow each player to type commands in chat instead of needing the host to use the F10 other radio commands. Cant wait to get that put as it will be key for long runnings on servers the host is not around on.

I could make an iPhone app for a mission card pretty easily, but I don't have the know how to automatically send the Mission briefing info to the phone... If there's enough interest out there (and nobody else is already working on it) I could make a standalone app that allows you to quickly tap/scroll pertinent info for a mission. My thoughts of the basic most important info (that I usually jot down on a notepad) would be: Flight names and their mission Frequencies Enemy threat types Time on target Any other ideas? Should I begin to write some code?

Time for a little bit more Su-33 pr0n :D