homepage Forums Air Combat & Civil Aviation DCS World Eno's Firehouse and Crew's Hollo Pointe Server Lounge

1.2.7 is separate, I tend to fly either one depending on MP Presence on servers I frequent.

SSD will only help loading times, depending on settings and previous hardware.

i Actually limit my FPS to 30, and Set CPU Affinity in the Autoexec.lua to avoid tearing and process thread hopping.

I fly 1.2.7 as much as possible and post crash logs when I encounter them. I only go to 1.2.6 when the firehouse is down or when everybody is in hollo pointe.

Also....did I miss something warning/rule about not loading controls from 1.2.6 into 1.2.7? Because that's exactly what I did.

it was recommended not to copy stuff from 1.2.6 to 1.2.7 as some control setups have changed.

trying to find the best price on Thrustmaster MFDs, as I'm finally ready to just get them, lol, had them before long ago for Falcon4, then sold them off.. Now I want some for DCS.

Changed Back To School where the Blue Air Defense is in Beslan City. This was the group that spawned two more ADA Groups but I'd taken the spawn groups out a few days back. The original group was behind a bunch of big buildings so I moved them. I think what was happening was Red armor pounding the city in their attempt to take out the Blue ADA. All of the buildings on fire and smoking are what was causing the stutter -- now the Blue ADA is more in the open. That Blue ADA is in there for a Ground Commander to use against Red dogs attacking Beslan Airfield.

WC

Just a quick note- I'm on nights and just wanted to get a blurb in between naps.

Einstein what mobo are you running? If its first gen i7 then we may have been experiencing the same problem with the inadequate Marvell 9128 controller. Not to be confused with the newer and improved 9182 controller.

Verify that you have your graphics plugged into the faster pcie slot (x16 generally). Also if you're running an older mobo your card may now be "waiting" for data. I can't remember your system specs.

Snipor they have recommended guys not transfer things (key assignments) over directly but in the case of Blackshark2 and a10 there were few ( if any) key assignment changes so there would be less impact.

I'm driving an Asus P6X58D-E with an i5 950 sitting in an 1366 socket. Little bit of googling tells me I've got the Marvell 9128 controller, which I take it is no good? Will have to look into it more.

As for controls - my recommendation is take the time to redo them from scratch with the new setup. It's a chore and a pain, but you'll remove any doubt when you run into issues later.

You: "Gah, I'm having problems with multiplayer with 1.2.7 - I keep getting disconnected! Any ideas?"
Them: "Did you import your controls from 1.2.6 or start from scratch?"
You: "Uh, well, yeah, I copied my config files from 1.2.6 but I don't see..."
Them: "CAN'T HELP YOU SORRY!"

I5 750 or I7 950? If that's your mobo I'm assuming i7 since its the 1356 chipset.

I think if you stay out of RAID setups you'll be fine but if you start blue screening and can't figure out why that's probably it. Most recommend sticking to the intel controllers which may still only be the sata 2 speeds but are said to be just as fast and much more reliable. You're going to see that info a lot as I did also while doing research for many of the same reasons. Also why I ended up biting the bullet and going out and bringing my backbone gear into this decade. I had a pcie3 graphics card and a Sata 3 capable ssd plugged into a mobo that was 2 gens behind.

That's pre Sata3 standard and though it is technically the same advertised speed it doesn't deliver on those ports.

On another note That 950 overclocks really well (love that mobo too ) if you have the cooling for it but of course can be a challenge to find the sweetest spot. I assume your hyper threading is turned off- which further enhances that option.

If I were in your shoes I'd look for a solid CPU / mobo / ram bundle and just get it over with lol. Your power supply provided you didn't cheap out on it (not my impression) would be adequate provided its 600w or more.

If you have more than stock cooling and a decent case I would suggest doing some research on overclocking- but I seem to recall us talking about it before and you being against it overall.

WC, I just copied the input profile folder in my saved games to the one for the beta. Although i only have a custom config for the A10C which hasn't really changed, so I don't know if that would be an issue for other modules.

---

Sounds like the mission editor could really use an overhaul for MP mission design - although having a dedicated server with functions like SLMOD and automatic pausing and server restarts would be nice after 1.2.7.

---

I'd like to get to mission design aswell if I could just find the time for it....

Wesley I'm trying to get some feedback from Grimes over on the ED forums to see if I should put SLMOD back into operation and start submitting logs to him again. For MIST functionality as well.

I should know more soon enough.

