Tumbleweed

Happy Christmas all.

Hey, that's awesome work. I'll give that a try. Many many thanks for sharing :thumbup:

Hi, I ordered a cheapo 7" reversing TFT colour monitor from eBay which accepts HDMI and VGA. It's arrived and all up n running but I'm having problems setting up a working monotor lua configuration so I can put some instruments on the 7 inch display. I've searched around and tried various things from posts I've read but most of them are out dated. What I've done so far is create a simple monitor lua which I'll post a little further down. I've turned off full screen in game and set the resolution in game to the combined resolution of both monitors. I've checked and in Windows, I have my big screen as my primary with the desktop extended on to the 7 inch screen. In the windows display options, the main monitor is the left most monitor with the smaller 7" monitor set up immediately to the right but at the top. I have the main viewport set up and working okay in the LUA but I can't seem to get any instruments to export to the second monitor. What I keep getting is this (see attached image) no matter what things I try to export. Here's my monitor LUA: Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.7777777777778; }, GUI = { x = 0; y = 0; width = 1920; height = 1080; }, ED_A10C_LEFT_MFCD = { x = 1930; y = 10; width = 600; height = 600; } } UIMainView = Viewports.Center Any help really appreciated! Oh, this is for the 1.5 DCS BTW! Sorry, should have said. Thanks :)

1.5 and 2.0 are not updates they are Beta and Alpha release candidates - respectively. Their sole purpose is for testing and bug hunting. Anyone wanting stability should remain on the stable 1.2 version until told otherwise. The Alpha and Beta are optional installs ONLY for testing and are not, I say again NOT updates. To be fair, both 1.5 and 2.0 both clearly state what they are so the problem is with the people downloading it expecting it to be the next evolutionary step in DCS when it isn't. Not quite yet. Everyone is welcome to download the Open Beta and Open Alpha and contribute to hunting out those pesky bugs, that's what they're for but this is optional.

