Jump to content

antagonist

Members
  • Posts

    269
  • Joined

  • Last visited

Posts posted by antagonist

  1. Hi all

     

    If you are one of the users who is seeing issues with DCS 2 Open alpha (DCS 2.0.5.2576 Update 1) since the patch we are collecting data.

     

    If you are seeing strange controller behaviour, gauges not working, switches not working, retracted gear and so on please post the following info.

     

    1. Your Dxdiag report

     

    * click on "START"

    * click "run"

    * type in "dxdiag" and click "OK"

    * check through the tabs and perform all tests

    * click "Save all Information..." and save the text file to a location of your choice

    * attach this text file to new message

     

    2. What antivirus / security are you using?

     

    3. auto update log

     

    files from root DCS World folder:

    ..\Eagle Dynamics\DCS World OpenAlpha\autoupdate_log.txt

     

    4. dcs.log

     

    C:\Users\<UserName>\Saved Games\DCS.Openalpha\Logs folder

     

    zip the whole log folder and attach it, guide in my signature.

     

    5. List any unofficial modifications / tweaks you are using

     

     

    Thanks

     

    1. attached

     

    2. Avast

     

    3. attached

     

    4. attached

     

    5. none

    DxDiag.txt

    autoupdate_log.txt

    Logs.rar

  2. This is really interesting and now I am glad I brought it up , ok but what are TERs? and also on my HOTAS Throttle the Flaps have three settings.. UP , MANOEUVRE and DOWN , I use DWN setting to land yes? I use UP for take off and MVR for cruising , is this right fellas? Sorry to be a pain but it might be the reason why sometimes I drag in flight.

     

    You do not use flaps for cruising, ever.

  3. of course, the merge will make development and bug catching much easier to manage, and we all want that.

     

    By the way, what is taking ED so long to do it?

     

    Is the 2.0 client still being considered too immature internally, has the Caucasus map not been redone yet or is it something else entirely?

  4. investigations are still ongoing, it is not a simple matter it seems.

     

    When ED have more info they will pass it on.

     

    Roger that.

     

    Yeah, I gathered it would be a really obscure coding issue by how it is affecting some people to a crippling degree while others are sitting there, playing on the patch 1 build with zero problems.

  5. I was prepared to be up in arms over the AI assets costing extra after seeing some posts here, but considering Normandy+assets is the same price as NTTR, I'm not sure what the fuss is about.

     

    The water looks amazing.

     

    Yeah, my feelings exactly.

     

    Got notified by friends how the map and its assets were going to be split up, went 'dafuq', went ahead and read up on stuff to either warrant or void voicing my aggravation, then went on to find the price for both was not any more reasonable or unreasonable (YMMV) than the one for NTTR.

     

    Now I'm sitting here asking what the goddamned problem was in the first place. *shrug*

  6. I doubt they have the same engine, but I'm not sure.

     

    I just saw the max ceiling for the AJS in the manual, and figured I'd go chase it!

     

    According to LNS's own product information, it uses the RM8A, whereas the fighter version uses the RM8B which is slightly longer due to an additional compressor stage.

  7. I went through all of my airplane modules this morning to see exactly which ones were affected by the last update. I hope this will help ED as I see so many posts listing one or two specific issues with a particular module.

     

    A-10C - Completely shuts down DCS upon engine start

     

    F5E - cannot access the module at all. Just shuts down DCS

     

    Spitfire- Key mapping is messed up. Plane won't start up at all.

     

    FW 190- Landing gear extracts upon start up and plane just drops to the deck.

     

    Mig 15- no more Ctrl+0 views. Some problems with cockpit function but plane will start and fly.

     

    All the rest seem to be Ok. In fact, I think that the Hawk is better than it's ever been. Great update for VEAO.

     

    I do not have the time to try the helis, but I will do it later. I have not heard or read any complaints about them as of the last update.

     

    I know that not all of you are having these issues. It is well known that everyone who is having issues seems to be having them with random modules, and some of you aren't having any issues. I am just listing what is and isn't working in my particular case.

     

     

    Fw 190 D: The plane spawns in with the landing gear retract button pushed down. Before powering the electrical system, it is possible to push the deploy gear button and prevent the plane from crashing to the ground by retracting its gear.

     

    However, after pushing in all the breakers, enabling fuel and magnetos, the flywheel is unable to completely turn over the engine. The prop will start turning and catching, but it never moves on from there, i.e. the engine never receives any kind of boost.

  8. since I did today's update, many gauges in the Bf-109 don't work. If I do a simple free flight mission with start from runway, the fuel gauge shows zero, the temp gauges show zero, the landing gear lights don't work, and many more issues. Since today's update I have similar issues with many planes, this is the last bug report I'm gonna do today. For now, I'll just give up on 2.0:cry:

     

    For me, the issues with the 109's gauges are fixable as I could trace them back to the ignition breaker not being pushed in despite airspawning.

     

    Guns also won't work until you push in the IFF breaker.

  9. Hi guys, I'm just as sad about the problem as you guys are, unfortunately many have found it's out of our control right now so waiting on ED for a fix.

     

    The instant the patch came out, tested to see if the patched version was working okay and found the exact same scenario seen here. Full throttle, got not afterburner, at a certain airspeed the FBW commands a full up elevon response.

     

    I'm also having issues with pretty much any other EFM based module it seems. I went so far as to do a full clean re-install of alpha last night and still coming back after work today the same issue occurs but does not happen in the development build, which points to other suggestions that the DRM protection is the root cause but I can't say for sure.

     

    It almost looks like memory address pointers to functions and/or data got all corrupted and screwy so it's getting odd responses and different behavior for each module.

     

    Apologies this is happening guys but hopefully they find a fix soon!

     

    One of the LNS devs actually tested with an unprotected version of the game and found out it was not subject to the issues you're describing.

     

    So yeah, almost certainly the fault of the copy protection.

  10. Wait until 130-150kts to set T/O trim (<--any aft stick sets it).

     

    Seems like the trim is meant for AB takeoffs, as well.

     

    Edit: By the way...I haven't flown the latest 2.0...Is that the problem here? I probably should've read the thread! :p

     

    StarForce being itself has screwed up the latest patch for 2.0.

  11. Сударь (с).

    Вам последнее предупреждение. Не умеете себя вести или временное помутнение, не заходите на форум, пожалуйста.

     

    Sorry gents, we'll handle this case.

     

     

    Don't mind me, I'm thoroughly entertained watching this bickering for no reason on his part.

  12. Yeah, quite a lot of the AI only planes are really showing their age, to put it mildly. Good to hear you're going to have your model made available for the core game's AI vehicles!

×
×
  • Create New...