Tetra

Was just looking at screenshots for the up-coming release of Europa Report and noticed the set designers decided to go with the TM Warthog throttle as the controls for their space capsule lol. :thumbup: Also noticed in another screenshot you can see the top of the stick too!

Sadly not, until ED decide to allow script access to the function calls for the FC3 RWR's its just not possible. :(

Would be very surprised if those figures were accurate, I highly doubt they are. I love steam, have plenty of titles on my account, however DCS will never be one of them, there is no advantage (at this point at least) for me to move my standalone install over.

Personally think gimping the free option that comes with DCS world would be pointless. The entire premise is to draw in new potential simmers and not give the false illusion that the game only plays out similar to something such as HAWX, which game mode kind of feels like. The huge influx of steam users was only to be expected, the product is free, everybody is going to try it just for the sake of it as they have nothing to loose. However I would bet out of all the users who "tried" it only a certain percentage stuck to it, learned the SU-25T and enjoyed it and will potentially purchase more modules because of it. Those people are the actual customer base that it was aimed at, the rest will just drop away after a while when they realize flight simming is not something they enjoy or have the patience for.

No probs, attached it to this message. Just extract the A10.ini to INSTALLPATH\Abbequerque Inc\FaceTrackNoIR\Settings\ I use a modified Accela filter curve as well as tweaked axis curves. Smoothing set to 1 sample and obviously with pointTracker as my tracking source. Protocol FreeTrack 2.0. Works absolutely great for me. Nope it works right "out the box" so to speak. The FtNIR FreeTrack 2.0 protocol does not need any modified dll's like FreeTrack does. There are a few setting you need to tweak though. Mine are listed below. A10.rar

lol..the pointy things that kill things.

I strongly suggest you drop Freetrack and try FaceTrackNoIR with the point tracker option. I used Freetrack for ages and although it worked fine it never felt satisfactory. I have a similar setup to you, PS3Eye and FreeTrackNoIR with a trackclip pro. It is incredibly smooth with a little bit of tweaking. If you want to try it I can send you my profile. Freetrack has not been updated for ages, FreeTrackNoIR is still in development and even has it's own TrackIR protocol.

Steam sales are not enforced by Valve, it was ED's decision alone for these items to go on sale on the steam platform. The possible benefits of expanding the potential customer base, who many will in-turn purchase subsequent and future modules at full-price FAR outweigh the minor amount of money ED made during a one day sale. Don't feel sorry for ED, this was a good marketing strategy which will pay dividends.

You can also obtain your heading/range from bullseye with the TAD and find or make any bullseye call the same way. Fish's had a good video on the TAD, the second half covers the various techniques for hooking the bullseye to do the above.

Did you check all the above I posted about the correct game/sim mode for the controls? If so post a quick screen-shot of your axis section in the controls options.

Post a screen-shot of your throttle assignment in the DCS world input screen, would be easier to tell what's going on. Normally to assign (if you haven't done already) just go to the Axis section, double click on throttle under the X-52 column and then when the pop-up screen comes up just move the throttle all the way forward and back until it shows the correct input in the box. EDIT: Also to note...make sure you are using the correct version of the controls. I don't have the P-51D but if it's anything like A-10C you should have "P-51D SIM" and "P-51D GAME" in your controls dialogue. One set of keys is for when you are flying in game mode (simplified flying kind of arcade style) and the other for full sim-mode (the real deal). You can change which mode you are in by going to the options and then gameplay tab and make sure it is on Sim (if you want the full realism). Have a look at mine for reference. Note that turning on "Game Flight Mode" and "Game Avionics Mode" will essentially put you back in to "Game mode" so make sure those are turned off. When you are done setting that up then hit OK. Then go back to the controls options and assign your throttle and stick axis under the "P-51D SIM" drop down in the controls settings. That way you will be flying in "SIM" mode and your controls will also be assigned to "SIM" mode. Also if you did clear your joystick mapping but did it in game mode by accident then follow my previous screenshot again making sure you are clearing the "Sim" mode controls.