Just an update for anyone that's interested or has experienced this behavior. As it turns out, there are two spots on my HOTAS throttle (Z Axis) that interferes with the Mini Stick and Rotary Scroll Wheel. The first position is around the Idle dent. The second position is around the Afterburner dent. The afterburner dent area is far more affectred than the Idle dent I hasten to add. The affected areas on the throttle are only small. If you move the throttle quite quickly the Mini Stick and Rotary aren't always affected. The area is jumped over too quickly to register and so only occasionally interferes. If you move the throttle more precisely and slowly over the affected areas, the interferance happens 9 times out of 10. This is the reason I could never reproduce the problem before. When testing in the past, I moved the throttle too quickly to see the problem. The issue is now definitely confirmed to be a fault with the Throttle part of the X-52 Pro HOTAS. It cannot possibly be anything else. I've since been in contact with Saitek / Madcats who have kindly agreed to RMA the unit. At this stage, short of opening the unit up myself, there's nothing else that can be done other than returning it. I have to add and give credit where credit is due. Saitek support have surprised me. I've read quite a few bad stories about their products and support prior to and since owning my X-52 Pro. In this instance, they seem to be quite helpful and supportive. To be fair, they didn't have to RMA my HOTAS since I got it over a year ago but in fairness, it's not been right since I got it. They did say I should have told them about the issue sooner but what would I have told them? I had no information to give about the problem or any idea where they should begin investigating. I didn't even think in a million years it would be the HOTAS hardware. I just put it down to me being a noob and something conflicting like a binding somewhere I'd not found and just put up with it. So credit to Saitek so far for being helpful. Unfortunately, I'm going to be without wings for a while :( F-15 Cold Turkey..... I'm sending the HOTAS back tomorrow or Thursday and I'll keep this post updated for anyone that might find this of use. I just hope that if they do replace it, the Rotaries, Slider and Ministick aren't as rough as mine were.

Hi, I'm hoping someone can help me with my X-52 Pro it's behaving rather odd. What is happening is this (and I think it's been going on since the day I got the controller): Whenever I push my throttle near the afterburner dent, it affects the mini stick AND the rotary scroll wheel on the back of the throttle handle. Both of these move when the throttle is near the AB dent. The ministick pulls all the way to the LEFT and the Rotary wheel scrolls one notch forward in sympathy. I can move the throttle towards and away from the AB dent and it continues. Now I say this has been happening since day one because sometimes in game, my screen randomly jumps view and back again which I always put down to my homemade TrackIR being glitchy and picking up points of light here and there. It did seem as if it was when I went into burner but I couldn't find anything wrong to back this theory up initially. Today I was in the Game controller properties in windows after buying some switch cleaner to attack the worthless roatary dials with when I saw it happening for the first time. You can clearly see the mini stick and rotary on the back of the throttle moving in sympathy with the throttle when it nears the AB dent. It does it 9 times out of 10. In game this is obviously causing a conflict when I go into AB hence the dodgy view jumping and flickering in game. Since this is happening in the Game controller properties directly it's not then due to binding issues in the game. I don't use the Saitek / Madcat programming software. I only have the driver installed. As I say, it's been doing this for ages but I've never been able to put my finger on the problem until now. This is also a reasonably fresh windows install and still it happens. This definitely isn't right. Any ideas please anyone? (other than throw the thing in the bin and buy a warthog) :music_whistling: Cheers! :thumbup: See the video below and you can see the Rotary wheel (located around button 19) and the mouse moving in sympathy with the throttle.

Yeah - slots for trusted pilots with heavily armed aircraft to patrol the skies to take out the disruptive fools. Sounds good to me :) Making sure those slots are set to to spawn in the air, fully loaded for rapid response. Maybe in the future it will be possible to script something that makes use of AI aircraft patrolling the skies looking for offenders live firing in a non-combat free flight server?

I've found that if you're alone and don't have much skill (like me) the best time to get on the 104th is during it's more quieter periods. Then I'm more likely to find people nearer my own skill level. Or that's how it's been the past few times I've been on. That and a few sneaky unexpected tactics seldom used by others tends to keep me alive in a BVR fight longer than 2 minutes hehe. It's a nice server to fly on for sure but yes, I've seen it on brutal days when you have a number of skilled players working together on the opposing team. On those days you may as well shoot yourself with your own 120s and Aim 9s - you're gonna get owned :megalol: All good fun though :thumbup:

Yep, this is the reason I don't bother with the other free flight servers around at the moment. Too many people abusing the servers. No respect for others flying, taking off where ever it suits, crashing into people on purpose and no and nothing to stop it. Me thinks this sim / game could do with a ban list of some description. Good luck guys, we're all behind you. Hope you find a solution :thumbup:

+1

Hello, I've owned my X-52 Pro for around just over a year. Total number of hours use, maybe 50 or less. They've been looked after like one of my children. Cleaned regularly, unplugged when not in use etc. The X-52 Throttle / Rotaries: Personally speaking, the rotaries and slider are next to useless for anything that requires precision such as zoom. To date, I've not found a use for any of them except the slider which I use to control the RPM on the P-51 because it's slightly more reliable than the rotaries. In windows, in the joystick controller options where you can test all the buttons, sliders and axis, you can see the rotaries and slider wavering around all over the place both when centered and when moved to new positions. Maybe 1/4 of their actual range is usable. The mini stick I've also found to be flimsy and useless. In the configuration settings where you can test all the buttons axis etc it also wobbles about all over the place like the slider and rotaries. My mini stick also doesn't have a full range of motion in the test window. It refuses to move the cursor all the way up and it generally feels cr*ppy and cheap. I don't use that either. So I'm already down 2 roataries and a mini stick and in most cases a slider. Everything else however works fine. Buttons, throttle, switches etc. All function perfectly well. It's just the rotaries, slider and mini stick that suck. Oh and the MFD display on the throttle occasionally throws a fit, flickers, dims and the backlight goes off completely for seeming no reason at all. Moving on to the stick: I can't say that I'm impressed with the stick much either. All the buttons work fine and the overall feel of the stick is nice and big but it suffers from horrific friction and there's quite a bit of play when centered under its own tension. What it boils down to is this. When sat centered, there's quite a bit of play in the stick which you have to null out either in game or in the joystick settings. In my case this is worse because I've done the magnet mod which increases the sensitivity even around this deadzone. Then when you've nulled out the deadzone, it puts the starting range of motion right where the friction kicks in. This means when you want a slight precice movement when flying formation say, you first have to fight past the friction to do it. This results in jerky movements in game and is not nice. You can further null out this friction zone but then you're losing more and more range of motion in the stick and have to add more and more curve to compensate. It really is not nice at all. I've been down the lubricating and mod route and nothing cures this horrible friction and wobbly centering. I could forgive the cheap useless rotaries, slider and mini stick if the joystick was nice and smooth but it's frankly horrible to work with. I've not found a setting I've ever been truly happy with. It's definitely a step up from my old Logitch 3D in that I have more switches and buttons close to hand but the handling of aircraft is horrid with the stick. At first I was really impressed with it and I've tried to love it enough to see past its faults but I can't. The more I do, the better I get, the worse it seems. At this point I think an old Atari 2600 Joystick would be better :/ My personal oppinion is that I will be getting rid of mine as soon as I can afford a Warthog. I've never tried a warthog so I can't say what they're like so I'm making the leap based on other people's experience and ratings of it but I can tell you what the X-52 Pro is like and that I won't be getting another. Sorry it's not good news but it is honest.

At the minute, I've been using FRAPs but I think I might give this RAT a try over the weekend. Thanks for the info! :thumbup: LOL me too. Messing around with RATs in my younger days is what got me interested in learning more about IT, programming etc. Fun days. :smilewink:

Woo Hoo! I'll try and jump on later today for a couple of hours :D Thank you to all concerned with bringing us a 1.5 VA Server :)

Thank you Bucic :thumbup: I'll have an experiment this weekend when I have some free time.

Whoever it was that made the breakthrough, I'm glad they did and they have my thanks :thumbup: Like Call911, VA is pretty much my main hangout on DCS. I like it because it's nice, casual and friendly and you don't get fools ruining other people's enjoyment. Roll on the weekend and thanks again VA! :pilotfly:

Wow thank you. This thread is just what I needed! I'm wanting to record some highlights from training flights and this will help me immensely with the cameras and views. Could I ask if it's better to record with enhancements like HDR, lense effect, DOF etc off and then do all that sort of stuff post edit? Thanks!

Awesome news! Thank you Pman. Can't wait :)

I miss VA. It was like my second home at one point.

Ahhh, okay, I see. I wasn't aware of the wires. Yes, I totally understand re the cosmetics. I'd be exactly the same. Though if you do have to resort to doing as suggested, you could get some small counter sink grub screws that would (if done correctly) sit pretty flush with the walls of the tubing and if you're painting the arm then the heads of the screws could be filled with semi-permanent type filler, sanded flat and painted along with the rest of the arm to disguise them. But personally, I'd just get a new one made. I'm not a fan of bodging. Bodging something nearly always comes back to haunt you later on :megalol: A job worth doing is a job worth doing well. Nice looking build by the way. :thumbup:

WOW... That's some RAM hunger right there! I was thinking of dragging my server box back out the attic this weekend to have a play around with a DCS server but it doesn't have nearly that much RAM. Maybe I'll hold fire until this is resolved. I'll probably just get the box formatted and ready in the meantime. Does anyone know if you still need a GFX card in the server box running on lowest possible settings?

Thank you tob.s I've decided to buy a dedicated 7" display instead. The lag would really irritate the hell out of me. :)

Hi, if the tubes are hollow I would look to make an insert adapter of some sort. What you need is something that you can fix inside one of the tubes such that it's half in and half out. Then you can slide on the broken piece and attach them both together. Maybe a smaller size aluminum tube or some wood just the right size to fit inside the tubes. Then you could tap in a couple of small discrete holding screws either side of both broken peices to fix them firmly to the newly made insert which will hold the whole thing firmly as one. If I made myself clear?

Can I just say that for people with a memory as bad as mine, what I tend to do is assign anything that's critical i.e. needs to be within immediate reach to my HOTAS and everything else including Tracking commands gets bound to voice control. Personally, I find it easier to remember vocal commands than a tonne of buttons and modifier binds. It's made fumbling with all the controls so much easier by just saying "center view" or "screenshot" or "BVR Mode" etc when I want to do something that doesn't require my utmost attention and/or input. Aircraft like the F-15 are pretty simple in terms of buttons but for aircraft like the A-10 or the KA-50 where lots of buttons and mappings are needed, this comes in very handy!

Hi, I've purchased this tablet for me and the Mrs as a treat and then I wondered if it would be any good for displaying instruments such as the Shkval or ABRIS in the KA-50 or the VSD for the F-15C? http://www.ebay.co.uk/itm/191481434436 It's not the greates of tablets, I really only got it so we had something light but bigger than our phones to browse with. I've read bits n pieces about people using tablets to display DCS instruments here and there but I'm not 100% sure what's needed. Any advice would be extremely welcome. Thanks! :thumbup:

Issue when using the "ruler" tool in Combined Arms I've been playing a bit of Combined Arms since the latest update but have encountered a couple of problems when in a mission. The ruler tool (the tool that gives range and bearing on the map) seems to no longer show a physical line on the F10 map. Then when playing around with the ruler tool in the mission it seemed that it caused the mission to crash. I tried twice and both times playing with the ruler tool seemed to cause a crash. I've attached both crash logs. This was a couple of days ago but I've been having a move around of my hardware so this is the first chance I've had to properly post about it. DCS.openbeta-Crash-20151107-205307.zip