Jump to content
Bohemia Interactive Forums

[kh]jman

Member
 View Profile  See their activity

  • Content Count

    886

  • Joined

  • Last visited

  • Medals

  • Medals

Posts posted by [kh]jman

  4. Posted · Edited by [KH]Jman

    @hellstorm77

    Rem out line: 126 in =BTC=_revive_init.sqf

    // hint "REVIVE STARTED";

    @Giallustio

    The ammo save code in BTC_get_gear (=BTC=_functions.sqf) is more of an issue. I've been looking at the code and I see 2 main issues.

    1. The find function call: _id = _array_class find _display_name; does not work since find will try to look for an exact match from the whole string and you're looking for, for example, "6.5mm 30Rnd STANAG Mag" in string "6.5mm 30Rnd STANAG Mag(30/30)[id:2625]" will return -1.

    I have kind of fixed it by creating two new functions called from _id = [_display_name, _magd] call fnc_searchArray; You will find the two functions at the bottom of the .sqf, fnc_find and fnc_searchArray

    It's now returning id's but you will notice that where there are several of the same item it's returning the first magazine instance it finds and not the one in the sequence that's required, I guess this can be fixed with a 'found' count parsed through the search functions so it will return the correct magazine index in the array.

    2. The _array_bullet array currently returns empty strings whereas it should return the bullet counts for the magazines. I have not fixed that one (it's late and I'm knackered) so perhaps you could have a look at it, it looks to me like your search pattern logic is messed up (shame we don't have regular expressions). I've forced the _count to zero at the moment to stop the script error on _count = _array_bullet select _id;

    Here is the new version of =BTC=_functions.sqf (modded from version 0.8): http://pastebin.com/00yFL7wu

    Here is an example of the new debug output for the function I've modded: http://pastebin.com/B1Zz5ja2

  10. Posted · Edited by [KH]Jman

    I agree with other people that it is not that clear that we get acces to beta and full game when we buy the alpha pack, may be it's on purpose i don't know :)

    Looks pretty clear to me.

    ref: http://www.arma3.com/buy

    alpha, digital deluxe edition and supporter edition all give you access to arma 3 beta (March 5th) & full game (full game when released)

    I still don't completely understand what will "free" players be able to play. Will they be able to play missions I create (with the paid version)? Will they be be completely unable to play any missions which require mods?

    Nonetheless, this is great! I sure wasn't expecting Alpha to be here so quickly after the recent lack of updates.

    alpha lite is invite only (from an alpha, digital deluxe edition and supporter edition purchaser).

    Lite versions cannot play multiplayer or created single player missions with mods.

  13. Posted · Edited by [KH]Jman

    @keyboardnutz

    There are many issues and bugs in the current PDB standalone version. Development of the standalone PDB scripts has ceased and I have moved development be to exclusively for MSO where PDB development has really moved on massively in MSO 4.6. Myself and the MSO dev team will also be working on a new MSO PDB version for Arma3 when it's released which will be in addon form.

    I am no longer offering support for this old standalone version of PDB.

    mso.jpg

    You can get support for the new PDB integrated into MSO on our dev-heaven site here

    MSO support is here and here

    The latest development files can be found here

    Might I suggest that an site admin locks this thread since it's now legacy.

  17. Posted · Edited by [KH]Jman

    Is there a known fix or workaround available now? What's the timeframe for a release of the next version?

    You can always grab our latest development branch from Dev-heaven https://dev-heaven.net/projects/mso/repository/show?rev=develop, these files are the basis for the next release and contain the fix. You will need to drop your existing database and use the new MSODatabase.sql schema. This is pre-release code use at your own risk. We cannot actively support the development branch here but if you have questions about it, please ask to join our Skype channel.

  19. Posted · Edited by [KH]Jman

    For your information, I am seeing the following errors in the server's rpt after allowing clients to use JSRS 1.5

    2013/01/08, 18:06:50 Cannot load sound 'jsrs_smoke\reload.wss'

    2013/01/08, 18:06:50 Cannot load sound 'jsrs_l85a2\reload.wss'

    2013/01/08, 18:07:38 Cannot load sound 'jsrs_m4sd\reload.wss'

    2013/01/08, 18:09:13 Cannot load sound 'jsrs_ak107\ak107_reload.wss'

    2013/01/08, 18:19:10 Cannot load sound 'jsrs_metis\reload.wss'

    2013/01/08, 19:03:27 Cannot load sound 'jsrs_l115a3\reload.wss'

    2013/01/08, 19:08:37 Cannot load sound 'jsrs_grenade\reload.wss'

    DH ticket: https://dev-heaven.net/issues/70217

    I am also seeing the following error looped over and over for long periods on the serverside rpt although I have not yet ascertained whether this one is being caused by JSRS enabled clients however it's not occurred until JSRS1.5 clients have been connecting.

    2013/01/08, 18:06:22 Unknown array value type -1

    2013/01/08, 18:06:22 EOF in string

×