Jump to content
x39

ArmA.Studio - The Open-Source Community made IDE for ArmA

Recommended Posts

ArmA.Studio 0.2.6331.26237 got released
you will be prompted when you start ArmA.Studio if you are not up to date (unless you disabled Auto-Updating)
Open panels will appear empty due to internal changes, just reopen those
Changes:

- Rewrote whole lot of the backend
--> Solution now supports separate projects from different pathes
--> Fixed a whole lot minor and major issues
- Added German Localization
- Added Plugin System
- Added Workspace History (displays the last X workspace pathes and makes them selectible)
- Added simple image viewer (no PAA currently)
- Added properties page for Solution-Project
- Added Search (& Replace)
- Added Temporary documents (will be received by the debugger so that debugging unknown code is possible)
- Breakpoints now are in a separate file with separate extension
- Images wont upscale anymore


Special Thanks goes out to @vabene1111#5492 and `trdwll` for this update
link: https://x39.io/projects?project=ArmA.Studio

  • Like 2

Share this post


Link to post
Share on other sites

just wanted to quickly point out that there is no need to get angry or call the software "shit" for bugs in an alpha phase ...

things like this:

<?xml version="1.0" encoding="utf-8"?>
<root>
  <version>0.2.6331.26237</version>
  <report><![CDATA[I tried saving a fucking file. fix your shit software]]></report>
  <stacktrace><![CDATA[...]]></stacktrace>
  <trace />
</root>

are frankly not helping nailing any problem

 

this specific case for example, i cannot fix just by seeing the actual stacktrace as the exception raised already should be catched in code.

An actual description what has happened and what was done, would allow me to "fix my shit software" as somehow an edge case was found i did not yet covered

 

just quick note

 

PS

that particular bug is fixed now

the root cause was that newly added projects would not have the dictionary of the solution "assigned" but instead the full path to the solution file

 

meaning that .../foo/solution.asln/newproject would be the path that obviously could not be created

was some change wrongly applied

there is no QA on this project ... so theese things can happen

will be in next minor release

 

fix can be received via auto-update or via https://x39.io/Files/ArmAStudio/ArmA.Studio.0.2.6333.12157.setup.exe

  • Like 1

Share this post


Link to post
Share on other sites

I'm a little confused as to what exactly this is. Can someone clarify please?

 

Thanks!

MrCrazyDude115

Share this post


Link to post
Share on other sites
19 hours ago, MrCrazyDude115 said:

I'm a little confused as to what exactly this is. Can someone clarify please?

 

Thanks!

MrCrazyDude115

see https://en.wikipedia.org/wiki/Integrated_development_environment

 

in most basic terms: a text editor that is capable of stopping the arma script execution at some point where you want under certain conditions

  • Like 2

Share this post


Link to post
Share on other sites

Some Update:

Development is silently continuing in background

recently, AppVeyor got introduced so that the latest in-dev build is always available for everybody

 

in that

- a language option was introduced to change the display language

- a help button was added to the Workspace Selector for new users

- the breakpoints now support setting a condition additionally

- Variables View was enhanced so that it now is more intuitive (SQF Expressions are in theory already possible but due to debugger limitations right now not available)

- loads of bugs got fixed

- a lot of things changed that i already forgot

 

sooooo ... ye ... we still are here, discord is way more active

and that already was the update :)

 

https://discord.gg/RRaPyb9

https://ci.appveyor.com/project/X39/arma-studio/build/artifacts

https://github.com/ArmA-Studio/ArmA.Studio/wiki/Install-and-use-ArmA.Studio

  • Like 1

Share this post


Link to post
Share on other sites

lets just push this release as official https://x39.io/Files/ArmAStudio/ArmA.Studio.0.2.6402.7223.setup.exe

 

no changelog as i simply forgot what was implemented ...

pretty loads of fixes and tiny Quality of life improvments

 

also some other new features got introduced (onee that would come in my mind would be breakpoints)

 

will keep those changes tracked from now ... promise :dozingoff:

  • Like 1

Share this post


Link to post
Share on other sites

right now preprocessor is not supported due to lack of support in regards of ANTLR

there is a branch to "hack" in that behaviour however (another simple solution would be to simply run the preprocessor before doing the linting ... but that would destroy the offsets)

Share this post


Link to post
Share on other sites

Time frame on when this may be compatibile with BattleEye?

Share this post


Link to post
Share on other sites
7 hours ago, Heisen_a said:

Time frame on when this may be compatibile with BattleEye?

Never as you can manipulate the game with this 

 

It was temporary auto enabled btw

Share this post


Link to post
Share on other sites
4 hours ago, x39 said:

Never as you can manipulate the game with this 

 

It was temporary auto enabled btw

So if I just download arma.studio and not the debugger, ill be fine with no risk.

Share this post


Link to post
Share on other sites
44 minutes ago, Heisen_a said:

So if I just download arma.studio and not the debugger, ill be fine with no risk.

you will be fine at any time as long as you do not try to attach (or more specific modify) anything whilst the game is running on BE

 

you can leave the debugger in there without any problem

just do not attach to the game whilst it is running

Share this post


Link to post
Share on other sites

Hey, I have issue loading the BIDebugEngine.dll ... I put it into game root and launch game, but nothing happened. The pipe used for communication is not active and when I launched non profiling version, no message appeared, so good guess would be the dll is ignored.

 

I've tried both x64 and x86 versions.

 

Is the extension broken, or is it on my side? Could somebody try it on version 1.76.142872?

Share this post


Link to post
Share on other sites

BI Broke it

should still be working with Performance build

@dedmen is responsible for that part so he probably can tell you more about this :)

Share this post


Link to post
Share on other sites
19 hours ago, SkaceKachna said:

Hey, I have issue loading the BIDebugEngine.dll ... I put it into game root and launch game, but nothing happened. The pipe used for communication is not active and when I launched non profiling version, no message appeared, so good guess would be the dll is ignored.

 

I've tried both x64 and x86 versions.

 

Is the extension broken, or is it on my side? Could somebody try it on version 1.76.142872?

Broken. You can still get 1.74 Profiling build and use it for now. BI killed the Debugger. I can get it back up but that needs time that I don't have right now.

Share this post


Link to post
Share on other sites

btw. https://discordapp.com/channels/294154999766843394/294532226039808000/528370839775608854 (requires being on the discord server already https://discord.gg/RRaPyb9) contains instructions about how to get the debugger running again (no mayor update on ArmA.Studio yet because ... uff ... work)

 

note that you might need to read a lil bit further for fixes (new debugger is kinda stable and kinda unstable, which is also a reason why there is no mayor release yet)

  • Thanks 1

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×