Jump to content

airdog

Members
  • Posts

    620
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by airdog

  1. Peter I would download the TS3 x64 client from here and uninstall/reinstall TS3. I am thinking that you may have the 32bit version of TS3 installed. Your other choice is to install the tars_32.dll plugin in place of the 64 plugin and see if it works. One thing to remeber is when you check the Tars plugin in the TS3 menu close TS3 and reopen it then check to see if its active.
  2. Make sure that TARS and DCS are running in administrator privlege mode. After you use the LCTRL(whatever) to select your radio you will then use your regular PTT switch to speak to eachother. That is provided that you are both on the same frequency. Also make sure in the tars control click on the A10 picture make sure that standby is unchecked. Also make sure in Teamspeak that you have the TARS plugin selected in the settings>plugins window. Thats what I can think of right now. If its still not going after all that let us know whats up
  3. Just click in the resolution box(not on the arrow that cause the box to expand) and backspace out your res and type your own. ITs that easy.
  4. They do it to Phuc with you and you are taking it hook line and sinker!
  5. Same works for the EKRAN EKRAN.Lua dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON purposes = {render_purpose.GENERAL} try_find_assigned_viewport("EKRAN","MFCD_05") -------PAGE IDs------- id_Page = { PAGE_NULL = 0, PAGE_OFF = 1, PAGE_MAIN = 2 } id_pagesubset = { MAIN = 0 } page_subsets = {} page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."EKRAN\\Indicator\\EKRAN.lua" ---------------------- pages = {} pages[id_Page.PAGE_MAIN] = {id_pagesubset.MAIN} init_pageID = id_Page.PAGE_MAIN use_parser = false My Monitor Config: _ = function(p) return p; end; name = _('Airdogs Pit'); Description = 'AirdogsPit' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.77777777777778; } } Shkval = { x = 575; y = 1152; width = 930; height = 345; } ABRIS = { x = 1675; y = 1461; width = 754; height = 495; } PVI = { x = 2275; y = 1070; width = 550; height = 120; } EKRAN = { x = 1750; y = 1200; width = 235; height = 80; } UIMainView = Viewports.Center You can also do the same for the UV26 digits
  6. Uncomment this line below in your CMSC Lua purposes = {--render_purpose.GENERAL Take out the --
  7. Yup same folder just in the A10c folder though. I'm pretty sure this only removes the MFD's. But it can remove the RWR if you use the viewporthandling RWR .lua that was new to 1.1.1.0 Some people have just used their 1.1.0.9 rwr .lua file in 1.1.1.0 and 1.1.1.1 and it works fine but requires that you edit the {--render_purpose.GENERAL in that .lua file. This link here http://forums.eagle.ru/showpost.php?p=1325507&postcount=269 shows how to do the RWR starting with 1.1.1.0 and continuing into 1.1.1.1. Like I said though you can actually just copy over your 1.1.0.9 rwr lua and it will work but you have to comment out the render line within that file to make it go away in the cockpit view. Hopefully this wasnt to confusing.
  8. Go here: x:\Program Files\Eagle Dynamics\DCS Black Shark 2\Scripts\Aircrafts\_Common\Cockpit and open up the ViewportHandling.lua and comment out line 31 with a -- Just commenting out this one line will kill the shkval,abris,pvi800 and the EKRAN. example below purposes = [color=red]{--render_purpose.GENERAL[/color], render_purpose.HUD_ONLY_VIEW, render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always render_target_always = true end
  9. BS2 is a totally separate install. It does not touch anything in BS1 install.
  10. Yup its the Gyro and it is like that in real aircraft too. Even new aircraft with glass cockpits still have standby gauges that still make the humming noise as the gyro spins down.
  11. And with all that info you provided we'll have it fixed in no time. You just sit there and we'll be right back to you ....dont move it won't take hardly anytime at all.
  12. Thanks downloading the torrent. Special thanks to the Texas comcast customer who is seeding at big time speeds!
  13. I would say that is much better than a "junkyard" cockpit. It's not a bad setup at all. You can have gauges for that setup in under an hour just go HERE and get Helios. It is donationware so its free to use the full version and if you like it please donate to the developer Gadroc. Tons of support on their forums as well as here.
  14. I did it and got a minor improvement but I was not having major issues either. I can say it does not hurt to try it.
  15. You really need to hinge the Warthog stick to fold forward and you would have no problem making the long flights because you have a built in urinal there too ;)
  16. Your missing Helios http://www.scsimulations.com DCS only exports the text the rest of the stuff needs to be done with Helios software. It is Donationware so its free to download and try but please donate to the developer if you continue to use it. You will get all the help you need on their forums to get it up and running.
  17. First item that needs to be cleared is that in windows monitor setup your main monitor needs to be the most right monitor with your secondary display to the right. You can physically put the secondary monitor to your left but in windows monitor setup it can't be there. I'm pretty sure that A10 requires that the main monitor be the right most monitor but if it doesn't it sure makes it easier to do this setup. In the a10c options page set total res to 3840x1440 and do not change the aspect ratio that it calculates. Make sure full screen is unchecked Now try this monitor setup .lua _ = function(p) return p; end; name = _('2 Monitor Setup'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1.77777777777; } } LEFT_MFCD = { x = 2560; y = 0; width = 1024 height = 1024 } UIMainView = Viewports.Center
  18. Your description in the Lua(in red) makes it sound as if you have 3 monitors. But you describe it as if it's only 2 monitors. Which is it?. The script below is assuming that your 2nd monitor is to the right of your main monitor and that you want your MFD's on the second monitor. Total resolution should be 3840x1440 in the options GUI Try This. _ = function(p) return p; end; name = _('2 Monitor Setup'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1.77777777777; } } LEFT_MFCD = { x = 2560; y = 0; width = 640; height = 640; } RIGHT_MFCD = { x = 3200; y = 0; width = 640; height = 640; } UIMainView = Viewports.Center
  19. Since you provide us with absolutely nothing to help you with my answer to why your EKRAN is not working is: YOU DID IT WRONG! Mine works perfect no problems at all when I followed Hellfrogs directions. MAybe is you take the time to put up a copy of your ekran lua and monitor lua someone could help...but "EKRAN dont work" is absolutely worthless info to us.
  20. ITs been awhile since ive used my cougar but from what I remember you may havew to do this: Open the HOTAS COugar Control panel in the axis setup tab click box box 7 in the microstick X row and click box 8 in the microstick Y row that will make the red plus sign move to those columns. Now at the bottom for the toe brakes move those red pluses over to columns 8 and 9. That should make windows recognize those axis as windows only sees the first 8 axis's in a single controller. Hopefully im correct on this...as I said above its been awhile since i used mine.
  21. Go to the Helios editor and then to your a10c interface tab. Click the setup export button. Just too make sure that the export.Lua is setup properly for Helios. if it says remove setup do it and then hit the button again.
  22. 1110 exports seems to work just like 1109 except for the fact that you can use the 1109 RWR .lua file in 1110 or not. The fresh 1110 install has a different RWR lua that you can modify the way I did or you can just replace it with the 1109 style lua and do it ragtops way...is this making sense??
  23. Ok...very interesting that they changed the way some were scripted in .lua but they work both ways. No point in changing anything if yours works....I guess its nice that there are 2 ways to do it now. Thanks for letting me know.
  24. Paccus FFB Alien Vehicle Joystick For only 5000 euros!!! Get yours today!
×
×
  • Create New...