For safe measure try the following. In the above make sure you do them in number order 1/2/3/4/5. Do the same for the "Axis" drop-down too. This will clear ALL the currently assigned X-52 controls in DCS world so nothing from your HOTAS should be defined in DCS world any more. Now go back to the axis drop down and set up your throttle axis and your joystick pitch/roll axis, these will probably be the only two things you need to assign in DCS world directly. Now Ok all that, close DCS world, run the Saitek profile in the Saitek control centre (system tray) make sure it goes green and the profile is shown on the MFD. Now launch DCS world and try again. Usually (in the case of Saitek profiles) rotaries simply send key-presses as the rotary moves, so it's not treated like a normal axis as such in the profile.

The Saitek profile you downloaded should basically be a representation of the keys laid out in DCS World. Ie if you hit a button on your HOTAS it will send that keystroke to DCS, there should be nothing to set up aside from assigning your throttle and the joysticks X&Y axis in DCS world. So load your profile first in the Saitek software, make sure it is running, then launch DCS World and the keystrokes should be sent through to DCS. Once inside DCS just assign your throttle and joystick to the appropriate axis functions for the P-51D and you should be good to go. The Import function in DCS is just for exporting and importing the actual assigned keys/joystick functions if you have assigned things directly inside DCS world, in your case that should not be necessary.

Its definitely the best way. Did something similar myself, also have a second bat file launch at the end of the launch bat which monitors if the DCS launcher is still running (ie. you are still playing) and if you aren't it quits all the of the processes you launched in the first one, or you could use it to re-launch the processes you killed when you finish playing if you liked in the :Kill block. DCSLAUNCH.bat @echo off Echo DCS LAUNCHER ECHO. timeout /T 1 /NOBREAK > nul Start "AutoHotKey" "C:\AutoHotKey_VoiceAttack\WH_DCS_A-10_VAC_PTA.exe" Echo AUTOHOTKEY RUNNING... timeout /T 1 /NOBREAK > nul Start "Voice Attack" "C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe" Echo VOICE ATTACK RUNNING... timeout /T 1 /NOBREAK > nul Start "Helio" "C:\Program Files (x86)\Gadrocs Workshop\Helios\HCS.lnk" Echo HELIOS STARTED (BEGIN PROFILE!) timeout /T 5 /NOBREAK > nul Echo STARTING FACE TRACKING SIT BACK... timeout /T 5 /NOBREAK Start "FaceTrackNoIR" "C:\Program Files (x86)\Abbequerque Inc\FaceTrackNoIR\FaceTrackNoIR.exe" Echo FACETRACKNOIR RUNNING... timeout /T 3 /NOBREAK > nul Start "DCS World" "E:\Eagle Dynamics\DCS World\bin\Launcher.exe" cls timeout /T 1 /NOBREAK > nul Start /min "BAT CHECK" "E:\DCSBAT\DCSCHECK.bat"DCSCHECK.bat @echo off Echo DCS IS RUNNING... :WAIT timeout /T 8 /NOBREAK > nul tasklist /fi "imagename eq Launcher.exe" | find /i "Launcher.exe" > nul if errorlevel 1 (GOTO KILL) else ( GOTO WAIT ) :KILL taskkill /F /im FaceTrackNoIR.exe >nul taskkill /F /im VoiceAttack.exe >nul taskkill /F /im WH_DCS_A-10_VAC_PTA.exe >nul taskkill /F /im HeliosControlCenter.exe >nul exit

Reported and replicated by Nate in this thread > http://forums.eagle.ru/showthread.php?t=113302

That would be awesome, is it possible to create varied shapes also? I notice many of the clouds seem to be of a similar structure in vanilla DCS? Anyway thanks again, really enjoying this mod.

Huge thanks for this, having the information in one place is absolutely invaluable! :thumbup:

Just picked up CA, great discount, many thanks :)

