rob10

You're probably better off submitting a support request direct to WW on this. I don't believe they watch this forum at all and some changes have occurred after people submitted support requests. They might occasionally respond, but almost all posts here are users, not WW.

See this thread:

This! Every time these discussions come up I think of all the people saying MT was dead and never going to happen and ED had talked about it for so long with nothing to show that it was never coming. Then, out of the blue it appeared and the masses rejoiced. Not the 1st development that went that way. It's just the nature of the beast with ED (for IMO plausible reasons), so have some patience.

Thanks, good to know.

Great that it's working better for you now. I haven't ever had disconnect issues so I can't say I've seen any change.

SimAppPro allows you to keep the lights on your throttle (i.e. A-G mode or A-A mode) or other parts of your hardware synchronized with the in-game setting. It's also required for any of the vibration effects on some of the joysticks.

Yep. You can also use SET FLAG VALUE to set a flag to a specific value. One other thing to remember is that flags are CASE SENSITIVE, so "Flag 1" is different to "flag 1". Also with FLAG ON/OFF – on and off DO NOT use integer 1/0 when evaluated (i.e. if you set flag ON, it won't evaluate to 1 in "if flag=1“)

It's basically treating your numbers as letters. So it sees "13" and sorts it before "2" because it's looking at it as "1","3" rather than "13" and "1" comes before "2" so "2" comes after it because it doesn't look at the "3" until 2nd round of sorting. Easiest way to get around this is use letters, so substitute "A" for "1", "B" for "2" and on up.

As usual, the answer is "it depends" . Depends very much how much (and what) you want to do. I have dipped into direct LUA a bit and some of the mod versions like MOOSE and MIST a bit, and it's amazing how much you can do with just a little bit of knowledge (helps if you have some programming knowledge to allow you to grasp concepts and different ways to do it). Examples and looking at other missions are a great way to learn since LUA can definitely be intimidating to get started into. Good post above!

They are basically just pre-populated bindings for various aircraft (virtually the same as binding them yourself in game). No ability to assign multiple keystrokes with one command. If you're just meaning a modifier (i.e. doing CTRL A rather than sending A, B and C with one button press) that can be done. I've never used that part of the SimAppPro because I've never seen the advantage, so maybe I'm missing something, but that's my understanding of it.

If you're seeing the same physical DDI blinking off in multiple ports/multiple cables is a bad sign. Likely the hardware. Only other thing you could try is physically switch ports AND change which screen you're exporting to that DDI in the SimAppPro software. This is my laptop so it's checked as ON and you want OFF for each USB port. It's in DEVICE MANAGER in Windows.

WW software doesn't have the same level of functional complexity as the TM software, so I'm pretty sure you can't directly do what you're looking for with SimAppPro. It's easy enough with AutoHotKey (very lightweight external program) or other joystick software, but not within SimAppPro that I'm aware of.

Double check that you have the SLEEP function for your USB ports turned off (or that Windows hasn't turned them back on if you have turned them off before). Are you running it direct to computer USB or through a hub? Could be a power issue if it's direct or you're not using a powered hub. Sounds like somewhere it's disconnecting the RDDI. Also check that all the cables into the back of the DDI are fully inserted. It's possible you have a dud DDI too. Try swapping the port you're plugging that one into with one of the other ones and see if it still happens with the problem DDI or starts happening with the new one plugged into that port. That should help determine if it's the port or the WW hardware that's at fault.

In fairness, while this might have been a problem in 2015, I'd pretty sure it was fixed and only became a problem again recently.

Keep an eye on the changelogs and the Hornet MINI-UPDATES thread in the Hornet sub-forum (although the fusing video was only in the F-16 Miniupdate section so easy to miss).

Physical RAM is always going to be better than a pagefile, so if possible I'd be getting more physical RAM AND bumping your pagefile size.

Copied from above: Won't pass IC check, but you can change it here: \DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua dedicated_viewport = {3910,2437,600,700} -- << AT LINE 33 It is set as "default", you'll need to figure out what co-ordinates you need to use

I've seen that as a completely random thing that happens in MP every once in a while. Not a common occurrence at all, but I've seen it more than once.

And how many posts have you seen of people missing the DCS.exe from their DCS-MT folder after the update? Can't say I've seen more than yours, which would suggest a problem on your end rather than a widespread ED/DCS problem. Following Rudel_chw's advice in the post above would be a good starting point.

None of the fuzing info has been updated in the manual to reflect the recent changes, so don't bother looking there. Due to limitations with the MC it's not possible to have 2 different fuses on the SAME weapon. So you could have different ones on GBU-12 vs GBU-38 but not 2 different fuses on GBU-12's or 2 different fuses on GBU-38's on the same plane at the same time.

You might as well. Today's newsletter announced that ST will be fully deprecated with the next patch.

You just need to click on the little triangle in the upper left corner of the weapon pylon with the LGB on it and it will give you options to change the laser codes and fuzes on the bomb. In the mission editor of course.

According to your logfile your pagefile is set to: 256 MB which is why Silverdevil mentioned it. Your DxDiag seems to show you have 32 mb pagefile set though . But definitely showing out of memory errors in a few spots in the logs so I'd question whether you have a hardware memory issue.

The problem is none of us have any idea of the facts of any of this. If you just look at questions you pose in this post, yes it seems unfair. BUT we have no idea how Razbam was supposed to be paid. They might have agreed to what seems to you an me to be an unfair contract that meant they had to wait for 6 months after the module released to be paid or they didn't get paid until they hit certain milestones or who knows what in order to get a contract. So it may be completely legit that they didn't get paid before this conflict blew up. Or maybe Razbam is getting screwed by ED. There really isn't enough information in either the official releases or leaks to know the true answer to all of this.

I completely understand where you're coming from, but not sure how you do that with a keypress or button press. It's either ON or OFF. In theory you could have it ramp up from zero to full, but then if you stop pressing does it immediately go back to zero or ramp down? And where does it start if you press again quickly -- on full or start over at zero and ramp up? Not really sure how you do brakes well without an axis.