Jump to content

Dwarden

BI Developer
  • Content count

    10511
  • Joined

  • Last visited

  • Medals

  • Medals

Community Reputation

929 Excellent

About Dwarden

  • Rank
    BI Developer

core_pfieldgroups_3

  • Occupation
    Major minion in empire of Bohemia Interactive

Contact Methods

  • Yahoo
    testhandle
  • Skype
    david_foltyn-dwarden
  • Biography
    Motto: Ideas are like ocean without borders!
  • Twitter
    FoltynD
  • Google+
    110932288521681156421
  • Youtube
    FoltynD
  • Vimeo
    foltynd
  • Xfire
    Dwarden
  • Steam url id
    Dwarden
  • Raptr
    Dwarden
  • MySpace
    TestName
  • Linkedin
    TestName
  • Tumblr
    dwarden
  • Flickr
    TestName
  • XBOX Live
    Dwarden0
  • PlayStation PSN
    Testname
  • Origin
    Dwarden
  • PlayFire
    Dwarden
  • SoundCloud
    Dwarden
  • Pinterest
    FoltynD
  • Reddit
    Dwarden
  • Twitch.Tv
    Dwarden
  • Ustream.Tv
    Dwarden

Profile Information

  • Gender
    Male
  • Location
    Brno, Czech Republic
  1. 1.82.144685 new PROFILING branch with PERFORMANCE binaries, v02, server and client, windows 32/64-bit, no linux 32-bit server atm. + crashfixes for issues with terrain loading in editor and several related to missiles https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm https://drive.google.com/folderview?id=0B03-H4YIbhkFMUt5RzNqZjFlNGs available via STEAMklient/STEAMcmd as branch too, read https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server BIForum feedback: https://forums.bistudio.com/topic/160288-arma-3-stable-server-182-performance-binary-feedback/?do=getLastComment Arma anything discord: https://discord.gg/arma
  2. they just latest libs as in both stable/profiling branch via steam ... only in case someone has wrong ones
  3. 1.82.144658 new PROFILING branch with PERFORMANCE binaries, v00, server and client, windows 32/64-bit, linux 32-bit server + sync with 1.82.main branch for profiling branch / performance binaries 1.82.144667 new PROFILING branch with PERFORMANCE binaries, v01, server and client, windows 32/64-bit, linux 32-bit server + hotfix server crash at zeus gamemode https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm https://drive.google.com/folderview?id=0B03-H4YIbhkFMUt5RzNqZjFlNGs available via STEAMklient/STEAMcmd as branch too, read https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server BIForum feedback: https://forums.bistudio.com/topic/160288-arma-3-stable-server-182-performance-binary-feedback/?do=getLastComment Arma anything discord: https://discord.gg/arma
  4. 1.64.144629 (cumulative ontop 144373) + additional crashfixes + other minor fixes ~ linux dedicated server fix WIP, TBA
  5. in that case same problem different origin :) both mods touch config entries which Corepatch fixes hence collision will occur Origins need to update (directly) or simple patch for Origins needs to be made
  6. @without_nic Epoch related issues, see the Epoch discord and get new version of the mod with fix @daleyg issue forwarded to corepatch team
  7. fixed BE both in stable and beta
  8. that works only for 1.63 stable not 1.64 beta !
  9. manual fix : copy content of \Arma 2 Operation Arrowhead\Expansion\BattlEye\ into \Arma 2 Operation Arrowhead\BattlEye\ ... can't be fixed tonight due to logistics issues so next workday
  10. A2OA stable just got data update \common\modules.pbo \expansion\addons\corepatch.pbo so the only difference between 1.63 and 1.64 are ACR lite data and new binaries/libraries
  11. well 1.64.x is mandatory cause that's what you get and will be final ... hence why i would prefer to see results on that to compare with 1.63 to avoid regressions note: generic description of load map, fire flare, see the bug is reason things fail to get fixed cause that's sort of useless report what exact time, what weapon, what flare ... e.g. repro mission solves that problem same for video or screenshots w/o it i or QA most likely fails to figure what you talk about also take in mind flares usually aren't the illuminating flares but signaling flares (different purpose, intensity and lit time is way shorter)
  12. @JOHN007 can you post video of the z-fighting flare bug with default 1.64 binary + data vs with your fix ? to see / understand the difference
  13. note: "-beta=FDFmod" is better to use than -mod= usually if that fails it means you need reinstall because something is wrong (e.g. registry paths missing)
  14. but all those are very complicated cases (e.g. vs ACR detection) ... the simple solution is something i could not utilize in early STEAM times (due to various versions of windows/rights issues) and that's use simple junction e.g. open dos command propmpt in A2OA folder so within your STEAM path \ STEAMapps \ common \ ARMA 2 Operation Arrowhead \ then just in command prompt mklink /J "Addons" "..\Arma 2\Addons" Junction created for Addons <<===>> ..\Arma 2\Addons then you do not need worry about mod path for A2 data anymore as this will create within A2OA folder \Addons\ junction folder linked to A2 folder \Addons\
  15. anyway i'm looking at this and you simply need use full paths to A2 / OA content when using -beta= , -mod= switches see e.g. files _runA2CO.cmd in the root of A2OA folder if correct data paths are used then you can use the other "-mod=" and "-beta" switches
×