Steams usage of the word "DLC" is not exactly correct, although some could argue it still applies. As you know, DCS World is the platform required to run any module you purchase. It's free, it even comes with the SU-25T, again, for free. In this case you are not being denied something that should have been "included" in the base game as is the case with a lot of DLC content that is sold for other games. It is very clear, you can get DCS World for free, if you want a module you purchase it, clean and simple. In the case of the Huey it is still in development, you purchased the beta, you will get the final product, nothing extra to pay, no other action required, if you didn't want the beta then you could have waited for the final full release before purchasing. Finally what cichlidfan said is correct, nearly every module, even FC3 has been on sale at some point in the past few months. Does it sting when you bought something that a week or so later goes on sale? Of course it does, but to be fair it is your decision alone when you purchase a module, it is well known that ED does great value sales, as has been demonstrated numerous times in the past.

Awesome stuff many thanks! Was only the other day I was looking at the original across the air base and thinking how it could really use an overhaul!

Good choice :D ! You certainly won't regret it (aside from maybe having to explain to the girlfriend maybe lol). It will definitely take some time to re-learn the layout, when I switched from my X-52 to the Warthog it was like going back to square one again, nothing was where I my muscle memory had remembered it to be, but after a few hours it becomes like second nature again. Trim hat is defaulted to view control with trim being a shifted function on the default layout. Only other thing I would suggest is get some serious curves and saturation on the slew nub, its way too sensitive with the default setting. As for rudder yep pedals next for sure lol, although a lot of people have success using the fake friction slider for rudder and then setting up wheel brakes on either the paddle or a shifted button. Get some pedals though and you can use the friction slider for zoom or whatever you like. Anyway enjoy!

These look great many thanks!

Ok disregard, seems to be a problem with my model, larger sized models seem to freak out the physics somewhat, while they retain weapon collisions the AI don't seem capable of navigating around them for some reason. Also models which are large in width but short in height (for example 100x100x1) instantly seem to loose collision. Will post my finalized lua and lods files later along with any further findings for anybody who finds this thread with a similar issue. EDIT: Final LUA and lods file for anybody that has a similar issue who needs them. From further investigation it seems the height of the object needs to be at least %10 of the width to prevent the collision shell physics from breaking (so a 100mx100m object would need to be at least 10m tall for example.) MyModel.LUA mount_vfs_model_path (current_mod_path.."/Shapes/"); mount_vfs_texture_path (current_mod_path.."/Textures/"); GT = {}; GT_t.ws = 0; set_recursive_metatable(GT, GT_t.generic_stationary) set_recursive_metatable(GT.chassis, GT_t.CH_t.STATIC); GT.chassis.life = 5000 GT.visual.shape = "MyModel"; GT.visual.shape_dstr = "MyModel"; --Burning after hit GT.visual.fire_size = 0; --relative burning size GT.visual.fire_pos = {0,0,0}; GT.visual.fire_time = 0; --burning time (seconds) GT.time_agony = 1; --Name Stuff GT.Name = "MyModel"; GT.DisplayName = _("MyModel"); GT.Rate = 1; GT.DetectionRange = 0; GT.ThreatRange = 0; GT.mapclasskey = "P0091000076"; GT.attribute = {wsType_Ground,wsType_Tank,wsType_Gun,wsType_GenericFort, "Fortifications", }; GT.category = "Fortification"; add_surface_unit(GT) MyModel.lods model = { lods = { {"MyModel.EDM",1000000.000000}; }; collision_shell = "MyModel-collision.edm"; }

Thanks a lot man, glad you found it useful :)

Just to add to this, strangely I noticed that my LOD settings work fine in both the standalone model viewer and the DCS world one, I set my primary LOD to 50, zoom out in the standalone viewer and the model disappears as expected, so it's obviously reading my Lods file. However in the DCS world model viewer my collision mesh does not show with "showcol" but yet it does in the standalone model viewer. Wondering if there is some naming convention discrepancy between the two applications. Also in-game my lod settings are not being read at all, model is still there out to full visible range. EDIT: Ok well I guess the reasoning is my lua file simply isn't using my lods file for some reason. Anybody got any idea how to call the lods file from the LUA script? EDIT2: Ok getting somewhere script should be calling GT.visual.shape = "MyModel";NOT GT.visual.shape = "MyModel.edm";LOD settings from the lods file is now being read in-game, collision still not sure on yet, will continue testing. EDIT3: Collision still not working ..