Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Community Reputation

0 Neutral


About i0n0s

  • Rank
    Gunnery Sergeant
  1. 1. timeout "0,15,30" 2. timeout "0,20,40" 1. will go off between 0 and 30 seconds with average of 15, 2. will go off between 0 and 40 seconds with average of 20. So there is a chance that 2. will go off before 1.
  2. Try it again with RTE Capture 1.60. It fixes the bug you encountered. About "inactive": Use JayArmA2Lib and check if the status changed when RTE is open. If it doesn't change then probably JayArmA2Lib is not installed correctly.
  3. @metalcraze: Please send me: %APPDATA%\RTE Capture\Options.ini %APPDATA%\RTE Capture\Profile.xml Just pushed revision 559, a jump of 30 commits. And only one line in the change log about the major change... New background for pause dialogue Drawing on 2D map now uses the new draw commands instead of local marker. Creating trigger works again. Waypoints stays connected after rewinding. Anyone uses the *gasp* 2D map? I guess no one, but I'm finally using the new commands to draw on the map and don't need to use local marker any more. I can drop more and more workarounds and it still works :)
  4. Any progress on the duplicate code detection? And is it possible to add a warning if a switch doesn't have a default state? Just in case if an unexpected value passes true.
  5. About the waypoint error: I fixed it in my last revision and the waypoints are saved correctly. It's only a failure when rebuilding the waypoints. The 'my document' folder may be the documents folder. It contains the ArmA 2 and ArmA 2 Other Profiles folder. @Jessie Yao: The installer makes the error or which program is creating the error. How to use the RTE for Dummies: @Duggedank: This would require a redesign of the dialogue which requires a lot more time then I can spend on it. Oh, and which team? It's currently a one men project. So if someone is interested to join, feel free to ask. Only a little script knowledge and/or knowledge about dialogue design is required. The RTE itself is complex, but the parts are simple and easily to understand.
  6. @victim913: I'll take a closer look to the waypoints. @built4speed: Obvious a null pointer. The question is when did it happen and what did you do. And is it reproducable. Otherwise I can't tell you nothing. About issues with exporting: As Patriot 911 stated: It's mostly due to an incorrect installation of JayArmA2Lib. Please request in its thread that it adds a sign to the A2 version number if installed and active so that people can easily check if it is working. But please continue using JayArmA2Lib. The way with "Use RTE Capture DLL" works too, but JayArmA2Lib is better. One general note: Once JayArmA2Lib is working correctly, RTE will take a little longer to open and will connect to RTE Capture directly. So you just need to launch RTE Capture, ignore it and keep it in the background, start A2 your favorite way, open the RTE, and it should work fine. @CannonousCrash: Can you check the data saved in RTE Capture if the objects are there once. It may be that you exported it multiple times. RTE Capture doesn't check for duplicated objects, so when you export the same unit twice, it will save both units.
  7. CO or OA works, but some features of OA aren't supported. The waypoint issue is new to me. I've created a bug tracker entry about it: http://rte.jonasscholz.de/bugs/view.php?id=279
  8. Have you run RTE Capture after the installation? If not, please do it. A wizard will install and create the @RTE folder. And it's not the folder where editor made missions go since this is placed in "ArmA 2 Other Profiles", but it is the "ArmA 2" folder beneath.
  9. Released RTE Capture 1.59: Updater for ION_RTE.pbo and ION_RTE_Dta.pbo works again. When merging into SQM, only one setPos will get added to the units init line. Added support for my documents\ArmA 2 as mod folder. Please use it as new default folder for the @RTE folder to prevent problems with UAC. Please read this blog entry and follow the change! Please note that the auto updater will update RTE Capture, it only failed to update ION_RTE.pbo and ION_RTE_Dta.pbo. Oh, and be aware of bugs! Existing 2d mission can be added into RTE, but only units and vehicles, no buildings. To save work within the RTE, use the "project administration". Export as template works for me. Does it also warns when opening the RTE?
  10. *censored* :mad: I remember a bug I fixed... This bug caused the updater to not recognise if a new version is out. Thought that it won't be a problem since the next version of RTE will come with a new version of RTE Capture with fix. But when installing, the installation of RTE is an update too... I'll push the RTE Capture update as soon as possible. When installing RTE the first time, please use the offline installer or the 7zip archive until a newer version as 1.55 is released! http://rte.jonasscholz.de/blog/2009/06/19/download
  11. Run RTE Capture again, this time as admin (to bypass UAC). Run an update. Now the @RTEditor folder will exists and it should work as planed. Or try the offline installer or the 7z archive: http://rte.jonasscholz.de/blog/2009/06/19/download
  12. @victim913: Tried to export when using ACE, used an infantry with added ACE medical stuff. Copied him, then exported them all and it worked. So I can't reproduce it :(
  13. Ok, what I'm currently doing: The next version of RTE Capture will support to have the modfolder in my documents\ArmA 2\@RTEditor. This will have a main advantage: You can simple update within RTE Capture again and don't need it to run as admin. The problem is caused by UAC, and moving the addon folder will bypass it. @CannonousCrash: You need to adjust the ingame gui size in the A2 options. @Zalsak: There is a bug in the current RTE Capture DLL or better within the RTE. In my current _debug_configuration_ it will work again. But better switch over to JayArmA2Lib. @ray243: This is a steam bug: It doesn't allow that much parameter if I remember correctly. Try it again with less mods. Try the minimal setup: @CBA, @JayArmA2Lib, @RTE. And one thing: You only need to load CBA one time, it seems to be loading twice. And another: Within settings: The ArmA II installation folder seems to be wrong. It should be: C:\Program Files\Steam\steamapps\common\arma 2 operation arrowhead\ And you will need to run RTE Capture as administrator once to download RTE due to UAC. Will be fixed with next update of RTE Capture. @victim913: The menu is due a bug within A2 which is present since 1.0. When having a large dialogue some commands will disappear. So the commands for moving the menu to the right place are gone. This happens randomly. A work around was not to use uiNamespace, but with the last patchs this is gone too... About the backpacks: The new backpacks with OA aren't supported yet. They are something I won't to support. About ACE backpacks: There is an implementation for the old ArmA ACE and those backpacks. So I don't know if it will work with ACE 2. But ACE has a low priority for me. About the saved loadouts: They go into the databank like the saves within RTE. About your export problem: I need to look at it. Haven't exported for a while. Have you tried to reopen RTE Capture and the RTE and export again? And if I read correctly: It's an ACE problem? So it only occurs with ACE units? I'll take a look. And it is propably a RTE issue instead of a JayArmA2Lib issue.
  14. They should be equivalent in speed, at least if implemented correctly ...