Is anyone currently using their flight controller as a PTT device for TS3? I setup my Mic Switch UP function (in TS3 itself) to act as my PTT, however, I am now having an issue that any time I push the PTT I lose function of my HOTAS Stick. Releasing the button causes it to come back, as if on pause.

Doing so frequently causes "corruption" of the axis - if I was stick left, hit PTT, center stick, then release - on release the stick is still left in game. This makes my aircraft completely unflyable as I have no way to re-calibrate it.

I also tried mapping the Mic Switch UP to my PTT key using TARGET, but I didn't map ALL the functions only to find nothing worked. Apparently not mapping something in TARGET doesn't leave it as "default" as I thought.

Any suggestions?

That's a weird one Wesley- I haven't heard of that before.

I never installed any target software- I installed the drivers and that was it. The only mapping I've done is in the game. I'm sure this doesn't help as much as to say I haven't seen or heard of that issue before.

There is a Z axis as well (I think that's pushing in the mic switch) that some people use but like you I chose the mic up switch instead.

Sounds like you got a bad driver / software install so my natural tendency would be to wipe it and start over again. Leave your keys mapped as they are in game of course- but reinstall the HOTAS related stuff. I stayed away from the TARGET software on my second time around when I realized it wasn't necessary.

Never had that problem; I use the paddle switch on the Warthog stick.

Weasley,

I use Mic Up as my PTT for Teamspeak but I mapped it directly in TS3, not using TARGET. I have not experienced that issue.

I'm not that familiar with TARGET, but it sounds like maybe Mic Up got mapped as a mode or switch button, instead of just a keyboard input?

Well,
I dont use CH manager for DCS, DCS Has a pretty good Individual Mapping system.

I just mapp everything directly in DCS,

I have my Pinky Button on my CH Stick mapped to Team Speak PTT.

Wesley -- are you using both TARGET and DCS Options for Warthog settings? I don't use TARGET...


I use the Mic Switch Up for TS PTT -- assigned in TS. DCS should not have any assignment for that switch.

Check it out in the Windows controller panel -- and do a calibration on the stick and throttle while you are there.

WC

To clarify:

1) I started with the setting in TS3. When that was an issue, I went to TARGET - which didn't work so I forgot about it.

2) The stick's calibration is fine - it is only affected in DCS for the CURRENT aircraft. If I respawn, all if fine until I start using the PTT again.

3) The error only seems primarily affect the pitch axis. Looking in cockpit at the stick, if I push my PTT (Mic SW UP) and push my HOTAS forward, the stick in DCS doesn't move. If I push the HOTAS, ALL THE WAY forward, the in game HOTAS will start to creep forward VERY slowly. At this point, if I let go of my PTT, whatever position the in game HOTAS is at "becomes the new center". Pushing the PTT again could change it, and this occurring many times makes the plane unflyable.

4) Respawning solves the issues until I hit the PTT.

5) The HOTAS is fine for windows calibration etc, it's only affected in DCS itself.

At this point I am considering this a driver error and going to wipe it clean, possibly a new TS3 install aswell if necessary.

By any chance, is the pitch control mapped in DCS World for your throttle? ie: You should only have two axis mappings in DCS for the Warthog throttle (maybe three if you use the slider for zoom like I do). I know that DCS likes to assign additional axis that is 'sees' to various things. My warthog stick gets pitch, bank and a rotation for the rudder that it doesn't have and I think DCS is seeing one of the hat switches as a candidate for that and assigning it. I always strip out all of the extra axis mappings that DCS puts in.

Also, I am using the mic-switch-up on the throttle in Teamspeak fine but I think I had to unmap it from DCS (then again, I can't remember unmapping that for 1.2.7). I do have to run Teamspeak as administrator though and teamspeak reports the PTT switch as being button 3 or whatever.

I got it solved. The issues only presented itself in DCS 1.2.7 so I wiped and re-mapped my controls aswell as removed TARGET software package and rebooted just to be safe.


EDIT:
I have also had to turn of "Synchronize HOTAS controls at mission start" as this leads to odd behaviors as soon as the mission starts. Before remapping, hitting "fly" with an air start lead to an immediate master caution which would vanish after a half second.

With the remap, hitting "fly" leads to the in game HOTAS moving full forward and left. Touching any control (or moving my TRACK IR for that matter) would immediately get everything right. Still, starting off spiraling uncontrollably isn't my idea of fun.....

Glad to hear you've got it sorted, Weasley, but I'm dying to know how that happened. Very curious. If you ever figure it out, let us know!

In the meantime, hope to see you up in the virtual skies, soon!