Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Everything is Ok when playing while i launched an init file ans a description.ext.
Making an add-on, i succeded (last hour) to add a cfgPatches in description.ext renamed config.cpp. I also created pbo, keys (bisign and bikey), put all this in @directory... and subfolders addons & key... Newest Arma3 tools Publisher is also Ok (no error)... I tried in friend scope at this stage... But, nothing when i try to dowload (after subscribing at my addon) No file dowloaded ?? and, if i hard copy the addon folder @... with other addons in arma, I can enable/disable addon via configure/expansions menu but whitout any result. (no error at least!)
So, my explanations in poor English, are rather bit long but i have 2 questions :
-what appens with uploaded? file(s) on workshop ? Why cannot i download what i created?
and
- copying a @folder with addons for pbo/bissign files, and key folder for bikey, doesn't seem to be sufficient for triggering my addon. So what could i do more?
Many thanks
Also, the @folder thing is supposed to have an "addons" subfolder inside them, with the PBO and BISSIGN files inside that. For example:
@CHO_F35B\addons\CHO_F35b.pbo
So. As i progress in testing pbo builders, i tried Mikero's pboproject. Pbo is done but with plenty of warning concerning all pictures in config.cpp BECAUSE PboProject works in P: drive and doesn't take into account c: pathes (for existing arma icons ans so on).
And, on the other hand, if i try via Arma3 tools PboBuider, i obtain an error "build failed code=1" without explaination.So, for finding this error, I have the choice between plague and cholera!
But Pbo seems to be created and even can be uploaded via Publisher!
PS : If i avoid to binarize, pbo build goes well. The problem is what could be this "error" if i can run my scripts in editor without any problem?
And , most of all,i can download my "addon" (1.3 Mb) now, with steam launcher. PBO File is in its addons folder, seems good like the other ones, but nothing appens in game (while editing and previewing a mission for instance).
to resume :
- in my mission preview editor, SQF files run automaticaly (conditions are met via init.sqf),
- in other mission, addon installed, nothing appens.
What is the file, command, trigger, line, which could make this "mod" goes round???
Now, addon builder returns error when adding my key (signature option). Binarization is OK!
So, probably no error in cpp and sqf but creating keys, always error result = 1??
DSSignFile seems to be working...
- first : i renamed description.ext in config.cpp (i didn't try to keep description.ext),
- i added two classes ; cfgpatches to say "it's an addon", and cfgfunctions to "launch" a first sqf.
- i binarized with addon builder to do a pbo. addon builder is pretty but doesn't explain what error it finds. So I debugged with pboProject, not easy to install but which says approximately what line is odd. And your project can run in editor but fail to binarize...
- main work was to change all pathes of images and icons, all pathes of called script. I didn't find any function to do the job, and scripts, images and so one must be clearly identify from main addon folder (@pouetpouet i.e.)
- if you can binarize, it's a great chance to success with pbo
- i used publisher to try an upload. It ounds great with a pbo embedded in addons folder and you can download via launcher to test
- i'm trying right now to sign, to add a notice and so on .
Hello. Are you sure you closed the object builder? When you "pbo" a folder, you need to close all apps except the addon builder (tools). If something else, you need to read the rpt file (inside the ...\steam\steamApps\common\Arma3 tools\logs).