tietze

Yep, but I'm just experimenting with using JSGME - automating it all for my lazy shiny metal a.. ;-) (when using the -remove files I expect JSGME to backup/move files as needed) [edit: Yes, it works - JSGME backs up the the files to "!BACKUP\Mods\aircrafts\Ka-50\Liveries\Cockpit_Ka-50\english"]

Just checked the JGSME manual, it is possible to add empty files appended with "-remove" to remove files for JGSME-mods! I've tried to add the -remove to the bunch of files inside the english folder, file attached (but I have not tested it yet myself) JGSME-remove for Ricardos Blue HD cockpit.zip

Yup! You can further append the following when TACView 1.2.3 and TARS 1.0.2.b2 is installed and configured (TARSExport.lua & TacviewExportDCS.lua should also be present as well as the relevant files in the DCS World folder in Program Files): dofile(lfs.writedir()..'Scripts/TARSExport.lua') local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewExportDCS.lua')

Hmm - checking the presence of the Export directory might not be the smartest way to ensure what version is running. Maybe it was better to check the version number? Checking the version of the SU-25T module could be an option (but I'm sure there is a better way): declare_plugin("Su-25T by Eagle Dynamics", { image = "FC.bmp", installed = true, -- if false that will be place holder , or advertising dirName = current_mod_path, fileMenuName = _("Su-25T"), version = "1.2.3", [...]

Imdisk is opensource and free: http://www.ltr-data.se/opencode.html/#ImDisk But DCS weighing more than 8GB is a tad to big for a ramdisk in my system.

It works nicely!

That is a really nice find :-) Works nicely putting everything into the "Saved games\DCS\Scripts"!

As far as I can figure out it means that if TACView detects an Export directory present in the old location* it thinks you have not updated to 1.2.3.9871 and accordingly will install the the export script into the old location*. If it does not detect the old directory* the TacviewExportDCS.lua will be installed in the new location** and the Export.lua in the new location will be modified accordingly. For more on this change there is this thread: DCS 1.2.3 & TARS 1.0.2b2 (+Helios). *C:\Program Files\Eagle Dynamics\DCS World\Config\Export **C:\Users\USERNAME\Saved Games\DCS\Scripts [Edit: I wonder if you update from 1.2.2 to 1.2.3 using the autoupdater if the old export directory is actually deleted or moved, if this is not the case it might not work]

I can see that trim was only mentioned in the first post. To me it is important to get the proper trim when in the pre-contact position. If you have mapped trimming of the pitch and roll-axes to one of your joystick's HAT-switches you can try to first 1) stabilize the aircraft with stick 2) trim it to level flight, and then 3) completely fly it in level flight making small adjustments with the trim-HAT (pitch) and throttle. Everytime you change the throttle you will have to change the trim of the pitch axis. Usually when the aircraft is trimmed to level flight at the correct speed behind the tanker you can just compensate for the engines causing pitch with the stick. Please note that the pitch trim changes when you open the refueling inlet on the A-10C. This older thread has some nice tips and pictures as well: Inflight refueling - like dented pig noses and link to interesting part of the AAR manual.

The file: C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\ABRIS\Options.lua Change the order of line 457 & 458 (DCS Version 1.2.3.9871), so the line with the decimal option is first. Do the same for the second coordinates located at line 464 & 465. From post by Ironstrike: http://forums.eagle.ru/showpost.php?p=1431202&postcount=15

You bet - and it works nicely :-)

Have you tried to enable the export-setting in the network.cfg in saved games/config, as c0ff has mentioned here? http://forums.eagle.ru/showthread.php?t=102034#5 Is it actually needed for TARS to work?

Yeah we gotta support him - it's a great and promising project that I really look forward to! :-)

Just saw the new banners, thought - hey maybe that is allowed on the ED-forums, apparently it is (looking at Ali Fish's signature ;)).

Second thought. Something else might be going on here: I'm seeing my 1GB VRAM maxed out all of a sudden (checking with GPU-Z). This causes some drops in FPS probably because textures are loaded and unloaded more frequently.

Removing smokecloud.pfx, still helps in 1.2.3.9871. With the cloud in place it only seems to bug my system down when speed relative to ground gets up. This hints that the more dust is generated the bigger the FPS-penalty. When looking closer at the dustcloud, it seems two dust clouds of different color are puffing up - one white and the other yellowish. In a somewhat stationary hover the FPS does not drop much with dustcloud (FPS ~ 31): When going faster the dustcloud/trail hits FPS hard (FPS ~ 13):

Yup, depending on which aircraft you are configuring open DCS World, go into the Options the page and then the CONTORLS tab. In the upper left corner there is a text "Layers" and a drop down menu where you can select between different aircrafts and game modes for example for P-51D there will be both a game and simulation mode as far as I remember. To configure buttons and keys you can just go ahead (use the buttons at the bottom and choose the correct line and column in the schema). It can be a good idea to clear category for your controller, because DCS usually has some strange default configurations for controls Please be sure not to choose clear category for the keyboard! To configure your joystick axes choose Axes Commands from the second drop down menu at the top or press the "Axis assign" button at the bottom. Not to be rude, but check out the manual for the DCS user interface: Start->Programs-> DCS World->Documentation->User Manual. Page 18 is for configuring controllers.

Yup, c0ff mentions it here: http://forums.eagle.ru/showthread.php?t=102034#5

In addition to what paulrkiii says my buest guess is that the advantage is a clean up of what-goes-where. So export scripts (and everything else that modifies DCS) goes into subdirectories of the Saved Games/DCS folder. This has the advantage that users are not needed to mess around in the DCS World folder (usually located in the program files folder). This probably makes "errors by messing around" less likely to happen, which could make life easier for both people making/creating export-dependent mods and for the following installation and use of those mods (not to mention providing support and fixing broken behaviour of DCS).

As you have experienced crossfire (or NVidia's SLI for that matter) does simply not work with DCS (World). In my experience multiplayer framerates have always been a tad lower when going into multiplayer. That said I must admit that the general framerate seems to be much more smooth in multiplayer in the new 1.2.3.9871 version of DCS World just released. For me still a significant framedrop persist with low level flying 1-3m when dust is generated (which is probably related to the smokecloud.pfx, that can be moved/deleted/renamed to resolve this). This thread might help: Bad FPS? Give these a try, pt. II

Take a look at c0ff's post and the following replies at the following link. What was before configured by config.lua (like: EnableExportScript = true) in the DCS World/Config/Export directory is now configured in network.cfg in your saved games/config directory: http://forums.eagle.ru/showthread.php?t=102034#5

Thanks for some really entertaining missions! :-)

Thanks! :-)

So the restriction imposed on export regards other objects than the "client" itself. That is you are always able to export what pertains to the client craft (sensors and dials for example), but not able to get information about any object?

Yep, it seems not to affect whether you are able to export yourself - even when running a server.