-
Good news everyone!
OXCE and OXCE+ have merged together!
Starting with version 5.0, there will be only one "extended version"... and we decided to stick with the name "OpenXcom Extended" or "OXCE" for short.
I will be slowly renaming anything important from OXCE+ to just OXCE... please have some patience, it will take a bit of time.
I have also locked the original OXCE and OXCE+ discussion threads, please continue the discussion in this common thread.
As for technical info:
- the main common GitHub repository is: https://github.com/MeridianOXC/OpenXcom/
- Yankes' repo is effectively frozen
- both myself and Yankes have full and equal commit rights to the common repository
The new and shiny OXCE 5.0 can be officially downloaded from here: https://openxcom.org/forum/index.php/topic,5258.0.html
Cheers,
Meridian
-
reserved
-
Nice one!
-
The king is dead, long live the king! :)
-
Hello again everyone,
I have deleted several posts above, because they would confuse other people reading this thread.
To make it absolutely clear:
- OXCE now contains all features from OXCE+ ... nothing is lost
- we have increased major version of OXCE to v5.0 to remove any possible remaining confusion
I have also built a new version for all common platforms: Windows, Android, MacOS and Ubuntu.
You can find them on the usual place: https://openxcom.org/forum/index.php/topic,5258.0.html
Enjoy!
-
Thanks so much. With a quick inspection - all the same as in OXCE+. And the actual "Readme"will?
-
New OXCE v5.1 is up.
2018-10-03
- Translation updates
- Unhardcoded recovery dividers for special items: https://openxcom.org/forum/index.php/topic,6616.0.html
- Sell/Sack GUI M-click logic update: https://openxcom.org/forum/index.php/topic,6612.msg104401.html#msg104401
- In debug mode, show all units on the minimap too
- Don't use piloted interceptors in New Battle mode
- Added armor flag to prevent moving (see below)
- Hide "Not awarded yet" button (in Commendations Pedia) when not needed
- Added mod option to give full score also for researched artifacts/captives (see below)
- Removed "coup de grace" user option
- Increased the globe country label width by 50%
- All soldier lists can now be reordered with the mouse wheel (by BTAxis)
- -cont/-continue command line arg to load the last saved game at start
- (Intentionally) Crash on missing research ruleset (instead of just logging and ignoring it)
- Fixed bug that prevented 'sniper' AI from attacking
- Fix crash on map light calculation
- Reduced mod loading time and memory usage by lazy-loading extraSprites: https://openxcom.org/forum/index.php/topic,3287.msg104264.html#msg104264
- Modifier for morale loss (by unit/soldier type) when a unit is killed: https://openxcom.org/forum/index.php/topic,6615.0.html
- Ctrl + M-click = Mind probe (in debug mode)
- Introduced Multi-Layered Paperdolls: https://openxcom.org/forum/index.php/topic,6290.msg104464.html#msg104464
- Alternative (shorter) ruleset for defining single sprites (see Layered paperdolls thread above for examples)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Requested by The Reaver of Darkness:
giveScoreAlsoForResearchedArtifacts: true # default is false; when true researched artifacts and interrogated prisoners still give full score in debriefing
Requested by bulletdesigner:
armors:
- type: STR_FLYING_SUIT_UC
allowsMoving: false # disables all kinds of movement, except for turning around on the spot
-
- Don't use piloted interceptors in New Battle mode
Is this about geoscape or battlescape? Can elaborate on what that means?
-
Is this about geoscape or battlescape? Can elaborate on what that means?
It means that interceptors that support just a few soldiers/pilots, and have "allowLanding: false" will not be available to use in the combat simulator (New Battle mode).
Requested here: https://openxcom.org/forum/index.php/topic,5566.msg104348.html#msg104348
-
It means that interceptors that support just a few soldiers/pilots, and have "allowLanding: false" will not be available to use in the combat simulator (New Battle mode).
Understood. Thanks for the update.
-
May I request a simple feature? fuelMax increases craft fuel by an additive amount. Can I have a variant stat that boosts it by a percentage?
Alternative request: a fuel stat which increases the fuel max by an integer relating to its refueling item. Example: a firestorm gains 5 fuel per unit of elerium. If you give it a modification with fuelStorage: 3 then its fuel increases by 15, and it takes 3 more elerium to refuel. This way the fuel bonus is additive but takes craft fuel efficiency into account.
The second one is the one I am more interested in, however I'll take either one.
-
What exactly you want to achieve? Overall adding multiplicative will be very hard because what you will multiply? Right now stats are additive because you can easy add and subtract values in any order you want but when you add multiply in mix then you can have multiple answers depending on order.
I could made other thing, instead of changing `fuelMax` I could change fuel usage in multiplicate way. This could have interesting gameplay decisions like: boosters that make craft faster but reduce range.
-
I could go for that. Mostly I want the fuel mods to have some better balance between craft with highly differing efficiencies. I have elerium refuel rates all the way from 5 to 100 across the several craft in my armada. If I make an elerium fuel mod which increases fuel capacity by 30, the Firestorm can use it to go twice as far but the Stalker gains only 3% flight time.
It would be nice to have an option to change fuel efficiency as a separate feature, but I'd like to be able to improve flight time without improving efficiency, and still have the change work well for craft of different base efficiencies.
- - -
Here's some math for my above idea about increasing fuel items:
fuelStorage: A
refuelRate: B
aircraft fuelMax: Xa
mod stat|fuelMax: Xb
net fuelMax: X
X = (A*B) + Xa + Xb
So the way it works is it's all additive. If your aircraft has a fuelMax of 60 and a refuelRate of 15, it takes 4 fuel items to fill it up and it flies for 600 minutes (10 hours). If you then add a mod which gives it fuelMax: 20, its fuelMax goes up to 80 and it now takes 6 fuel items to fill up, and it flies for 13h20m. If you then add another mod which gives it fuelItems: 3, it increases its net fuelMax to 125, it now takes 9 fuel items to fill up, and it flies for 20h50m.
-
I somehow fail to understand the examples.
For example, if a craft had fuelMax 60 and you mod it to have fuelMax 20, it won't be 80... it will just be 20.
If you can please rewrite the example with real ruleset attribute names (instead of "fuelStorage", "mod stat|fuelMax" etc. ) and real values, it would help me understand it.
Also, the formula is wrong, no matter how I look at it... aircraft's net fuelMax is just its fuelMax plus fuelMax of all its equipped "weapons".
So X = Xa + (Y1 + Y2 + Y3 + Y4), where Y1-Y4 are fuelMax of the equipped weapons.
Your variables A and B are nowhere in the formula, and I don't even know what Xb is supposed to be.
-
I think what's needed are bigger fuel tanks that can't be equipped on a smaller craft.
So, I dunno, make more craft slot types?
EDIT:
or make the same fuel tank's capacity vary by the craft it's mounted on? It that what you're suggesting, Reaver?
-
or make the same fuel tank's capacity vary by the craft it's mounted on? It that what you're suggesting, Reaver?
As far as I understood his idea, he suggests changing the fuel efficiency, and not the amount of fuel itself. The use of some parts increases the amount of fuel, the use of other parts increases the flight distance by a certain percentage (through multiplication) with the same amount of fuel. Therefore, in the formula there is an addition (for additional fuel tanks) and multiplication (for engine improvements). But maybe I did not understand him that way.
-
I somehow fail to understand the examples.
For example, if a craft had fuelMax 60 and you mod it to have fuelMax 20, it won't be 80... it will just be 20.
If you can please rewrite the example with real ruleset attribute names (instead of "fuelStorage", "mod stat|fuelMax" etc. ) and real values, it would help me understand it.
Also, the formula is wrong, no matter how I look at it... aircraft's net fuelMax is just its fuelMax plus fuelMax of all its equipped "weapons".
So X = Xa + (Y1 + Y2 + Y3 + Y4), where Y1-Y4 are fuelMax of the equipped weapons.
Your variables A and B are nowhere in the formula, and I don't even know what Xb is supposed to be.
I tried to make it as clear as possible.
fuelStorage: A - this is the attribute I am suggesting be added, as I explained in previous posts
refuelRate: B - the refuelRate attribute on craft
aircraft fuelMax: Xa - the fuelMax attribute on craft
mod stat|fuelMax: Xb - the fuelMax attribute on craftWeapon
net fuelMax: X - the total fuelMax attribute used by the aircraft when you use it in-game
X = (A*B) + Xa + Xb
crafts:
- type: STR_INTERCEPTOR
fuelMax: 800
refuelRate: 50
weaponTypes:
- 1
- 1
- [0, 1, 2]
weaponStrings:
- STR_AIR_WEAPON_SMALL
- STR_AIR_WEAPON_SMALL
- STR_AIR_WEAPON_MEDIUM
- type: STR_UPGRADE_FUEL_TANKS_A
stats:
fuelMax: 200
launcher: STR_UPGRADE_FUEL_TANKS_A_UG
weaponType: 1
- type: STR_UPGRADE_FUEL_TANKS_B
stats:
fuelStorage: 6
launcher: STR_UPGRADE_FUEL_TANKS_B_UG
weaponType: 1
The Upgrade A would add 200 to the Interceptor's fuel capacity, while the Upgrade B would add 300 to its fuel capacity (refuelRate: 50 * fuelStorage: 6).
- - - - -
EDIT:
or make the same fuel tank's capacity vary by the craft it's mounted on? It that what you're suggesting, Reaver?
My suggestion would have that effect.
I'm trying to get fuel tanks that adjust their size to the size of the fuel tanks of the craft they're being put on. To give a strong example, I have two craft which both use elerium fuel: the Firestorm and the Stalker. The Firestorm has a fuelMax of 30 and a refuelRate of 10, while the Stalker has a fuelMax of 1000 and a refuelRate of 100. If I make a fuel upgrade that increases fuel by 30, it'll double the Firestorm's fuel capacity (which will then cost +3 elerium to refuel) but the Stalker's capacity will only be increased by 3%, and it'll use only 30% of the extra 1 elerium it takes to fill it to full. But if I make a fuel upgrade that increases fuel by 300, while it will increase the Stalker's flight time by 30% and its refuel cost by 3 elerium, if applied to the Firestorm its fuel capacity would go up to 330 and it would take 33 units of elerium to refuel it.
And I can't just use a different kind of fuel tank for the two craft because I have other refuelRates on other craft:
Firestorm: 10
Heracles: 40
Assassin: 75
Stalker: 100
And more. I don't want to make a different fuel upgrade for every differing level of fuel efficiency.
- - - - -
As far as I understood his idea, he suggests changing the fuel efficiency, and not the amount of fuel itself.
I am interested in such a feature, but it wasn't my primary suggestion. I was suggesting a feature which would give an amount of fuel that is altered by the craft's fuel efficiency (specifically multiplied by its refuelRate attribute).
It would be cool to be able to change craft efficiency. Howabout a factor in which you increase refuelRate by a percentage? It would be nice to also have one which increases fuelMax by a percentage. The math on these percentage increases is easy: you add together the percentage bonuses on all the modules with the same attribute, and then increase the craft's value by the final percentage.
For example, I equip a Fuel Tank A (fuelPercent: 30) and a Fuel Tank B (fuelPercent: 50) to a craft with 500 fuelMax. You add together the two fuel tanks to get an 80% increase to the craft's fuelMax, which brings it to 900.
To make another example, I equip Fuel Efficiency Mod A (fuelEfficiency: 25) and Fuel Efficiency Mod B (fuelEfficiency: 160) to a craft with a refuelRate of 40. You add together the two mods to get a 185% increase to fuel efficiency, which brings the craft's refuelRate to 114.
-
My suggestion would have that effect.
Then why just not make a new attribute for the equipment item, like fuelMaxPercentage or something, exclusive with the old fuelMax attribute, which will just add that much percent of the craft's fuelMax?
i.e.
craftFinalFuelMax = craftFuelMax * ( 100 + slotA.fuelMaxPercentage + slotB.fuelMaxPercentage + ... ) / 100
This story with making it depend on refuelRate is kind of too complicated in my opinion.
EDIT: or, alternatively, express equipment fuelMax in units of refuelRate (which is the core of your suggestion I think).
But there's no reason to keep the old equipment's fuelMax around - it'll only complicate things and waste fuel
-
I just want one of these things, or something to solve my dilemma.
-
New OXCE version is up.
2018-10-14
- Missions spawned by alien bases can now target different regions: https://openxcom.org/forum/index.php/topic,6557.msg104976.html#msg104976
- Added mod switch for HK fast retarget: https://openxcom.org/forum/index.php/topic,5717.msg104986.html#msg104986
- Added support for alien missile strikes (on Geoscape): https://openxcom.org/forum/index.php/topic,6557.msg104920.html#msg104920
- Added support for Earth-based alien operations: https://openxcom.org/forum/index.php/topic,6557.msg104669.html#msg104669
- Script support for post-mission soldier stat improvement: https://openxcom.org/forum/index.php/topic,6619.msg104686.html#msg104686
- Protect Stats for Nerds "related items" that are not unlocked yet (ammo, built-in-items, ...)
- Support for alien base upgrades (based on its age): https://openxcom.org/forum/index.php/topic,6430.msg104530.html#msg104530
- More scaling options for very high resolutions: https://openxcom.org/forum/index.php/topic,6620.0.html
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Disclaimer: breaking change for hunt missions... please update your mods, more info: https://openxcom.org/forum/index.php/topic,5717.msg104986.html#msg104986
-
Since I didn't see any post mentioning a bug-dedicated thread, I'll put this here.
I noticed a weird bug (using latest GIT commits) => when selecting an item in the inventory screen, it's BIGOBS sprite doesn't follow the mouse cursor, but is stuck at (0,0) coordinates.
Changing Inventory.cpp blit:
Old
_selection->blitNShade(this, 0,0);
New
_selection->blitNShade(this, _selection->getX(), _selection->getY());
Seem to solve the issue.
Awaiting to confirm this in order to PR an OXCE-updated inventory per armor feature (see OXC PR1210)...
-
Yup, another side effect of my big refactor. As you already did it and test that then create pull request, I will merge it.
-
Awaiting to confirm this in order to PR an OXCE-updated inventory per armor feature (see OXC PR1210)...
I've seen this in OXC and I need to have a closer look at it... but most likely I will take it into OXCE.
And after a bit of testing, it will probably be merged to OXC as well.
-
I've seen this in OXC and I need to have a closer look at it... but most likely I will take it into OXCE.
And after a bit of testing, it will probably be merged to OXC as well.
Adapted already for OXCE (I hope ;))... PR 20...
-
Dear Meridian,
Can you please teach me/us how to "steal" some mods from the truly amazing megamods out there? For example, I would just like sniper rifles addes to the vanilla, or maybe a gym.
Thank you for your patience and dedication!
-
Can you please teach me/us how to "steal" some mods from the truly amazing megamods out there? For example, I would just like sniper rifles addes to the vanilla, or maybe a gym.
Below I have attached an example mod containing the .308 Sniper Rifle from The X-Com Files total conversion mod. Download it, install it, and pop open the ruleset in notepad++ so you can follow along as I explain how I built it.
You can just copy the code into a separate ruleset file and place it in its own mod directory. To figure out how to do that, look at other small mods as examples. Then just copy the relevant data from the large mod into your mod in the same format as it is in the small mod. Lastly, make sure you test it thoroughly!
Here's an example for the sniper rifle, which I copied from the items ruleset in X-Com Files. You want to take out some unnecessary elements. The original sniper rifle code from X-Com Files has a lot of excess data that we don't need. The simpler it is, the easier it is to handle. I removed the categories and research requirement, because our mod doesn't have the category list or research projects from X-Com Files. The rest of the fluff I'll just leave in place, but most of it could be removed without problem. To know which to leave and which to take out, check the OXC ruleset reference (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)). Anything not listed there you can do without and it won't break the mod, though it might detract from the quality of the mod.
The next part is to figure out all the extra parts we need. The most generic components other than the item entry are the graphics, sounds, and language entries. All of the lines which call for a sprite or sound file you'll notice have a number next to them, for example: bigSprite: 609. This means that the Sniper Rifle is calling for #609 from the bigSprite list. We'll want to grab these things from the extraSprites and extraSounds files. The bigSprite, floorSprite, handSprite, bulletSprite, and hitAnimation come from the BIGOBS.PCK, FLOOROB.PCK, HANDOB.PCK, Projectiles, and SMOKE.PCK sections of the extraSprites ruleset, respectively. (sic) We will not need entries from Projectiles or SMOKE.PCK because the numbers given for those on our Sniper Rifle (2, 26) are vanilla numbers which do not need resources. Usually when the number is very small, it is a vanilla resource. Mods typically use numbers that are 3 digits and up.
I copied the BIGOBS.PCK, FLOOROB.PCK, and HANDOBS.PCK sections over, carrying only one or two entries each (one for the rifle, one for the clip). Note the following data in the HANDOB.PCK entry:
height: 40
width: 256
subX: 32
subY: 40
This indicates that the entire image is 256x40 pixels and is subdivided into units of 32x40 pixels. All entries in HANDOBS.PCK should use the same value, but it is important to match the dimensions to the image file you're using. If you call the wrong size image, the game will crash on loading. If you call the right size, but the subdivisions are wrong, the textures will be fragmented and out of place. But we are just copying data from a different mod which presumably got the numbers correct so we should be fine.
Next we need the actual graphics files. The data we just copied over lists the file path, starting in your mod's main folder. For example, the bigObs #609 is to be found in {mod folder}/Resources/Weapons_Compilation/ClassicWeapons/bigob_SniperRifle.gif. Since we don't have those folders, we must either create them or change the file path. I choose to make a resources folder and delete all other folders from all file paths. So our final path is changed to Resources/bigob_SniperRifle.gif. So I created a folder called [Resources] and then searched for each graphics file we need in X-Com Files and copied them into my [Resources] folder, then I removed the extraneous folders from the file paths in extraSprites.
Now we need the sound files in extraSounds, from the BATTLE.CAT section. It's fireSound: 76 and hitSound:77 so we find those entries and copy them over just like with extraSprites. Then we copy the sound file over (and repair the file path).
Now we just want the language file and we should be done. We don't need to do anything more than copy it over. The game automatically reads all string values (such as STR_SNIPER_RIFLE) and checks your current language file for a corresponding entry. And it's also okay to not have the language file. If it doesn't find it, it'll just call the weapon STR_SNIPER_RIFLE instead of calling it Sniper Rifle. We get the language file from the extraStrings section corresponding to our chosen language--I'll go with en-US. Now if you've found STR_SNIPER_RIFLE in the language file, you'll notice there is a language entry for a UFOPedia topic on the rifle included in there as well. We can use that to add the UFOPedia project, but I'm not going to cover that at this stage. You can search X-Com Files and try to add it yourself if you like. You will need to find its entry in the ufopaedia section, and make sure you remove the research requirement from the ufopedia entry like we did with the item, unless you intend to instead copy the research project into the mod.
- - - - -
If you wish to try your hand at adding a gym from a big mod: find one in the facilities section of its ruleset and copy it over. You'll want to get the spriteFacility from BASEBITS.PCK in the extraSprites section. You will also want to copy over the corresponding map file from the MAPS folder, the routes file from the ROUTES folder, and any terrain files it uses from the TERRAIN folder. Make sure your mod has these folders just like this. The entry in facilities tells its MAPS/ROUTES/TERRAIN data at mapName, where it links to an entry in the terrains section. You'll probably find the facility map in the section called XBASE or something similar. You'll need to copy over the full mapDataSets entry, any mapBlocks that are used in your facilities, and all terrain files (from the TERRAIN folder) that are listed in the mapDataSets entry. If the mod doesn't contain one of the terrain files, it's probably a vanilla file which you won't need, such as BLANKS.
- - - - -
Once you feel like you're done, or at a good stopping point, you should test everything you added to your mod. We just added a sniper rifle, so we want to run the mod, start up a random battle, load the sniper rifle and ammo onto our ship, and try using and firing the weapon at an alien or two. If everything works out, then we have probably copied the mod correctly. If there are any unexpected errors, you can ask for help from the community either here on the forums (ideally in a new post in the Work in Progress subsection) or on our Discord channel (https://discord.gg/j6TVGd). Please don't post any replies to this message here in this thread. If you make a new thread in Work in Progress, I will see it and visit it.
-
Thank you, Reaver for your clear and detailed response! Much obliged, kind sir.
-
I'm having trouble adding (i.e. running it together, loading last) Biggieboy82's Large Workshop to an existing mod (xcomfiles in this case). It keeps messing up base defense terrains:
terrains:
- name: XBASE
addOnly: true
mapDataSets:
- BLANKS
- XBASE1
- XBASE2
- XBASE3
- BATHWALL
- BATHBITZ
mapBlocks:
- name: XBLW_01
width: 10
length: 10
- name: XBLW_02
width: 10
length: 10
- name: XBLW_03
width: 10
length: 10
- name: XBLW_04
width: 10
length: 10
In particular, i couldn't find any documentation for the "addOnly" switch. As far as i can tell it doesn't work as intended, as it overwrites the map datasets when it's supposed to add them the list. This is xcomfiles terrain definition:
- name: XBASE
mapDataSets:
- BLANKS
- XBASE1
- XBASE2
- XCOMWALL
- XCOMBITS
As far as i can tell the mod is only supposed to add the missing datasets - instead it overwrites them and deletes those not on the list, messing up existing blocks. The only way i can get it to work is by deleting the datasets line alltogether, but of course it then fails to load on a base defense that includes the large workshop. Any hints on how i can get this to work?
EDIT:
Nevermind, works fine without the mapDataSets.
-
OpenXcom is supporting only 8bit graphic
Since when? Maybe we should go back to the way it was? In version 5.0 such mess was not.
-
Since when? Maybe we should go back to the way it was? In version 5.0 such mess was not.
Since the beginning!
When you got lucky, some 24bit images may have loaded... but not always and not for everyone. They are also not supported in OpenXcom, and they never were.
-
I mean, it would be nice to undo all the changes in image support that have been made since version 5.0.
-
I mean, it would be nice to undo all the changes in image support that have been made since version 5.0.
For what reason?
Did something break?
(except for not loading 24bit images... which were not and still are not supported)
-
For what reason?
Did something break?
(except for not loading 24bit images... which were not and still are not supported)
It's broken, from my point of view. I have are worth both version of. In version 5.0, images work, but in version 5.1 - they don't. The theoretical knowledge that they should not work does not change anything. The fact remains - in version 5.1 there are some changes that lead to the error of previously working images.
-
I don't know what to answer to that.
From my point of view, it was broken before and now it is correct.
If you want more opinions, feel free to ask Yankes/SupSuper/Warboy... maybe they can provide more arguments, or explain better than I can.
-
As in 99% cases OXC use only 8bit images when I did refactor and optimization of surfaces I remove loading of multi byte graphics.
-
I don't know what the arguments, but... I have nothing to replace the images that are not working in the new version. That's the whole point. Apparently I will have to continue using version 5.0. Until find a replacement.
-
I don't know what the arguments, but... I have nothing to replace the images that are not working in the new version. That's the whole point. Apparently I will have to continue using version 5.0.
You don't know how to convert them into 8bit graphics?
I can help with that if you want... I assumed all modders know how to work with xcom palettes.
I made a small tutorial for luke83 here, maybe it helps you too: https://openxcom.org/forum/index.php/topic,6750.msg107256.html#msg107256
-
You don't know how to convert them into 8bit graphics?
I can help with that if you want... I assumed all modders know how to work with xcom palettes.
I made a small tutorial for luke83 here, maybe it helps you too: https://openxcom.org/forum/index.php/topic,6750.msg107256.html#msg107256
Thank you, of course, but it won't help me much. I don't know English. I'll try using Photoshop to do it. It'll work out eventually.
-
Hi Yankes, can I request that the awardExperience script be given a ptre to the attacking unit instead of a ptr? I'd like to be able to set a tag on a unit when it gains experience for handling of bonus stat gains at the end of a mission, but only once they've gained some experience.
Also, it looks like the getGeoscapeSoldier function is misspelled as getGeosapceSoldier compared to the pointer type GeoscapeSoldier.
Edit: I'm also having an issue with animating an item floorob - the following works to re-select the frames when the item is blit as a handob, but not for floorob. Outputting anim_frame to debug_log shows that it remains 0 for the floorob, and the selectItemSprite script doesn't have access to the BattleGame to get the frame either:
items:
- type: STR_GRENADE
floorSprite: 100
scripts:
selectItemSprite:
if eq blit_part blit_item_floor;
set sprite_offset anim_frame;
mod sprite_offset 3;
#debug_log 1 anim_frame;
#debug_log 2 sprite_offset;
end;
add sprite_index sprite_offset;
return sprite_index;
-
Changing `ptr` to `ptre` is usually one line change but I try keep everything read only, main reason is that I can reason what scripts can and what can't do.
If I change it to writable version should I prepare code to handle instant death of unit after this script run? Because of this I leaving this as read only.
One thing I could think is give access only to `tag` object as writable because game engine do not relay on this values.
Btw maybe there is other place where you logic could be placed? Right now after mission you can access `battleUnit.Exp.*` where all stats grain are stored.
For function, you misspelled misspelled function too :D, I will fix it right now.
For script, right, I do not propagate it there, this will be fix too.
-
Ah, I missed the BattleUnit.Exp.<x> in the documentation, that does what I need it to do, thanks! I think it'd still be nice to have access to setting tags even where we have ptr instead of ptre, but not necessary for this application.
-
bugs fixed, now select sprite can have access to shade and animation frame.
-
I don't know what the arguments, but... I have nothing to replace the images that are not working in the new version. That's the whole point. Apparently I will have to continue using version 5.0. Until find a replacement.
@Ethereal
I have converted all 24bit images from your mod (the latest available on the forum) to 8bit images.
You can find them in the attachment.
-
@Ethereal
I have converted all 24bit images from your mod (the latest available on the forum) to 8bit images.
You can find them in the attachment.
Thank you very much!
Unfortunately, I lost the battle with Photoshop as it was my first experience with it. I can not get him to save files in "png" format.
-
I can help with that if you want... I assumed all modders know how to work with xcom palettes.
I guarantee you less than half of modders, by number, know how to work with X-Com palettes. Remember, this is OpenXcom, an incredibly easy format for non-programmers to get into.
-
New OXCE v5.2 is up.
2018-12-22
- Updated OXCE language files
- Updated OXC language files
- Ability to redefine main menu background image
- Allowed running, kneeling and strafing for all units
- Required item(s) per starting condition (by Finnik)
- When gym is destroyed, people stop training
- Fixed getOneFreeProtected being ignored when getOneFree was not defined
- Reworked case-insensitive search (hopefully works better now)
- Show armor movement type in Stats for Nerds
- Added AI option for destroying XCom base facilities: https://openxcom.org/forum/index.php/topic,6663.0.html
- Ability to replace damaged buildings with rubble: https://openxcom.org/forum/index.php/topic,6668.msg105753.html#msg105753
- Ability to define how likely a facility is to be damaged by a missile: https://openxcom.org/forum/index.php/topic,6668.msg105690.html#msg105690
- Fixed multiple simultaneous base defenses (in the same game tick)
- Fixed directional lighting
- Fixed TU recovery on multi-stage missions
- Vanilla: Added "transferTime" property to ruleset soldiers
- Vanilla: showing (approximate) craft range at take-off
- Vanilla: added support for bigger globe markers
- Vanilla: scrollable ufopedia categories
- Engine: rendering speed optimisation
- Engine: only 8bit images are supported (which was always the case, but now it is enforced!)
- Engine: transparency on color index 0 is now enforced (for now there can be one more additional transparency index, but only until OXCE 5.3)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
I have discovered a bug in 5.1 version, that is not listed as fixed in this list. Yesterday I discovered it on Android and today I confirmed it on Windows version.
Effect: Using special abilities by any unit.
Required: A unit with a special ability that has a menu (X-COM Files "Attack Dog", XPirates "Bug"), any other unit.
How to replicate: Select the psionic unit. Move the map so, that the special ability icon is over the unit you want to use it.
Click the special ability icon. The menu for using the ability appears and the unit under the icon is selected.
Use one of the abilities from the menu. The newly selected unit uses it with all that means. (The selected unit is pays the
cost of the ability with correct percentages, the selecteded unit's stats are used and trained.)
It only happens with abilities that drop menus. If the ability does not have a menu, such as with X-COM Files "Hybrid", the unit below the icon is not selected.
-
Confirmed, it's any weapon that uses the 'special weapon' code, separate from the vanilla 'psi button' reserved for being able to use Psi Panic with mind controlled aliens - the action of clicking on the button continues on to whatever is below the button when you cancel the menu. You can see this if you click on the button not on a unit, it'll bring up the movement preview if you have that option on, or start moving the unit if you don't have it on. I'm testing a fix right now.
-
Confirmed, it's any weapon that uses the 'special weapon' code, separate from the vanilla 'psi button' reserved for being able to use Psi Panic with mind controlled aliens - the action of clicking on the button continues on to whatever is below the button when you cancel the menu. You can see this if you click on the button not on a unit, it'll bring up the movement preview if you have that option on, or start moving the unit if you don't have it on. I'm testing a fix right now.
Any news on that fix? or does this not affect vanilla MC/Psi?
-
Thank you for a great unified mod!
I always read every change list with interest.
Everything is invented very cool and convenient.
The only thing ... I would like to have a smarter AI ... ... but this is probably impossible in principle.
-
Any news on that fix? or does this not affect vanilla MC/Psi?
Fix is now available (PC version only for now).
The bug doesn't affect vanilla MC/Psi.
-
Fix is now available (PC version only for now).
The bug doesn't affect vanilla MC/Psi.
Alright awesome. I grabbed it, I was testing a tank with a special weapon, so this will be good.
-
You need professional help. Really.
-
Is any option to disable hunter alien UFOs who randomly attack and destroy my transport and scout ships in Area 51 mod? Last time my Skyranger was killed when I returned from successful mission. I like this project because of a lot little great features in compere with original openxcom, but those hunter UFO's completely annoys me.
-
Is any option to disable hunter alien UFOs who randomly attack and destroy my transport and scout ships in Area 51 mod? Last time my Skyranger was killed when I returned from successful mission. I like this project because of a lot little great features in compere with original openxcom, but those hunter UFO's completely annoys me.
OXCE only adds support for hunter-killers, it doesn't enable them automatically.
The hunter-killers were intentionally added into the mod by the modder, not by the devs.
If you don't agree with that, you can turn them off by editing the mod's ruleset files, in this case:
1/ alienMissions_Area_51.rul file... search for all occurrences of hunterKillerPercentage and change the numbers after that attribute to 0
2/alienDeployments_Area_51.rul file... search for all occurrences of baseDetectionRange and change the numbers after that attribute to 0
EDIT (SET AS REMINDER!!! :o):
Uh, Houston. We got a big a$$ problem.
The geoscape radar systems in OXCE has a bug, but never been fixed. Take a look at the image i've did using snipping tool app instead of F12.
(https://openxcom.org/forum/index.php?action=dlattach;topic=6586.0;attach=40678;image)
See, messed up radar bug in OXCE.
That bothers me with the older OXCE version i'm playing instead of the newer version.
What a bad relief. :-[
It's not a bug, it's a feature.
And it comes from OXC, not from OXCE.
-
Today I discovered a bug (not sure) - if you escorting you transport ship on the mission and get attacked by alien hunter UFO, both aircrafts lose their destination after successful dog fight and turning back to their base, so you need point you Skyranger again on mission objective at the map and re-escort it with you Interceptor.
-
Hey Meridian, how about returning to base not only soldiers from destroyed Skyranger but their equipment too, at least what they're carrying on themselves? It's kinda unfair what they're evacuates but drop their staff. Just suggestion anyway.
P.S.
Started another new game (yes I'm stubborn as a mule :) ), and Skyranger was destroyed when it returning back from Abandoned factory mission. It had escort, but it won't help - encountered very large, my Avalanche did nothing to it. Aliens killed transport but when run away from Interceptor. Very strange behavior. So harsh. But I like this is challenge and no longer cries ;)
-
Today I discovered a bug (not sure) - if you escorting you transport ship on the mission and get attacked by alien hunter UFO, both aircrafts lose their destination after successful dog fight and turning back to their base, so you need point you Skyranger again on mission objective at the map and re-escort it with you Interceptor.
The crew of the transport ship,
- Fuck it all! On the approach are attacking! Turn back!
Fighter pilot,
- Hey, where are you going?!
The crew of the transport ship,
- Home!
Fighter pilot,
- Then accompany yourself!
A typical mess in the ranks of the retreating army. :D
Hey Meridian, how about returning to base not only soldiers from destroyed Skyranger but their equipment too, at least what they're carrying on themselves? It's kinda unfair what they're evacuates but drop their staff. Just suggestion anyway.
If this equipment is not secret, then it is not a pity to quit. And if the secret, then it is wise to destroy it on the spot, so that it does not get to aliens, terrorists, or some other hooligans.
-
Why don't they remain at the crash site and wait for X-Com to pick them up? Here's an idea:
They wait at the site. If you do pick them up, you get to keep anything that survived the crash. But as long as the site waits there, aliens might go after it, and if they get it, you lose points for all soldiers lost to the aliens, and for all equipment the aliens recover. So if you decide you don't think you can make it (or you see a UFO heading for them), then you can remotely command the site be destroyed. If you issue that command, the site will disappear, all equipment will be lost, and the surviving soldiers will make their way back to base on their own over several days.
-
Why don't they remain at the crash site and wait for X-Com to pick them up?
Because people tend to not just sit around and twiddle their thumbs, but rather get to the nearest inhabited area for potential medical treatment and to buy pizza and coke instead of starving.
Also, there is no crash site, the craft was destroyed in the air, they barely managed to eject/jump and didn't take anything with them other than a parachute.
Lastly, unless you are in Antarctic, Sahara or middle of Amazon... the accident will be seen by local military/government and local rescue forces will arrive to help sooner than Xcom.
Here's an idea:
They wait at the site. If you do pick them up, you get to keep anything that survived the crash. But as long as the site waits there, aliens might go after it, and if they get it, you lose points for all soldiers lost to the aliens, and for all equipment the aliens recover. So if you decide you don't think you can make it (or you see a UFO heading for them), then you can remotely command the site be destroyed. If you issue that command, the site will disappear, all equipment will be lost, and the surviving soldiers will make their way back to base on their own over several days.
Nice idea.
Too much work, not interested.
-
Nice idea.
Too much work, not interested.
As a suggestion, I can state the idea that came to me when the UFO Hunters-Killers were added. It is somewhat simpler, maybe it will not be so difficult to implement it. The idea was to equalize the capabilities of people and aliens, not only in air combat, but also in ground combat. Now people can attack downed UFOs, and aliens cannot attack people from a downed transport worker. So, the idea was that the Hunter-Killer should have another property - can they sit down after people from a downed transport worker. It makes sense to assign this flag to big Hunters carrying many aliens and terrorist units. Small ones, with a small detachment of aliens, have little chance of winning, so the flag is not assigned to them - they only shoot down planes. So, if the Hunter-Killer knocks down an X-Com transport, then if he can, then he descends after the survivors and lands. At the same time, the soldier scatters around the battlefield (they parachuted with parachutes and did not have time to group themselves), and from their weapons and equipment they only had what had been assigned in advance. There was no equipment window before the fight, but the one that was already assigned was fastened to the uniform or was at hand, so professional soldiers could grab this weapon when leaving the ship. The aliens themselves are partly inside the UFO, partly manage to disperse across the battlefield (as they do now when attacking a stranded UFO). However, many people may be at a disadvantage, surrounded by enemies. The initiative of the first move will be for attacking newcomers, but the X-Com soldiers will have the opportunity to respond to the return fire, as it is now on the first move in a normal battle, only the sides change places. Opportunities to evacuate people do not have - refusal from battle is a recognition of defeat. In case of victory, soldiers can use the help of local allies to return to the base, but lose all trophies (they are picked up by the local army or whoever is there), and their equipment is destroyed, according to the instructions. That is, the return will still not be fast, all equipment is lost, only the battle is added, in which the soldiers have to defend their right to life.
Sorry if it turned out incomprehensible. The text was translated into English with the help of a Google translator.
Update:
Yes, probably it is better to clarify right away. I myself do not create fashion, so this was an offer from a player who wants to see diversity in mods, not a modode's proposal. And it is worth realizing it only if there are interested mod creators interested in it. They may somehow complement it, how it will be better suited to them.
-
Speaking of ideas. Required in air combat with the HK one on one, to make the automatic destruction of the ship X-COM, if the velocity of the ship X-COM is lower than that of the UFO(no possibility to fly away), and he'd run out of all ammo or no weapons.
There were cases when, thanks to the modules, the evasion of the transport ship exceeded the accuracy of UFOs. Or the rate of UFO fire and damage did not allow to break through the energy shield of unarmed transport. In these cases, the air battle becomes endless.
Yes I know. Transports should accompany the interceptors, but at the beginning of the game, these interceptors can be destroyed even by small UFOs, and transport, hung with protective modules, can be impenetrable for small UFOs.
-
That's a mod balance issue, not a code issue.
Don't make your transports invulnerable or the HK UFOs impotent.
-
I agree with you. But it happens that the transport just a lot of HP. Implementing my offer will save a lot of time for the player.
-
If anything were to happen... I'd say the attacker should give up after a while. How long can you chase an unhittable target?
After all that's what X-Com does (though the actual reason is limited ammo).
PS. Honestly I don't think it's that easy for a modder to predict which transport is fine and which will make the game effectively freeze.
-
The feature is called "hunter-killers"... that's the guys that make you regret you were born. If you use the feature to implement alien holiday cruise ships with little alien children shooting at xcom from their little alien plastic pea-shooters... it's your decision, I don't judge... but don't expect a feature designed to support HKs to support also your alien holiday cruise ships.
In my opinion, the game already has more than enough options to implement HKs, in several different ways, even if you have very different early/mid/late game.
If it's such a big problem, I can add a self-destruct button/hotkey (or if you want think about it as HK giving up and setting a collision course with your craft)... but I'm not making a HK abort its mission... HKs either kill you or die trying.
-
Well, it's not like I've ever actually needed to use this, but I dig this [self-destruct!] button idea for the sheer awesome potential. :D
-
The modder can allow you to put defensive weapons on your transport, and it is entirely up to them how durable your transports are and how rough the HKs are. If they are sending battleships at your transports which chase them down at high speed and pulverize them rapidly, then I think it was the modder's intent to make you feel that your transports are not sacred. I would respond by selecting one of the following options:
1.) purchase multiple cheap transports, troops, and equipment sets
2.) play a different mod
-
The modder can allow you to put defensive weapons on your transport, and it is entirely up to them how durable your transports are and how rough the HKs are. If they are sending battleships at your transports which chase them down at high speed and pulverize them rapidly, then I think it was the modder's intent to make you feel that your transports are not sacred. I would respond by selecting one of the following options:
1.) purchase multiple cheap transports, troops, and equipment sets
2.) play a different mod
That's totally not on topic Reaver, but I absolutely agree with you.
-
Well, it's not like I've ever actually needed to use this, but I dig this [self-destruct!] button idea for the sheer awesome potential. :D
Potential for awesome misclicks? :P
...why would a friggin' troop transport even have a self-destruct feature in the first place? I'm just imagening having this in X-COM files and your agents being intercepted on a commercial flight, only for guys to blow up the plane. Not that it wouldn't be hilarious (this being xcom after all), but i'd be in favor of a "limited ammuntion" or "ufo breaks off/outruns" feature.
-
As for self destruction - I'm not sure, but the fact that HK will go to ram the ship, which is not able to destroy by conventional means-a great idea. The ram must of course be fatal for the X-COM ship in 100% of cases.
-
Apologizes if I'm posting in wrong forum, but I think this code related bug, actually not bug but exception what not present there. Area 51 mod. Alien Hunter Killer detected, its on screen below:
(https://i.postimg.cc/SJqntKd3/screen004.png) (https://postimg.cc/SJqntKd3)
Now intercept it with Interceptor 3 from USA base:
(https://i.postimg.cc/YhW7cc2F/screen005.png) (https://postimg.cc/YhW7cc2F)
It's going to attack our Interceptor 3:
(https://i.postimg.cc/crqjnvZK/screen006.png) (https://postimg.cc/crqjnvZK)
And when the Dog fight phase starts, the game is crash with messages in log file:
[16-01-2019_00-52-17] [FATAL] A fatal error has occurred: Segmentation fault. This usually indicates something missing in a mod.
[16-01-2019_00-52-17] [FATAL] 0x88db20 OpenXcom::CrossPlatform::stackTrace(void*)
[16-01-2019_00-52-17] [FATAL] 0x8911b0 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[16-01-2019_00-52-17] [FATAL] 0x401750 signalLogger(int)
[16-01-2019_00-52-17] [FATAL] 0x76f653b0 RtlCaptureStackContext
[16-01-2019_00-52-17] [FATAL] 0x76f46540 RtlGetAppContainerNamedObjectPath
[16-01-2019_00-52-22] [FATAL] OpenXcom has crashed: Segmentation fault. This usually indicates something missing in a mod.
But you probably already found what the Interceptor 3 has NO weapons. I forgot equip it after I bought it. That's why I think OXCE crashes. Now the questions:
1. Is this a bug?
2. Could be it fixed if weapon(s) (both or only one, dependence on type of you aircraft, or just how many you decided to equip) missing?
And save file, so you can reproduce it yourself:
-
Now the questions:
1. Is this a bug?
2. Could be it fixed if weapon(s) (both or only one, dependence on type of you aircraft, or just how many you decided to equip) missing?
1/ yes
2/ fixed
-
2/ fixed
Umm... replaced files from latest 15th January archive but game still crashes there, or you haven't uploaded fixed version yet? I guess it should be at least 16th or later data, since I'm posted during night and you replied later.
-
Got it! Wow self destruct, this is something new and funny. :) Thanks for fast fix and reply. By the way, new question regardless dog fight phase - when it starts there is no more option to minimize window and go to world map. Is it possible to add this in case if you forgot send you escort from nearest base? But I guess this is will break game algorithm and mechanics. Just a question, anyway ;)
-
Got it! Wow self destruct, this is something new and funny. :) Thanks for fast fix and reply. By the way, new question regardless dog fight phase - when it starts there is no more option to minimize window and go to world map. Is it possible to add this in case if you forgot send you escort from nearest base? But I guess this is will break game algorithm and mechanics. Just a question, anyway ;)
Self-destruction is active only if there is no way to escape from an overly aggressive UFO - hunter-killer. In a normal intercept all remained as before.
-
P.S. Sometimes slave-piloted tanks disappear from FORTUNA on missions, going to ckeck it once again and write a bugreport.
In the next OXCE version, 2x2 soldiers will always be deployed first, ignoring their position in the list.
They won't disappear anymore, but you won't be able to define their exact position anymore (for example you won't be able to move them to the craft's rear end).
-
Praise the Lord! It was such a headache. Thanks!
-
In the next OXCE version, 2x2 soldiers will always be deployed first, ignoring their position in the list.
They won't disappear anymore, but you won't be able to define their exact position anymore (for example you won't be able to move them to the craft's rear end).
Do not quite understand, it will apply to all 2x2 player units, including HWP, or only a big soldier?
-
Do not quite understand, it will apply to all 2x2 player units, including HWP, or only a big soldier?
Old order:
1. HWPs first (in list order)
2. then Soldiers (in list order)
New order:
1. HWPs first (in list order)
2. then 2x2 Soldiers (in list order)
2. then 1x1 Soldiers (in list order)
-
The fact is that HWPs can be small - 1x1. Not only 2x2. This is taken into account?
It would be more correct to do:
order:
1. 2x2 HWPs
2. 2x2 Soldiers
3. 1x1 HWPs
4. 1x1 Soldiers
-
This is taken into account?
No.
-
New OXCE v5.3 is up.
2019-03-05
- Added lazy loading as a GUI user option
- Ability to specify minimum required OXCE version per mod: https://openxcom.org/forum/index.php/topic,6945.0.html
- Added script support for stat bonuses, including:
* Items: damageBonus, meleeBonus, accuracyMultiplier, meleeMultiplier, throwMultiplier, closeQuartersMultiplier
* Armors: psiDefence, meleeDodge, recovery (time, energy, morale, health, stun)
- Ctrl+Alt+New Project to sort the research list by cost
- Ctrl+Alt+Inventory to delete soldiers' equipment layouts
- Always deploy 2x2 xcom soldiers first, ignoring their position in the list
- When transferring aliens, check store space too (not only alien containment)
- Prison check on Purchase: https://openxcom.org/forum/index.php/topic,6917.msg110499.html#msg110499
- Facilities that cannot be built in a base yet/anymore are shown at the bottom of the list
- Panic/berserk sounds: https://openxcom.org/forum/index.php/topic,6921.0.html
- Changed language loading to default to en-US when translations are missing.
* Prioritize untranslated text over incorrect text. Modders, you can stop copy-pasting en-US to en-GB.
- User option cleanup: https://openxcom.org/forum/index.php/topic,6880.0.html
- Different alien inventory background for xcom soldiers: https://openxcom.org/forum/index.php/topic,5047.msg109930.html#msg109930
- Highlight colors in Ufopedia: https://openxcom.org/forum/index.php/topic,6883.0.html
- Option for AI to pick up weapons more actively: https://openxcom.org/forum/index.php/topic,6882.0.html
- Changed slo-mo hotkey from F8 to Alt+F8
- Added burning indicator to alien inventory view
- Allow to recover spawned xcom units as civilians
- Added randomized manufacturing: https://openxcom.org/forum/index.php/topic,6867.0.html
- Added new script to change move sound: https://openxcom.org/forum/index.php/topic,6758.msg109325.html#msg109325
- Ability to transform items during recovery: https://openxcom.org/forum/index.php/topic,6868.0.html
- Self-destruct button in Dogfight: https://openxcom.org/forum/index.php/topic,5717.msg108512.html#msg108512
- HKs don't attack craft returning from a mission anymore
- Unhardcoded (underwater) breathing animation (per armor)
- Added option to disable underwater sounds
- Added option to disable ocean shading on the globe
- Armor transformation support for aliens and civilians
- Walls can now generate light too (not only floor and objects)
- Engine: reduced idle CPU burn
- Engine: added zip loader: https://openxcom.org/forum/index.php/topic,6922.0.html
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
Another cool relase! I'd humbly advice to post changelogs for the future in another dedicated thread, if possible :)
-
Is anyway to change % of Hunter Killers UFOs dependence on difficulty? Interesting on both parameters: % that UFO what you encounter has chance been HK and % of their hunter attack missions. if it possible, what changes I need make in rules set files?
-
Is anyway to change % of Hunter Killers UFOs dependence on difficulty? Interesting on both parameters: % that UFO what you encounter has chance been HK and % of their hunter attack missions. if it possible, what changes I need make in rules set files?
No, currently not.
-
Thanks for fast reply. Any plans of this feature in future releases? Is it even possible with current rules set format?
I have discovered some interesting bug (or not?) with liquid oil explosion on those kind of maps:
(https://i.postimg.cc/D4KVWmLz/screen026.png) (https://postimg.cc/D4KVWmLz)
If you shoot it, it will explode with long chain, blow, blow, blow.... etc. Sometimes it took 2-3 real life minutes to finish. If you shoot same in classic openxcom, it exploding faster. You can compare yourself, if you want, I'm attaching save file. Now the question is it little bug or just a feature of OXCE?
-
Hello.
I have an idea for a feature.
Some kind of toggle near the TU reserve switches, which tells your units, how aggresive they should be with their reactions.
OFF: Vanilla
ON: Only react to attacks (Firing, throwing)
Default: OFF
Modded in sides should probably have this settable in the mission definition.
I got the idea when playing X-Pirates, and raiding a hopper. Some fat men moved before the killer droid did and got shot.
The intention for this is to make it easier to not accidentaly kill harmless enemies. But the tradeoff is, that the dangerous enemies will get to shoot.
-
Thanks for fast reply. Any plans of this feature in future releases? Is it even possible with current rules set format?
I have discovered some interesting bug (or not?) with liquid oil explosion on those kind of maps:
(https://i.postimg.cc/D4KVWmLz/screen026.png) (https://postimg.cc/D4KVWmLz)
If you shoot it, it will explode with long chain, blow, blow, blow.... etc. Sometimes it took 2-3 real life minutes to finish. If you shoot same in classic openxcom, it exploding faster. You can compare yourself, if you want, I'm attaching save file. Now the question is it little bug or just a feature of OXCE?
It's a feature of OXCE.
(already a very old one)
The thread with OXC/OXCE differences has been updated accordingly: https://openxcom.org/forum/index.php/topic,6459.0.html
-
Questions about difficulties: have you changed rate of alien psi control attacks, weapons powers and armor behavior and etc in compare with open xcom version. I'm replaying area 51 on veteran but failing due to incredible psi attacks. Interesting changes in amount of aliens in every mission too. I mean how many will be generated in their ships, bases and terror (council) missions.
-
Questions about difficulties: have you changed rate of alien psi control attacks
no
weapons powers
no
and armor behavior and etc in compare with open xcom version.
no
I'm replaying area 51 on veteran but failing due to incredible psi attacks.
There was a bug in psi attacks between versions 2019-01-03 and 2019-02-22.
If you have a version older than 2019-01-03 or newer than 2019-02-22, psi attacks work the same as in vanilla.
Otherwise, please upgrade.
Interesting changes in amount of aliens in every mission too. I mean how many will be generated in their ships, bases and terror (council) missions.
That's responsibility of Area 51, not of OXCE.
-
Thank you for fast response and your answers.
There was a bug in psi attacks between versions 2019-01-03 and 2019-02-22.
If you have a version older than 2019-01-03 or newer than 2019-02-22, psi attacks work the same as in vanilla.
Otherwise, please upgrade.
That's responsibility of Area 51, not of OXCE.
Got it! Upgraded. Testing now.
By the way - double stats strings on newest version 5.3.2 (2019-03-18)
"cwmcwm" on screenshot:
(https://i.postimg.cc/XXrNdYrm/screen029.png) (https://postimg.cc/XXrNdYrm)
-
Thank you for fast response and your answers.Got it! Upgraded. Testing now.
By the way - double stats strings on newest version 5.3.2 (2019-03-18)
"cwmcwm" on screenshot:
(https://i.postimg.cc/XXrNdYrm/screen029.png) (https://postimg.cc/XXrNdYrm)
Look here: https://openxcom.org/forum/index.php/topic,5258.msg110802.html#msg110802
You have situation called BAD... please change to one of the situations called GOOD.
-
Some suggestions and questions about soldiers sorting order. Now we have a lot of options, like sort by accuracy, strength etc... But all of them has order from lower to higher. But I'm often like to use opposite effect from higher to lower. Of course, I can do it manually, but may be option in future releases? Or it's already exists and I'm just missing it?
-
Some suggestions and questions about soldiers sorting order. Now we have a lot of options, like sort by accuracy, strength etc... But all of them has order from lower to higher. But I'm often like to use opposite effect from higher to lower. Of course, I can do it manually, but may be option in future releases? Or it's already exists and I'm just missing it?
Click = sort ascending
Shift+click = sort descending
Ctrl+click = don't sort, just show numbers
-
A small request:
Can we have the option of transferring the loot after a battle always available? Say a button alongside with sell, score, exp?
-
New OXCE v5.3 is up.
- Added script support for stat bonuses, including:
* Items: damageBonus, meleeBonus, accuracyMultiplier, meleeMultiplier, throwMultiplier, closeQuartersMultiplier
* Armors: psiDefence, meleeDodge, recovery (time, energy, morale, health, stun)
Great. But where can i get more info about thi? Is there discussion, or maybe an example mod?
-
Example of some dumb script:
armors:
- type: STR_NONE_UC
recovery:
time: |
unit.tuBonusStats bonus 50 10 0 0; #same as old `tu: [0.05, 0.01]`
add bonus 5; #similar to old `flatOne: 5`
limit_upper bonus 100; #impossible in old version, now TU will never reach more than 100 per turn
return bonus;
There is too global version that affect all units/items:
extended:
scripts:
energyRecoveryBonusStats:
- offset: 1
code: |
div bonus 2; #all units have only half energy regeneration
return bonus;
-
It is great, indeed.
And how about item, increasing accuracy or damage, when stored in backpack?
-
Inventory is still off limits for scripts, you have only access to left and right weapon.
-
Inventory is still off limits for scripts, you have only access to left and right weapon.
Maybe I missed the thread where it's explained, apologies if so. Where I can get a list of variables that can be modified by scripts and examples of use? Do I need to dig into the source code?
-
if you run game with debug and verbatim or some thing like that, script engine will do full dump of all possible functions avaialbe in each script.
-
if you run game with debug and verbatim or some thing like that, script engine will do full dump of all possible functions avaialbe in each script.
Please, can you provide an example?
-
Please, can you provide an example?
full dump attached
-
full dump attached
This is a great info. Many things to think of, thanks.
-
full dump attached
Thanks!
-
Is there any reason the the sorting option "First Letter" isn't fully alphabetical? I mean, it's REALLY close, but not quite.
"I have approximate knowledge of many things"
It's fully alphabetical since today.
-
Noticed that opening doors seems to require energy in OXCE (even though none is consumed) whereas it doesn't in OXC. Also, when you attempt to open a door but don't have enough energy, the "Not Enough Time Units" message is displayed.
This is with v5.3.2 / 2019-03-18
-
Yes, it's a known issue.
I'll look at it again soon.
-
What did you do with the sound in the latest version? After the upgrade has changed the sound of death of Sectoids and shock plasma. I didn't do anything myself. I really do not like these changes and please return the sound settings to their original state.
P.S. In general, I found the original sounds in the "wav" format and the situation ceased to seem the End of the World.
P.P.S. Apparently the problem is reading."cat" file.
-
What did you do with the sound in the latest version? After the upgrade has changed the sound of death of Sectoids and shock plasma. I didn't do anything myself. I really do not like these changes and please return the sound settings to their original state.
P.S. In general, I found the original sounds in the "wav" format and the situation ceased to seem the End of the World.
P.P.S. Apparently the problem is reading."cat" file.
Can you share the CAT file that is causing the problem?
(or the entire content of your SOUND directory and your options.cfg file)
-
Can you share the CAT file that is causing the problem?
(or the entire content of your SOUND directory and your options.cfg file)
Yes I can. And ".log" in the appendage. Strangely, a lot of things have been written in ".log", but everything works exactly as intended. And about the sound is nothing.
-
Hi, i have openxcom version on pc and openxcom extender android on tablet, could i play between platforms without problems? Or will i change openxcom on pc to openxcom extender?
Thanks in advance
-
Hi, i have openxcom version on pc and openxcom extender android on tablet, could i play between platforms without problems? Or will i change openxcom on pc to openxcom extender?
Thanks in advance
You can transfer your saves from openxcom to openxcom extended without problems. From PC to Android.
But if you transfer saves from openxcom extended to openxcom (from Android to PC) you will lose some information.
I would recommend updating your PC to openxcom extended too... but the decision is yours.
-
You can transfer your saves from openxcom to openxcom extended without problems. From PC to Android.
But if you transfer saves from openxcom extended to openxcom (from Android to PC) you will lose some information.
I would recommend updating your PC to openxcom extended too... but the decision is yours.
Thanks a lot, I'll do that.
Another question, if I install oxce I will have to patch games manually or is like openxcom?
Thanks in advance
-
Thanks a lot, I'll do that.
Another question, if I install oxce I will have to patch games manually or is like openxcom?
Thanks in advance
It's the same like downloading openxcom nightly as zip.
-
Meridian, do I have to dig at myself in order to identify the problem of sounds, or will there be a bug fix in the next version of OXCE?
-
Meridian, do I have to dig at myself in order to identify the problem of sounds, or will there be a bug fix in the next version of OXCE?
I have not had a chance to look at it yet... I will try it today or tomorrow.
But if you can help, that would be nice.
-
I am not a programmer. But apparently there is an offset when playing a sound in the file "cat", in the folder "\ openxcom \ UFO \ sound". If you take the files "cat" from here https://openxcom.org/forum/index.php/topic,2727.msg28562.html#msg28562 , then the sound will be strange, although this is the way out. But there the file size is smaller than from my version of the UFO, and some sounds may not suffice (did not check completely).
It is possible, as an option, to integrate this mod https://openxcom.org/forum/index.php/topic,2044.msg19770.html#msg19770 into OXCE and forget about this problem.
-
It's the same like downloading openxcom nightly as zip.
Ok, i will patch ufo an tftd then.
Thanks!
-
I am not a programmer. But apparently there is an offset when playing a sound in the file "cat", in the folder "\ openxcom \ UFO \ sound". If you take the files "cat" from here https://openxcom.org/forum/index.php/topic,2727.msg28562.html#msg28562 , then the sound will be strange, although this is the way out. But there the file size is smaller than from my version of the UFO, and some sounds may not suffice (did not check completely).
It is possible, as an option, to integrate this mod https://openxcom.org/forum/index.php/topic,2044.msg19770.html#msg19770 into OXCE and forget about this problem.
I have reproduced the issue using your files, but I don't know how to fix it.
I have informed Stoddard (who was doing the recent changes), and waiting for his feedback.
-
Hi, I have another question. Where is cfg file?
It's for copy it to pc, phone and tablet, to have the same options.
Thanks in advance
-
Hi, I have another question. Where is cfg file?
It's for copy it to pc, phone and tablet, to have the same options.
Thanks in advance
%Documents%/OpenXcom/options.cfg
-
Something I can not understand - and in the display of the ship’s readiness status, does the "refuel \ repair Rate" count or is it a display of total readiness taking into account repair, reloading and refueling?
-
%Documents%/OpenXcom/options.cfg
Thanks!
-
Another question, how can i donate? I already donate 5€ to openxcom and i want to donate to OCXE developer too.
-
Something I can not understand - and in the display of the ship’s readiness status, does the "refuel \ repair Rate" count or is it a display of total readiness taking into account repair, reloading and refueling?
It's all of them added together, plus an additional hour many times, for reasons unknown to me. (rounding issues?) Each craft has exactly one thing done to it at a time, so each of the weapons gets rearmed individually.
-
It's all of them added together, plus an additional hour many times, for reasons unknown to me. (rounding issues?) Each craft has exactly one thing done to it at a time, so each of the weapons gets rearmed individually.
It's all together.
1 hour difference is caused by the fact that separate refuel/rearm/repair times are calculated rounded to whole hours up... but the actual actions are performed in 30 minute intervals; so something that takes 0.5+0.5+0.5 = 1.5 hours is shown as 1+1+1 = 3 hours (instead of 2 hours)
-
It's all of them added together, plus an additional hour many times, for reasons unknown to me. (rounding issues?) Each craft has exactly one thing done to it at a time, so each of the weapons gets rearmed individually.
It's all together.
1 hour difference is caused by the fact that separate refuel/rearm/repair times are calculated rounded to whole hours up... but the actual actions are performed in 30 minute intervals; so something that takes 0.5+0.5+0.5 = 1.5 hours is shown as 1+1+1 = 3 hours (instead of 2 hours)
Well, yes, plus the crew’s lunch time, a delay in sanitary need ... yes, yes, yes. :D All this is strange.
-
I'm following your playthrough of TWOTS at the moment and noticed that you have upgraded to OXCE 5.3.3 of 13/04/19 but, https://openxcom.org/forum/index.php/topic,5258.0.html shows 18/03/19 as the latest. Can you provide a link for the latest release or are you still testing it at the moment?
-
https://lxnt.wtf/oxem/#/Extended
-
https://lxnt.wtf/oxem/#/Extended
O_o No information, no list of changes ... Such top-secret information?
-
O_o No information, no list of changes ... Such top-secret information?
Changelog is produced on releases only, not on nightly builds.
And you can see the changelog in github or on discord if you want it sooner.
I also create a new thread for every new feature with examples here on the forum as soon as it is implemented or even sooner if I want feedback.
What more do you want?
-
Hi, i don´t know if it is a problem or not but when i load a game from my tablet (i play between android and pc versions) prompts a message that say i had activated mods and i will have problems. I play with same configuration in both platforms.
Can i play without risks?
Thanks in advance.
-
Hi, i don´t know if it is a problem or not but when i load a game from my tablet (i play between android and pc versions) prompts a message that say i had activated mods and i will have problems. I play with same configuration in both platforms.
Can i play without risks?
If it says that then you don't have the same configuration.
Try starting a new game on PC, make a save, start a new game on tablet, make a save, and upload both saves here... we'll tell you what's different.
-
If it says that then you don't have the same configuration.
Try starting a new game on PC, make a save, start a new game on tablet, make a save, and upload both saves here... we'll tell you what's different.
Thanks! I attached them.
-
Thanks! I attached them.
These two are same... are you getting the warning when you move one of them to the other platform?
-
These two are same... are you getting the warning when you move one of them to the other platform?
Yes, From pc to Android. From android to pc there is no warning
Edit: it's my fault, on tablet is ok. problem is on my phone. I will check configuration again
Sorry
-
New OXCE v5.4 is up.
2019-04-22
- Added ability to decide whether to kill or sell aliens in alien containment
- Added option to prevent or allow loading an item to craft inventory: see 'ignoreInCraftEquip' attribute in nightly ruleset reference (NRR)
- Training Finished popup now shows the base name too
- Show cause of death (killer & weapon) on diary overview
- Shift+click to swap loaded ammo
- Shift+click for instant unload
- Ctrl+Alt+j/k to stun/kill all aliens EXCEPT under the cursor
- Sort soldiers by name instead of just by first letter
- Skip zero-quantity craft/soldier types in Monthly Costs breakdown: see 'forceShowInMonthlyCosts' attribute in NRR
- Added "extraRandomItems" attribute to alien deployment: https://openxcom.org/forum/index.php/topic,7055.msg111746.html#msg111746
- Added "randomRace" attribute to alien deployment: https://openxcom.org/forum/index.php/topic,7065.msg111733.html#msg111733
- Manufacture/Purchase links from "Cannot Reequip" GUI
- Added mod option to build infiltration bases near countries: see 'buildInfiltrationBaseCloseToTheCountry' attribute in NRR
- Added a chance for environmental conditions being applied or not (per battle): see 'globalChance' attribute in NRR
- Global Production Overview (default hotkey 'P')
- Added craft weapon ruleset option to hide stat info in Ufopedia: see 'hidePediaInfo' attribute in NRR
- Added item ruleset option to hide damage info in Ufopedia: see 'hidePower' attribute in NRR
- Add multi page support for Ufopaedia articles: see 'pages' attribute in NRR
- Mission bounty item now supports item transformations
- Allowed other attack types (e.g. snap or auto) for launcher weapons
- TU recovery each turn is now additive (same as e.g. energy recovery), cannot go over maximum, encumberance/wound penalties are applied at the end
- Added random manufacturing summary GUI
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
NRR: Nightly ruleset reference (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
Nice!
Is the option of always be able to transfer the loot after battle (versus only when there is no more room), still on the to-do-some-day list ?
EDIT:
New OXCE v5.4 is up.
- Shift+click to swap loaded ammo
- Shift+click for instant unload
I can unload the ammo directly to the ground if Shift+click. What the other option does?
It appears there are many more keyboard shortcuts than those found in the Options Menu. Is there a page with all of the OXCE current controls available to the player ?
-
Thank you for the work and update.
-
EDIT:I can unload the ammo directly to the ground if Shift+click. What the other option does?
If you are holding an ammo in the hand already, you can use shift+click to swap that ammo with an already loaded ammo in the gun.
I.e. "ammo swap" instead of "unload + load"
It appears there are many more keyboard shortcuts than those found in the Options Menu. Is there a page with all of the OXCE current controls available to the player ?
https://openxcom.org/forum/index.php/topic,6424.0.html
If there is something missing, you're more than welcome to add it.
-
- TU recovery each turn is now additive (same as e.g. energy recovery), cannot go over maximum, encumberance/wound penalties are applied at the end
Wouldn't it be preferable for encumbrance/wound penalties to be applied before cumulating TUs, so a heavily over encumbered dog could build up enough TUs over several turns to drop the corpse in its backpack. (Not that such an issue happened to me :P ) Also have a minimum of 1 TU regenerated per turn.
-
Wouldn't it be preferable for encumbrance/wound penalties to be applied before cumulating TUs, so a heavily over encumbered dog could build up enough TUs over several turns to drop the corpse in its backpack. (Not that such an issue happened to me :P ) Also have a minimum of 1 TU regenerated per turn.
Not vanilla compatible... it would mean that there are never any penalties in vanilla.
-
This kind of penalty can be written using scripts - I recently re-wrote overweight penalties in the 40k mod to apply to energy instead of TUs.
-
This kind of penalty can be written using scripts - I recently re-wrote overweight penalties in the 40k mod to apply to energy instead of TUs.
That would require editing tags on every armour in the game, right?
-
No, not necessarily. I wrote a single, global script to handle this. Any exceptions can be made at the armor or item level, but the base mechanics didn't require extra script ruleset tags on every armor.
-
No, not necessarily. I wrote a single, global script to handle this. Any exceptions can be made at the armor or item level, but the base mechanics didn't require extra script ruleset tags on every armor.
That's way better than I expected!
Not going to run with this straight away or anything, but could you share this script? It sounds potentially relevant to any mod.
-
Thanks for your work! If I update to 5.4 could i play my 5.3.2 savegame without problems?
-
1 hour difference is caused by the fact that separate refuel/rearm/repair times are calculated rounded to whole hours up... but the actual actions are performed in 30 minute intervals; so something that takes 0.5+0.5+0.5 = 1.5 hours is shown as 1+1+1 = 3 hours (instead of 2 hours)
I'm talking about how every time the craft says X hours, X hours later it says it's 100% complete but still in-process. It seems to put the craft in ready status at the end of the first time slot for which nothing is done to it, and not at the beginning of that time slot. It works the same whether it's doing things on multiple parts of the craft or not--example, loading a weapon that takes 2 hours, it says it takes 2 hours and it properly fills ammo 4 times in that 2 hours, but the weapon will be full and the craft still says Rearming.
-
I'm talking about how every time the craft says X hours, X hours later it says it's 100% complete but still in-process. It seems to put the craft in ready status at the end of the first time slot for which nothing is done to it, and not at the beginning of that time slot. It works the same whether it's doing things on multiple parts of the craft or not--example, loading a weapon that takes 2 hours, it says it takes 2 hours and it properly fills ammo 4 times in that 2 hours, but the weapon will be full and the craft still says Rearming.
Sorry, I did not understand any of this.
Please provide a starting save, screenshot of each step and which number is correct and which is wrong.
-
You can do it in vanilla. Disable all mods and make a new game. Take the cannon off your first interceptor, then put it back on. It'll say rearming: 2 hours. After 1 hour the cannon has 100/200 rounds, and it says rearming: 1 hour. After 2 hours the cannon has 200/200 rounds and it says rearming: 1 hour.
- - - -
Can we have an option to increase the number of mind shields that a base facility may count as? For example:
facilities:
- type: STR_MIND_SHIELD
mindPower: 1
- type: STR_LARGE_MIND_SHIELD
size: 2
mindPower: 6
- type: STR_ADVANCED_MIND_SHIELD
mindPower: 2
-
You can do it in vanilla. Disable all mods and make a new game. Take the cannon off your first interceptor, then put it back on. It'll say rearming: 2 hours. After 1 hour the cannon has 100/200 rounds, and it says rearming: 1 hour. After 2 hours the cannon has 200/200 rounds and it says rearming: 1 hour.
OK, I will have a look.
Can we have an option to increase the number of mind shields that a base facility may count as? For example:
facilities:
- type: STR_MIND_SHIELD
mindPower: 1
- type: STR_LARGE_MIND_SHIELD
size: 2
mindPower: 5
- type: STR_ADVANCED_MIND_SHIELD
mindPower: 2
Yes, todolisted.
Also, FWIW, I am very glad that someone has also requirements like this.
I am pretty sick of (almost) all modders making me build 10 alien containments, 20 workshops, 30 labs and a gazillion of storage/living space facilities.
Making small compact efficient bases is beautiful.
-
Making small compact efficient bases is beautiful.
While we're at it, may I request a global variable to make grav shields stack?
vars:
gravStacking: true
It won't significantly increase base defense power in most setups, but may allow you to slightly reduce the number of facilities used. Such as: 1 grav shield and 5 fusion defense = 10x fusion defense for 6 facility space. But 2 grav shield and 3 fusion defense = 9x fusion defense for 5 facility space.
On the other hand, mods like Tech-Comm might implement using large fractions of your base for defense, and trying to calculate how many grav shields vs defenses gives you the best ratio.
-
Question about tech viewer: What all those "-,=,#" marks means, and how I can determine which project is easily or harder? If possible answer with some examples.
-
Very good question, I had been wondering about those symbols as well.
-
I noticed that only weapon-type craftWepons are shown on the interception window. Passive craftWeapons, such as one that grants extra speed, accuracy, and so on, are not.
Would it be possible to show them too (obviously omitting the range indicator, since they don't have any)? I think it would be useful, and especially more cool, to show them.
I guess this is sort of a selfish request, but I just finished a bunch of icons and seeing them not appear was disappointing :P.
-
I noticed that only weapon-type craftWepons are shown on the interception window. Passive craftWeapons, such as one that grants extra speed, accuracy, and so on, are not.
Would it be possible to show them too (obviously omitting the range indicator, since they don't have any)? I think it would be useful, and especially more cool, to show them.
I guess this is sort of a selfish request, but I just finished a bunch of icons and seeing them not appear was disappointing :P.
yes
-
After upgrading from a previous version i've noticed that terrain damage seems to be applied before the actual hit animation has played. Is this intended?
-
After upgrading from a previous version i've noticed that terrain damage seems to be applied before the actual hit animation has played. Is this intended?
From which version to which version?
-
5.3.0 to 5.4.1
-
Yeah, this seems to be the relevant change: https://github.com/MeridianOXC/OpenXcom/commit/73c9eb39d15af4e1a02600fdfd97b848c4292c4c
I forgot what the reason was, maybe Yankes can clarify.
-
Yes, this is intended, this is change made in propose of future changes and refactors.
Terrain is change because bullet physically hit at that moment, and after bullet hit/explosion animation will play.
-
Terrain is change because bullet physically hit at that moment, and after bullet hit/explosion animation will play.
It is thrue in theory, but explosives now looks strange. But if it needed, then it needed...
-
Doesn't this break vanilla behaviour/animation cycles?
As Nord has pointed out this looks extremely odd atm, since the terrain breaks before the projectile hit animation plays out.
Might i suggest moving this change into a seperate dev-branch until this has been sorted out? I'd like to use a version of OXCE that doesn't randomly crash, but right now i'd actually prefer the game to randomly crash instead of having precognitive terrain tiles.
With what version were these changes introduced?
-
Can we have option auto set timer after dog fight to 5 seconds automatically? Can we have option auto zoom out world map if USO could not be reached due to depth? Same if can not be reached under land. All questions consider TFTD. May be I missed something so I add it here later.
-
Can we have option auto set timer after dog fight to 5 seconds automatically?
The timer is already always set to 5 seconds when the dogfight starts.
Can we have option auto zoom out world map if USO could not be reached due to depth? Same if can not be reached under land. All questions consider TFTD. May be I missed something so I add it here later.
No, I am adding user options only if 100+ users ask for them. And I haven't heard such a request from anyone else.
-
Doesn't this break vanilla behaviour/animation cycles?
As Nord has pointed out this looks extremely odd atm, since the terrain breaks before the projectile hit animation plays out.
Might i suggest moving this change into a seperate dev-branch until this has been sorted out? I'd like to use a version of OXCE that doesn't randomly crash, but right now i'd actually prefer the game to randomly crash instead of having precognitive terrain tiles.
With what version were these changes introduced?
This is already sorted out, and tiles aren't precognitive because damage hit them at this moment. Overall gameplay behavior is exactly same as previously, only moment when animation is play was changed.
This change is important in long run, because damage calculation is done first now then it can affect how explosion will play out, that is impossible in old version.
Example could be that explosion animation is played in random places even if damage do not reach that place, in new version I could add that animations is show only where damage was done.
One thing I have in mind is do not update every tile at once during explosion. Instead do it by circualr "layer" that will simulate propagate of shock wave.
-
This is already sorted out, and tiles aren't precognitive because damage hit them at this moment. Overall gameplay behavior is exactly same as previously, only moment when animation is play was changed.
This change is important in long run, because damage calculation is done first now then it can affect how explosion will play out, that is impossible in old version.
Example could be that explosion animation is played in random places even if damage do not reach that place, in new version I could add that animations is show only where damage was done.
One thing I have in mind is do not update every tile at once during explosion. Instead do it by circualr "layer" that will simulate propagate of shock wave.
Excuse me, but this seems like a pretty important change as far as animation behaviour is concerned, in a mod that prides itself on keeping/preserving vanilla consistency. Going by this you could also do away with the shooting animation entirely and just show the results instead.
As far as i am concerned the tiles are 'precognitive', since the only inidication that any damage has been delat is when the hit animation plays - which is does after the terrain tile is already destroyed. Damage calculation in-game isn't transparent to the player. I'd ask you to reconsider and at least give us an option to enable vanilla behaviour (for animations).
Can you tell me when this change was introduced?
-
Can you tell me when this change was introduced?
It was introduced on March 17th.
-
Excuse me, but this seems like a pretty important change as far as animation behaviour is concerned, in a mod that prides itself on keeping/preserving vanilla consistency. Going by this you could also do away with the shooting animation entirely and just show the results instead.
This is priority of OXC not OXCE. When I start OXCE, my main goal was modding capacity of engine even when sacrificing original behavior.
See: https://openxcom.org/forum/index.php/topic,6459.0.html
If new behavior have similar (not same!) end effect and give more options for modder then I throw through the window original behavior.
And here we have exactly this case, changing order is very visible but end result is same. As it give lot of potential for new mod capabilities and code refactor that will simplify and allow future changes and new functionalities. And only thing left is personal taste and familiarity with old behavior.
For single hit animation current version look even better IMHO.
As far as i am concerned the tiles are 'precognitive', since the only inidication that any damage has been delat is when the hit animation plays - which is does after the terrain tile is already destroyed. Damage calculation in-game isn't transparent to the player. I'd ask you to reconsider and at least give us an option to enable vanilla behaviour (for animations).
People evaporate in nuclear strike before shock wave reach them.
Options to toggle it is out out question, because whole point of this change was to simplify game logic not add new cases and versions. Whole point is that I could really on this that calculation was done before all animations.
Only thing that could be done (as I said previous post) to alter how tiles are handled after damage calculations. That could allow delay update of tiles to some frames after hit, but this need more work and right now I have other priorities.
Right now you are only one I know who is very against this change, if there was more demand for changing it, from more people, then I could consider to alter current behavior. Other wise I leave this as is.
-
About moral damage, as reportet here:
https://openxcom.org/forum/index.php/topic,4058.msg112656.html#msg112656 (https://openxcom.org/forum/index.php/topic,4058.msg112656.html#msg112656)
Moral damage, as in weapons dealing damage to moral, is multiplied by: (110 - bravery)/100
This works fine as long as the maximum bravery is 100. Since mods introduced bravery adding armors, bravery 100+ is now possible. While immunity to moral damage at 110 bravery is debatable, damage inversion for bravery >110 is clearly a bug.
How to solve? Treat everything >110 bravery as 110 (immunity) or treat everything >100 as 100? Other options?
-
How to solve?
Solution 1: don't create such armors
Solution 2: don't create such weapons
Solution 3: use scripts to implement your own damage algorithm with whatever rules you can think of
-
About moral damage, as reportet here:
https://openxcom.org/forum/index.php/topic,4058.msg112656.html#msg112656 (https://openxcom.org/forum/index.php/topic,4058.msg112656.html#msg112656)
Moral damage, as in weapons dealing damage to moral, is multiplied by: (110 - bravery)/100
This works fine as long as the maximum bravery is 100. Since mods introduced bravery adding armors, bravery 100+ is now possible. While immunity to moral damage at 110 bravery is debatable, damage inversion for bravery >110 is clearly a bug.
How to solve? Treat everything >110 bravery as 110 (immunity) or treat everything >100 as 100? Other options?
I don't like the way bravery picks up slowly at first, but then accelerates until suddenly hitting the top. But there are some ways to work around it.
If you have weapons that deal morale damage based on bravery, then I would recommend being careful to not allow bravery to go above 110, and maybe make it very difficult to bring it above 100. Perhaps if your soldiers max out at 100, you could have a special expensive armor which grants 10 bravery. Or you could have regular soldiers max at 90 and special high-tech soldiers able to reach 100. If you allow the soldier natural max to get most of the way up, and put a high cost on adding any more bravery externally, then it's easier to manage.
Another thing you might be able to do (I assume it's possible) is to have it deal damage to morale based on its power value, or at least have a flat value added to the bravery-based morale damage. That way you can ignore the 110 bravery's natural fear immunity and be able to deal morale damage to units with much higher bravery values, as long as they don't have actual fear immunity.
-
Let's back to dogfight speed. I don't know is this a bug or not, but if you encounter USO under land and pursuit it with fast speed (1 minute or more) as soon as it going to water and dogfight phase begins, speed of your interceptor not drops down to 5 seconds when USO successfully drowned. Can not provide any save files, you have to check it manually.
-
In my opinion, not a bug.
Can be changed if enough people think it is a bug.
-
If Interceptor used to escort you friendly craft and got attacked on the way, it's loosing his escort target after dogfight is over and turning to base. Bug?
-
I don't like the way bravery picks up slowly at first, but then accelerates until suddenly hitting the top. But there are some ways to work around it.
If you have weapons that deal morale damage based on bravery, then I would recommend being careful to not allow bravery to go above 110, and maybe make it very difficult to bring it above 100. Perhaps if your soldiers max out at 100, you could have a special expensive armor which grants 10 bravery. Or you could have regular soldiers max at 90 and special high-tech soldiers able to reach 100. If you allow the soldier natural max to get most of the way up, and put a high cost on adding any more bravery externally, then it's easier to manage.
Another thing you might be able to do (I assume it's possible) is to have it deal damage to morale based on its power value, or at least have a flat value added to the bravery-based morale damage. That way you can ignore the 110 bravery's natural fear immunity and be able to deal morale damage to units with much higher bravery values, as long as they don't have actual fear immunity.
You missunderstand. Damage to morals, as in:
damageAlter:
ToMorale: 1.0
is multiplied by
(110 - bravery)/100
with bravery being the bravery stat of the target! Not the weapon holder!
That is why I reported it here as a bug. The "ToMorale" parameter of OXCE has this scaling right now, whether you want it or not.
Regarding:
"Solution 1: don't create such armors"
Why allow +bravery armors in the ruleset if that is you opinion?
"Solution 2: don't create such weapons"
Why allow "ToMorale" as an option in the "damageAlter" category, if that is your opinion? Any weapon that uses "ToMorale" displays the described behavior. I would say fix it or scrap it.
"Solution 3: use scripts to implement your own damage algorithm with whatever rules you can think of"
I don't want to create any weapons, I'm just reporting on a sign inversion bug using simple ruleset options of OXCE that are used alot in the Piratez mod.
-
If Interceptor used to escort you friendly craft and got attacked on the way, it's loosing his escort target after dogfight is over and turning to base. Bug?
No, not a bug.
-
Regarding:
"Solution 1: don't create such armors"
Why allow +bravery armors in the ruleset if that is you opinion?
"Solution 2: don't create such weapons"
Why allow "ToMorale" as an option in the "damageAlter" category, if that is your opinion? Any weapon that uses "ToMorale" displays the described behavior. I would say fix it or scrap it.
"Solution 3: use scripts to implement your own damage algorithm with whatever rules you can think of"
I don't want to create any weapons, I'm just reporting on a sign inversion bug using simple ruleset options of OXCE that are used alot in the Piratez mod.
1/ I did not allow +bravery armors. Also, it's not my opinion, it's just a possible option.
2/ I have also not implemented ToMorale option. Again, it's not my opinion, just giving you options.
3/ I didn't say you need to create any weapons, I just said you can change the damage algorithm (even for all weapons at once)
Anyway, there are a million things you can change in the ruleset to break the game.
I cannot fix them all, the only way to fix them all is to remove modding capability completely.
Modders always try to change more and more... until it breaks; there's absolutely no way for me to stop that from happening.
And making it even more moddable, doesn't solve the problem, just adds more ways how to break the game.
Yankes has listened to your needs for changing everything imaginable around damage calculation and has given you a tool to do that (scripts).
If you want to change how the morale damage works, you can!
The "ToMorale" parameter of OXCE has this scaling right now, whether you want it or not.
Not true.
If you don't want it, you can already today script your own damage algorithm.
--
If you have a concrete solution for this "bug", please tell us. And ask all modders if I can change it too.
Until then I consider this a feature, not a bug.
-
For the record, I have no objections to changing this. I'm neutral.
-
I already gave two solutions. Just limit bravery in the damage multiplier to 100 or 110. It's 100% vanilla compatible as vanilla does not allow bravery over 100 anyway.
It's a simple overflow bug where modding has enabled a variable to have higher values than vanilla intended. Same as if you mod in a weapon dealing 1000 damage and it suddenly heals and not kills.
-
Monthly report, text out of screen, scroll bar in future releases may be?
(https://i.postimg.cc/NLk2d871/screen017.png) (https://postimg.cc/NLk2d871)
-
Monthly report, text out of screen, scroll bar in future releases may be?
(https://i.postimg.cc/NLk2d871/screen017.png) (https://postimg.cc/NLk2d871)
Unfortunately, I cannot add a scrollbar there, sorry.
But I agree with you, it's a bug.
-
Playing Reaver's megamod on 5.4.1, one of my bases (Turquino) has a live alien listed in the storage even though I don't have an alien containment facility for that base. Can't tell when that alien got there.
(https://i.postimg.cc/DJcK0QSB/screen028.png) (https://postimg.cc/DJcK0QSB)
-
Let's back to dogfight speed. I don't know is this a bug or not, but if you encounter USO under land and pursuit it with fast speed (1 minute or more) as soon as it going to water and dogfight phase begins, speed of your interceptor not drops down to 5 seconds when USO successfully drowned. Can not provide any save files, you have to check it manually.
Changed.
I already gave two solutions. Just limit bravery in the damage multiplier to 100 or 110. It's 100% vanilla compatible as vanilla does not allow bravery over 100 anyway.
It's a simple overflow bug where modding has enabled a variable to have higher values than vanilla intended. Same as if you mod in a weapon dealing 1000 damage and it suddenly heals and not kills.
Feature removed.
Playing Reaver's megamod on 5.4.1, one of my bases (Turquino) has a live alien listed in the storage even though I don't have an alien containment facility for that base. Can't tell when that alien got there.
I don't see how I can help here.
Maybe report to Reaver?
-
How the dept warning system working? Last month I got no warning as usual and went to minus more than 1 mil. I quickly sold some staff and fixed my balance, but why no waning this time? Assume what this happened because I spend some money at last day of month below warning threshold?
-
Playing Reaver's megamod on 5.4.1
Always report to the mod before reporting to the base game. Also, my Faithful megamod is vanilla.
I'll take a look into it but please post about it in my mod page:
[UFO MEGAMOD] Reaver's Faithful Megamod (https://openxcom.org/forum/index.php/topic,5543.90.html)
-
New OXCE v5.5 is up.
2019-05-19
- Deselect all hotkey (default X) in Psi/Martial Training GUIs
- Remember mission target and craft/base even after the briefing
- Added "Highlight new topics" user option
- Bravery now can't decrease morale change below zero percent
- Required base services in "We can now..." GUIs
- Starting conditions: allowed/forbidden soldier types
- Starting conditions: forbidden items and item categories
- Starting conditions: forbidden vehicles support
- Starting conditions: forbidden armors support
- Starting conditions: forbidden craft support
- BREAKING CHANGE: split Starting conditions (into Starting Conditions and Enviro Effects): https://openxcom.org/forum/index.php/topic,4444.msg113226.html#msg113226
- Fixed dogfight for HKs with extremely short range
- Manufacture dependency tree now shows also base facilities
- Added optional research requirement for armor equip, see 'requires' armor attribute in NRR
- New attribute for mind shield power, see 'mindPower' facility attribute in NRR
- User option to remember disabled craft weapons after dogfight (+no rearm)
- Draw dogfight icons also for craft equipment
- Improved pedia articles for tractor beams
- Extra NV button for Android
- Removed the facility teleport cheat
- Updated kill/sell button logic in alien containment
- Added arc script: https://openxcom.org/forum/index.php/topic,7125.0.html
- Updated OXC and OXCE language files
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
NRR: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
So morale damage is no longer inversed when above BRA 110? Not a big thing, but, EDDIE, why? Why did you do that to me? Why do you hate me? (We both know that only Piratez use >110 BRA) I just only learned about it now.
-
- Draw dogfight icons also for craft equipment
Yay!
-
So morale damage is no longer inversed when above BRA 110? Not a big thing, but, EDDIE, why? Why did you do that to me? Why do you hate me? (We both know that only Piratez use >110 BRA) I just only learned about it now.
https://xkcd.com/1172/ (https://xkcd.com/1172/)
I think bravery damage inversion is far more likely to be problematic than useful. And more importantly, it seems reasonable to ask for the use as a separate feature: a feature in which it's possible to declare a state that causes some units to have morale restored under certain conditions. Maybe the end result will give you MORE control than you ever had before.
I support the change. It doesn't currently affect my mod either way, but if it ever did it'd be negatively.
P.S.: My upcoming mod has >110 BRA.
- - - - - - - - - -
Meridian:
Thank you so much for everything you do! I could never repay you for all your work, so the best I can do instead is show the value of your work by using it to better my mod. The following suggestion is merely tossing ideas against the wall. I put you under no pressure to set any of it into action. Feel free to ignore anything I say here.
Here's some suggestions to perhaps cover for Dioxine's needs while also opening up an entire new angle to modding involving morale management. Should you pursue this suggestion, you can expect to see more people finding more ways to break their mods. It's a labor of love, and every time someone asks for a new feature to get out of a corner they drove themselves into, it's a way of saying "I love all these options and it inspires my creativity!".
.
A.) Add a damageAlter which deals (or heals) damage to morale, and can be based on a resistance. If the resistance number declared is -1, then it uses bravery as we understand (including healing for bravery 120+). If it's 0, then it deals the morale change regardless of other considerations. It should allow for negative numbers on the effect value, so you can make something that heals morale to anyone (even lily-livered), or you could even make something that heals MORE morale the LESS brave the soldier is.
B.) Add an option for medi-kits to make the pain killer option heal morale damage that wasn't caused by injury.
painKillerType:
0 = vanilla (only heals morale lost by injury
1 = only heals morale lost by psi/use/item effects
2 = only heals morale lost by friendly deaths
3 = 0&1
4 = 0&2
5 = 1&2
6 = all three (always heals morale)
-
About scrollbar on month report screen, if it possible here:
(https://i.postimg.cc/RWSh0dtL/screen029.png) (https://postimg.cc/RWSh0dtL)
why it's not possible there? Breaks too much code of original project? Sorry for being stubborn. Just wondering.
-
The listbox component supports scrollbar, the textbox component doesn't.
-
Not sure what this right forum but since I'm using OXCE asking here: is it possible to add stun, wounded and other marks to 2x2 enemies like Hallucinoids? Or this is already present? May be I just missing it with my guns, so no damage signs?
-
Not sure what this right forum but since I'm using OXCE asking here: is it possible to add stun, wounded and other marks to 2x2 enemies like Hallucinoids? Or this is already present? May be I just missing it with my guns, so no damage signs?
-
Got it. Sir! It seems my weapons or missing or not produce fatal wounds.
-
Got it. Sir! It seems my weapons or missing or not produce fatal wounds.
Hallucinoids are immune to fatal wounds as far as I know.
-
Could you make a tweak to the ToItem attribute on damageAlter? Currently, it goes through items one at a time, damaging it until it destroys that item. I can't see a good way to use this functionality. It randomly destroys an almost-fixed number of items, regardless of how many items are on the unit(s) hit by the attack.
I propose that ToItem causes all items held by the attacked unit(s) to be hit the same as if they were on the ground. This means, for example, that a ToItem value of 1.0 on an explosive would destroy items held by units just as though they were laying on the ground.
If the current functionality of ToItem is worth maintaining, then I propose a new value: ToAllItems
-
How to block ability enter aliens to the ship? My people wiped out due to reaction fire. I know what I can nullify time units, but at Vanilla they can't enter it. Any scripts or options to disable it?
-
Could you make a tweak to the ToItem attribute on damageAlter? Currently, it goes through items one at a time, damaging it until it destroys that item. I can't see a good way to use this functionality. It randomly destroys an almost-fixed number of items, regardless of how many items are on the unit(s) hit by the attack.
I propose that ToItem causes all items held by the attacked unit(s) to be hit the same as if they were on the ground. This means, for example, that a ToItem value of 1.0 on an explosive would destroy items held by units just as though they were laying on the ground.
If the current functionality of ToItem is worth maintaining, then I propose a new value: ToAllItems
First changing this will affect vanilla behavior, you need have good reason to do this.
Second, same logic is used to items in inventory as items on ground, only difference is that items and unit in inventory get damage from overkill of target unit.
Third, current behavior of item damage is bad, its do only one check for item armor value and if damage is bigger then item is destroyed.
-
I already gave two solutions. Just limit bravery in the damage multiplier to 100 or 110. It's 100% vanilla compatible as vanilla does not allow bravery over 100 anyway.
It's a simple overflow bug where modding has enabled a variable to have higher values than vanilla intended. Same as if you mod in a weapon dealing 1000 damage and it suddenly heals and not kills.
Feature removed.
So morale damage is no longer inversed when above BRA 110? Not a big thing, but, EDDIE, why? Why did you do that to me? Why do you hate me? (We both know that only Piratez use >110 BRA) I just only learned about it now.
Feature added back in.
As far as I know Piratez is the only mod using bravery > 110 and Dioxine explicitly asked (yesterday) for this feature to be returned to the way it was before.
-
Assigned for Martial training aquanauts lose it if Triton was destroyed and they had arrived back to the base.
-
Assigned for Martial training aquanauts lose it if Triton was destroyed and they had arrived back to the base.
Yes.
-
I encountered odd behaviour with The X-COM Files mod. When all non-stunned enemies want to surrender, but some who don't are on the verge of waking up, my turn ends automatically, but the mission doesn't end and enemies get their turn. The savegame and full description are here:
https://openxcom.org/forum/index.php/topic,5047.msg113748.html#msg113748
https://openxcom.org/forum/index.php/topic,5047.msg113759.html#msg113759
Engine bug?
Latest release of the mod (0.9.9c), engine from Extended-5.5-537067a0c-2019-05-30-bionic-x86_64.7z. For some reason Extended-5.5.1-723854c2a-2019-06-12-bionic-x86_64.7z refuses to work, gives errors like
"Error for 'STR_MAGMA_CHAINSAWBOT_WEAPON': offset '-3' have incorrect value in set 'BIGOBS.PCK' "
-
I encountered odd behaviour with The X-COM Files mod. When all non-stunned enemies want to surrender, but some who don't are on the verge of waking up, my turn ends automatically, but the mission doesn't end and enemies get their turn. The savegame and full description are here:
https://openxcom.org/forum/index.php/topic,5047.msg113748.html#msg113748
https://openxcom.org/forum/index.php/topic,5047.msg113759.html#msg113759
Engine bug?
More an incompatibility of user option than a bug... but yeah it's an oxce issue, not xcf issue.
Latest release of the mod (0.9.9c), engine from Extended-5.5-537067a0c-2019-05-30-bionic-x86_64.7z. For some reason Extended-5.5.1-723854c2a-2019-06-12-bionic-x86_64.7z refuses to work, gives errors like
"Error for 'STR_MAGMA_CHAINSAWBOT_WEAPON': offset '-3' have incorrect value in set 'BIGOBS.PCK' "
https://openxcom.org/forum/index.php/topic,3287.msg113764.html#msg113764
-
In the "monthly cost" page at "flying sub rental" and "salaries" complete lists of all types that might or might not become usable in this game are shown.
Is there a trick or option, to only show up discovered (buyable/producable/usable/discovered or something like that) types?
(I would like to split the game using "arcScripts" and "randomArcs" into different arcs, where the types of the not active other arcs will never be seen. So it would be useless to see tons of variations of a ship if only one will be usable ever.)
-
In the "monthly cost" page at "flying sub rental" and "salaries" complete lists of all types that might or might not become usable in this game are shown.
Since OXCE 5.4 it is not: https://openxcom.org/forum/index.php/topic,6586.msg112262.html#msg112262
Is there a trick or option, to only show up discovered (buyable/producable/usable/discovered or something like that) types?
- Skip zero-quantity craft/soldier types in Monthly Costs breakdown: see 'forceShowInMonthlyCosts' attribute in NRR
-
Asking it's here, because I think it's more engine based than mod scripts. Question about damage and ranks - I've found what new soldiers (aquanauts) often not killing enemy in one shot what usually dies of it if someone more experienced shoot them. Same for throwing grenades. So question - why it happens and what determine damage - current stats of soldier (aquanaut) or her/his rank? Thanks for patience and apologizes if that question has been already answered.
-
Asking it's here, because I think it's more engine based than mod scripts. Question about damage and ranks - I've found what new soldiers (aquanauts) often not killing enemy in one shot what usually dies of it if someone more experienced shoot them. Same for throwing grenades. So question - why it happens and what determine damage - current stats of soldier (aquanaut) or her/his rank? Thanks for patience and apologizes if that question has been already answered.
Both current stats and rank can determine damage.
But as far as I know the only mod using rank to determine damage is Piratez (and only for a very few weapons)... everything else uses only soldier stats.
-
Question about damage and ranks - I've found what new soldiers (aquanauts) often not killing enemy in one shot what usually dies of it if someone more experienced shoot them. Same for throwing grenades.
It's a variety of subtle factors you may not be noticing, plus some apophenia. Maybe your less experienced soldiers are up toward the front and more likely to get the first shot. Maybe your more experienced soldiers carry better weapons. Maybe aliens are less likely to survive a hit gradually as the game progresses--your soldiers become more experienced but also get better weapons. Maybe you get better at using the same weapons, because you the player are more experienced and know what kills them. As for grenades and other explosives, it's probably the same, but hitting a square closer to the target counts for more damage (usually 10 more).
I've actually experienced the converse: as I research better armors, my rookies seem to become more powerful in combat. It's probably just that they can hold the line better, and it's definitely not them doing more damage.
-
Without trying to say something bad about the game or about the players: I haven't seen a game, which would spawn more myths about its mechanics than Xcom.
-
So, I'm not too sure what's going on with this, but after installing everything, both including and excluding TFTD, I'm getting this error.
(https://i.imgur.com/h5gXuiK.png)
TFTD:
(https://i.imgur.com/bU1Gytw.png)
Base:
(https://i.imgur.com/knyOoVz.png)
-
It says you are missing file UFO/UFOGRAPH/SPICONS.DAT
Can you check if this file exists?
-
Without trying to say something bad about the game or about the players: I haven't seen a game, which would spawn more myths about its mechanics than Xcom.
No kidding. I recently came across my old pro-tips forum post and was appalled to see just how inaccurate it was. And I was a veteran player of several years when I posted that. Modding has really helped me to understand the game in a way that playing it could never teach me.
X-Com Pro-tips! (https://openxcom.org/forum/index.php?topic=2939.0)
-
It says you are missing file UFO/UFOGRAPH/SPICONS.DAT
Can you check if this file exists?
That would be in the original? I can check. If not, can I snag the one from tftd, or are they different?
-
Yes it is from the original.
And they are different in UFO and TFTD.
-
Yes it is from the original.
And they are different in UFO and TFTD.
Thank you. That got me going.
-
Playing XPirateZ, spotted strange bug: flares, when thrown and missed, sometimes vanish in nowhere.
-
Playing XPirateZ, spotted strange bug: flares, when thrown and missed, sometimes vanish in nowhere.
It's a feature, some just fail to ignite.
-
It's a feature, some just fail to ignite.
I honestly can't tell if you're being serious.
-
It's a feature, some just fail to ignite.
Ah. I understand. Unclear ufopedia description though.
In fact, great idea.
-
I honestly can't tell if you're being serious.
He's serious.
The feature though is completely redundant/irrelevant IMO, feels like it's done only because it can be done, no other reason.
But maybe it's just me...
-
He's serious.
The feature though is completely redundant/irrelevant IMO, feels like it's done only because it can be done, no other reason.
But maybe it's just me...
Is this about the throwExplode/specialChance triggers?
-
He's serious.
The feature though is completely redundant/irrelevant IMO, feels like it's done only because it can be done, no other reason.
But maybe it's just me...
While it has no meaning in the terms of gammeplay (maybe aside of "not again!" screams) dont forget about immersion in the world of piratez, with all that rusty spaceships and sabres&blasters.
-
When route is plotted for a kneeling operative, TUs to kneel again are not shown. If this bug was reported previously, I haven't found it.
Example. A kneeling operative has 60 TUs, aimed shot takes 42 TUs, kneeling takes 4 TUs. Buttons are pressed to reserved TUs for kneeling and aimed shot. In the plotted straight route 2 steps are shown green — with 48 (correct) and 44 (incorrect) TUs left. If I try to walk him along this route, he stops at 48, and 44 is shown as yellow (correct).
Observed on OXCE builds 5.5.1-d20b54d00 from June 14 and 5.5.2-ccf1eee4a from June 23.
-
Has this changed from previous version or is it something completely new that you would like to have?
-
Never paid attention, frankly. I checked some old versions. So far:
5.1 from 2018-10-14 behaves the same;
OXCE+ 3.10 from 2018-06-20 behaves the same;
OXC from 2018-01-05 and 2019-07-03 behave the same.
I won't be able to compile and test anything older until tomorrow (much later, more likely), but it's clearly has been that way for years. When a unit is kneeling, the "reserve time units for kneeling" button doesn't affect the displayed route.
It's clearly an incorrect behaviour, which hasn't bothered people much.
-
I had trouble understanding this at fist, on account of the "TUs to kneel again are not shown"-part, since TUs "shown" don't take into account reserved actions. The TU count displayed simply reflects the TUs you've left when you reach that square.
The problem is that route colouration doesn't take into account the fact that you've reserved TUs for kneeling when you start out in that position. It's like the game assumes that since you start out in that stance you'll stay kneeling for the whole path, hence not taking the additional 4 TUs into account. This sounds like a bug to me, since the coloration doesn't match the reserved actions. Or is the colouration only supposed to reflect reserved shots?
-
Or is the colouration only supposed to reflect reserved shots?
I don't know.
It's not like we have a specification for that, it's not vanilla.
-
I don't know.
It's not like we have a specification for that, it's not vanilla.
Yeah, but somebody designed and implemented that mechanic. Was the idea behind that mechanic to not take into account kneeling costs when you start out kneeling? Was it supposed to only apply to reserved shots? Because it's not a bug if it's working as intended.
-
According to ufopedia it just accounts for being able to move and fire.
Never actually seen anyone use those buttons, especially kneeling one.
-
According to ufopedia it just accounts for being able to move and fire.
Display path taken with colored arrows: green - can move and fire; yellow - can move; red - cannot move.
Move and fire it is, apparently. Says nothing about kneeling.
Never actually seen anyone use those buttons, especially kneeling one.
How many people have you watched, actually?
-
I've seen it... But I doubt more than 5% of players actually use them. It's probably still too generous. ;)
-
I stooped using it like four years ago. But before, I used them a lot.
-
I see it with beginners quite a lot.
For experienced players, I strongly recommend not using any TU reserve, both kneel and shoot. You can do better on your own.
-
Or is the colouration only supposed to reflect reserved shots?
It does reflect TUs reserved for kneeling when the operative is standing.
I don't know.
It's not like we have a specification for that, it's not vanilla.
Recent vanilla behaves exactly the same.
And I use kneeling reserve constantly — to look around.
-
Recent vanilla behaves exactly the same.
OpenXcom is not vanilla :)
I meant original from 1994.
-
I was under the impression that most people, especially veterans, used the TU reserve buttons. I use them frequently, usually to move several soldiers quickly without overspending their TUs. It's a great timesaver at times, but sometimes I turn it off because the amount I want to reserve isn't an available option.
While we're on the subject of the movement and indicators, I have noticed another bug quite a few times: When a soldier with 8-11 time units tries to walk through a closed door, they open the door (spending 4 time units) and then stop, giving you the error that they do not have enough time units to proceed. You have to issue the order a second time to get them through the door. I suspect that what's happening is the game deducts the 4 TUs for opening the door without going through it, then incorrectly tests for 8 time units remaining for going through a closed door. It may be failing to update the door's status on the time unit checker.
He's serious.
The feature though is completely redundant/irrelevant IMO, feels like it's done only because it can be done, no other reason.
But maybe it's just me...
That's X-Piratez's features in a nutshell. The mod uses features because they are available. I like it, because it's a one-stop shop for modding examples. X-Piratez plus the ruleset reference (fantastic work on the OXCE documentation btw) will get you enough info to type up almost any mod features short of scripts.
-
I was under the impression that most people, especially veterans, used the TU reserve buttons. I use them frequently, usually to move several soldiers quickly without overspending their TUs. It's a great timesaver at times, but sometimes I turn it off because the amount I want to reserve isn't an available option.
I would probably use them a lot more often if it wasn't for OCX's route indicators. Sure beats having to remember the exact TU costs for every type of terrain in the game, for both vanilla jogging and OCX sprinting and strafing. Also misclicks. Misclicks are the work of T'Leth.
While we're on the subject of the movement and indicators, I have noticed another bug quite a few times: When a soldier with 8-11 time units tries to walk through a closed door, they open the door (spending 4 time units) and then stop, giving you the error that they do not have enough time units to proceed. You have to issue the order a second time to get them through the door. I suspect that what's happening is the game deducts the 4 TUs for opening the door without going through it, then incorrectly tests for 8 time units remaining for going through a closed door. It may be failing to update the door's status on the time unit checker.
The route indicators aren't perfect, you usually still do have to eyeball things like getting up from a crouch and opening automatic doors. (Countless rookies have been spared horrible death from tactical suicide by the humble right click-to-strafe combo emulating real life breaching techniques.) Guess it's just like vanilla, given how you always had to factor in TU costs for turning when reserving for shots. It would make sense that the route indicator's displayed cost is what the game internally uses for checking if you have enough TUs to keep moving, as opposed to how many TUs you currently actually have.
-
Hi Meridian! Could you move the mod menu like in Nightlies? Thanks :)
-
Hi Meridian! Could you move the mod menu like in Nightlies? Thanks :)
Why?
-
Why?
so it is more convenient, options separately, mods separately. But it's your choice of course.
-
Thx Meridian :)
-
New OXCE v5.6.1 is up.
2019-08-03
- Fixed mod loading order / corrupted options.cfg
* if you have OXCE from between 2019-01-27 and 2019-08-02 it is highly recommended to upgrade
* or at least check your options.cfg and make sure master mods (xcom1, xcom2, piratez, etc.) are on the top of the mod list
- Spawn less aliens in base defense when UFO is damaged: https://openxcom.org/forum/index.php/topic,7150.0.html
- Added new mana resource: https://openxcom.org/forum/index.php/topic,7241.0.html
- Ability to destroy alien bases by research (once daily)
- Ability to interrupt alien missions by research (once daily or after a mission): https://openxcom.org/forum/index.php/topic,7230.0.html
- Refactor of vertical levels map generation and alternate terrain handling (by ohartenstein)
- CTRL toggles No/Patrol button in ConfirmLanding UI
- BREAKING CHANGE: negative sprite indices are now officially not supported
* but you can now access sprites and sounds from other mods
- Increased max number of avatars from 128 to 512
- Some TechTreeViewer improvements
- Revert "Bravery now can't decrease morale change below zero percent"
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html
-
Thanks for new version !
But big pb ! :-[
v5.6.1
TFTD
Nota ;
C:\_GAMES\OpenXcom_Ex\standard\xcom2\Resources\UI\globe_tftd.png exist !
902 octets - 27x3
New Game... create first base... named first base... ok... Boom !
[04-08-2019_20-08-04] [INFO] OpenXcom Version: Extended 5.6.1 (v2019-08-03)
[04-08-2019_20-08-04] [INFO] Platform: Windows 64 bit
[04-08-2019_20-08-04] [INFO] Data folder is:
[04-08-2019_20-08-04] [INFO] Data search is:
[04-08-2019_20-08-04] [INFO] - C:/Users/Gabriel/Documents/OpenXcom/
[04-08-2019_20-08-04] [INFO] - C:/_GAMES/OpenXcom_Ex/
[04-08-2019_20-08-04] [INFO] User folder is: C:/_GAMES/OpenXcom_Ex/user/
[04-08-2019_20-08-04] [INFO] Config folder is: C:/_GAMES/OpenXcom_Ex/user/
[04-08-2019_20-08-04] [INFO] Options loaded successfully.
[04-08-2019_20-08-04] [INFO] SDL initialized successfully.
[04-08-2019_20-08-04] [INFO] SDL_mixer initialized successfully.
[04-08-2019_20-08-04] [INFO] Attempted locale:
[04-08-2019_20-08-05] [INFO] Detected locale: C
[04-08-2019_20-08-05] [INFO] Attempting to set display to 1600x900x32...
[04-08-2019_20-08-05] [INFO] Display set to 1600x900x32.
[04-08-2019_20-08-05] [INFO] Loading data...
[04-08-2019_20-08-05] [INFO] Scanning standard mods in ''...
[04-08-2019_20-08-05] [INFO] Scanning user mods in 'C:/_GAMES/OpenXcom_Ex/user/'...
[04-08-2019_20-08-05] [INFO] Active mods:
[04-08-2019_20-08-05] [INFO] - xcom2 v1.0
[04-08-2019_20-08-05] [INFO] - centre_entrainement_TFTD v1.0
[04-08-2019_20-08-05] [INFO] - Angel_interceptor v1.0
[04-08-2019_20-08-05] [INFO] - Moray_interceptor v1.01m
[04-08-2019_20-08-05] [INFO] - extra_pockets_TFTD v1.0
[04-08-2019_20-08-05] [INFO] - gauss_sniper_grenade v1.0m
[04-08-2019_20-08-05] [INFO] - new_flare_zrbite v1.0
[04-08-2019_20-08-05] [INFO] - scouts-drones v1.0
[04-08-2019_20-08-05] [INFO] - tenue_plongee v1.0m
[04-08-2019_20-08-05] [INFO] - Medailles_TFTD v2.2
[04-08-2019_20-08-05] [INFO] - static-smoke-tftd v1.0
[04-08-2019_20-08-05] [INFO] - UFOextender_Psionic_Line_Of_Fire_TFTD v1.0
[04-08-2019_20-08-05] [INFO] - Aliens_Pick_Up_Weapons_TFTD v1.0
[04-08-2019_20-08-05] [INFO] - Advanced_Medical_TFTD v2.0m
[04-08-2019_20-08-05] [INFO] - New_Torpedos_TFTD v1.0m
[04-08-2019_20-08-05] [INFO] - Knife_Weapon_TFTD v1.0
[04-08-2019_20-08-05] [INFO] - extra_explosions v1.0
[04-08-2019_20-08-05] [INFO] - Craft_Info_Armor v1.0
[04-08-2019_20-08-05] [INFO] - Sonic_Sniper_Weapon_TFTD v1.0
[04-08-2019_20-08-06] [INFO] Loading rulesets...
[04-08-2019_20-08-21] [INFO] Loading fonts... Font.dat
[04-08-2019_20-08-21] [INFO] Lazy loading: 1
[04-08-2019_20-08-21] [INFO] Loading custom palettes from ruleset...
[04-08-2019_20-08-21] [INFO] Making palette backups...
[04-08-2019_20-08-22] [INFO] Data loaded successfully.
[04-08-2019_20-08-22] [INFO] Loading language...
[04-08-2019_20-08-22] [INFO] Language loaded successfully.
[04-08-2019_20-08-22] [INFO] OpenXcom started successfully!
[04-08-2019_20-08-24] [INFO] Scanning standard mods in ''...
[04-08-2019_20-08-24] [INFO] Scanning user mods in 'C:/_GAMES/OpenXcom_Ex/user/'...
[04-08-2019_20-08-41] [INFO] SDL_mixer initialized successfully.
[04-08-2019_20-08-41] [INFO] Loading data...
[04-08-2019_20-08-41] [INFO] Scanning standard mods in ''...
[04-08-2019_20-08-41] [INFO] Scanning user mods in 'C:/_GAMES/OpenXcom_Ex/user/'...
[04-08-2019_20-08-41] [INFO] Active mods:
[04-08-2019_20-08-41] [INFO] - xcom2 v1.0
[04-08-2019_20-08-41] [INFO] - centre_entrainement_TFTD v1.0
[04-08-2019_20-08-41] [INFO] - Angel_interceptor v1.0
[04-08-2019_20-08-41] [INFO] - Moray_interceptor v1.01m
[04-08-2019_20-08-41] [INFO] - extra_pockets_TFTD v1.0
[04-08-2019_20-08-41] [INFO] - gauss_sniper_grenade v1.0m
[04-08-2019_20-08-41] [INFO] - new_flare_zrbite v1.0
[04-08-2019_20-08-41] [INFO] - scouts-drones v1.0
[04-08-2019_20-08-41] [INFO] - tenue_plongee v1.0m
[04-08-2019_20-08-41] [INFO] - Medailles_TFTD v2.2
[04-08-2019_20-08-41] [INFO] - static-smoke-tftd v1.0
[04-08-2019_20-08-41] [INFO] - UFOextender_Psionic_Line_Of_Fire_TFTD v1.0
[04-08-2019_20-08-41] [INFO] - Aliens_Pick_Up_Weapons_TFTD v1.0
[04-08-2019_20-08-41] [INFO] - Advanced_Medical_TFTD v2.0m
[04-08-2019_20-08-41] [INFO] - New_Torpedos_TFTD v1.0m
[04-08-2019_20-08-41] [INFO] - Knife_Weapon_TFTD v1.0
[04-08-2019_20-08-41] [INFO] - extra_explosions v1.0
[04-08-2019_20-08-41] [INFO] - Craft_Info_Armor v1.0
[04-08-2019_20-08-41] [INFO] - Sonic_Sniper_Weapon_TFTD v1.0
[04-08-2019_20-08-41] [INFO] - XcomUtil_Statstrings_TFTD v1.0
[04-08-2019_20-08-42] [INFO] Loading rulesets...
[04-08-2019_20-08-58] [INFO] Loading fonts... Font.dat
[04-08-2019_20-08-59] [INFO] Lazy loading: 1
[04-08-2019_20-08-59] [INFO] Loading custom palettes from ruleset...
[04-08-2019_20-08-59] [INFO] Making palette backups...
[04-08-2019_20-08-59] [INFO] Data loaded successfully.
[04-08-2019_20-08-59] [INFO] Loading language...
[04-08-2019_20-08-59] [INFO] Language loaded successfully.
[04-08-2019_20-08-59] [INFO] OpenXcom started successfully!
[04-08-2019_20-09-02] [INFO] Scanning standard mods in ''...
[04-08-2019_20-09-02] [INFO] Scanning user mods in 'C:/_GAMES/OpenXcom_Ex/user/'...
[04-08-2019_20-09-13] [FATAL] FileRecord::at(Resources/UI/globe_tftd.png): requested file not found.
[04-08-2019_20-09-13] [ERROR] FileRecord::at(Resources/UI/globe_tftd.png): requested file not found.
[04-08-2019_20-09-58] [FATAL] A fatal error has occurred: Segmentation fault.
[04-08-2019_20-09-58] [FATAL] 0x585960 OpenXcom::CrossPlatform::stackTrace(void*)
[04-08-2019_20-09-58] [FATAL] 0x586ce0 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[04-08-2019_20-09-58] [FATAL] 0x41c850 signalLogger(int)
[04-08-2019_20-09-58] [FATAL] 0x918850 OpenXcom::UfopaediaStartState::think()
[04-08-2019_20-09-58] [FATAL] 0x7ffc5ec5b550 _C_specific_handler
[04-08-2019_20-09-58] [FATAL] 0x7ffc5ec6f6c0 _chkstk
[04-08-2019_20-09-58] [FATAL] 0x7ffc5ebdc460 RtlWalkFrameChain
[04-08-2019_20-09-58] [FATAL] 0x7ffc5ec6e6e0 KiUserExceptionDispatcher
[04-08-2019_20-09-58] [FATAL] 0x69b5c0 OpenXcom::Globe::polarToCart(double, double, short*, short*) const
[04-08-2019_20-09-58] [FATAL] 0x69fd90 OpenXcom::Globe::drawMarkers()
[04-08-2019_20-09-58] [FATAL] 0x65d9a0 OpenXcom::Timer::think(OpenXcom::State*, OpenXcom::Surface*)
[04-08-2019_20-09-58] [FATAL] 0x69b3f0 OpenXcom::Globe::think()
[04-08-2019_20-09-58] [FATAL] 0x657680 OpenXcom::State::think()
[04-08-2019_20-09-58] [FATAL] 0x69b170 OpenXcom::GeoscapeState::think()
[04-08-2019_20-09-58] [FATAL] 0x59eba0 OpenXcom::Game::run()
[04-08-2019_20-09-58] [FATAL] 0x41c8c0 SDL_main
[04-08-2019_20-09-58] [FATAL] 0x91a360 console_main
[04-08-2019_20-09-58] [FATAL] 0x91a480 WinMain
[04-08-2019_20-09-58] [FATAL] ??
[04-08-2019_20-09-58] [FATAL] ??
[04-08-2019_20-09-58] [FATAL] 0x7ffc5e294020 BaseThreadInitThunk
[04-08-2019_20-09-58] [FATAL] 0x7ffc5ec43670 RtlUserThreadStart
[04-08-2019_20-10-18] [FATAL] OpenXcom has crashed: Segmentation fault.
Log file: C:/_GAMES/OpenXcom_Ex/user/openxcom.log
If this error was unexpected, please report it on OpenXcom forum or discord.
The following can help us solve the problem:
1. a saved game from just before the crash (helps 98%)
2. a detailed description how to reproduce the crash (helps 80%)
3. a log file (helps 10%)
4. a screenshot of this error message (helps 5%)
-
I can start TFTD without problems; also create a base and continue.
Can you try a clean install without mods?
If it works, copy the mods into this new install folder.
If you can't make it work, just zip your entire game folder (the one that doesn't work) and upload it here, I'll check what's wrong.
-
I saw that the automatic night vision mode was removed as an option. Just wanted to comment that playing xcom files I kinda miss it. I run all of my cultist missions as night missions when in early game without smoke grenades, and not having to remember to turn off personal lights or turn on night vision was super helpful. I don't mind the having to turn on night vision much, but having to remember to turn off personal lights has gotten more than a few agents killed for me.
-
I saw that the automatic night vision mode was removed as an option. Just wanted to comment that playing xcom files I kinda miss it. I run all of my cultist missions as night missions when in early game without smoke grenades, and not having to remember to turn off personal lights or turn on night vision was super helpful. I don't mind the having to turn on night vision much, but having to remember to turn off personal lights has gotten more than a few agents killed for me.
I'll think of something for the next version...
-
Thanks Meridian, and sorry for not weighing in on the conversation earlier. I play xcom fairly infrequently anymore (basically only when a new version of xcom files or xpiratez comes out with features I'm super interested in), so I didn't notice the change until fairly recently, even though it was made almost half a year ago.
-
I can start TFTD without problems; also create a base and continue.
After several attempts to start the game, it suddenly started working! ???
I'll put him under surveillance!
A quick question about Mods: are "gif" files allowed with the latest OXCE version?
-
A quick question about Mods: are "gif" files allowed with the latest OXCE version?
Short answer: yes
Long answer: The GIF file loading is not done directly by OpenXcom, it is done by SDL (a 3rd party library we are using), and even SDL is outsourcing some work to the operating system. On most platforms (e.g. Windows, Linux, Android), it works fine. On some platforms (e.g. MacOS) it doesn't. So, unless you're using Mac, you can use GIFs. If you are on Mac, the only safe bet is png.
-
Thank you for your answer.
By testing all the mods I have in this game I discovered a very strange thing...
The "Gaus Sniper" Mod was crashing when I wanted to watch the USOpedia!
I discovered that now we shouldn't make any case errors with folder paths.
I had in the Ruleset: 0: Resources/UFOPaedia/GAUSSSNIPERRIFLE.png
But the path was: Resources/Ufopaedia/GAUSSSNIPERRIFLE.png
???
By fixing the case everything works!
-
OXCE is throwing some errors in the log-file about invalid/obsolete starting condition attributes in one of my mods. Is there any way to get a more detailed overview concerning the actual line or entry that throws that error? Because as far as i can tell they should be working fine.
EDIT:
NVM, found&fixed the errors.
-
Cross-Hair Cursor Now Allows Select Next Unit Hotkey!!
Thank You for this amazing feature! It wasn't in the April version. In the April version I had to right click with the mouse to make the cross-hair cursor disappear and only then could I select my next unit, IIRC. Now you have added the superb feature of the select next unit hotkey working flawlessly when I still have the cross-hair cursor active. It makes combat so much more streamlined!! Thank You!!
-
Cross-Hair Cursor Now Allows Select Next Unit Hotkey!!
Thank You for this amazing feature! It wasn't in the April version. In the April version I had to right click with the mouse to make the cross-hair cursor disappear and only then could I select my next unit, IIRC. Now you have added the superb feature of the select next unit hotkey working flawlessly when I still have the cross-hair cursor active. It makes combat so much more streamlined!! Thank You!!
I have not added such a feature.
If you say something like that is now possible, it's most likely buggy and will have to be fixed/removed again.
EDIT: this came from OXC: https://github.com/OpenXcom/OpenXcom/commit/7d219f52f5cb998e0726f69f872ac47d8f3023f0
-
I could have sworn i read something about a new feature referencing content from other mods inside your own mod, but for the life of me i can't find that post. Am i misremembering this?
-
Panic Message PopUp Timeout:
Is there an INI variable that can be changed to reduce the on-screen time of panic message popups? "XY has Panicked / Gone Berserk"
-
I could have sworn i read something about a new feature referencing content from other mods inside your own mod, but for the life of me i can't find that post. Am i misremembering this?
https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods
Panic Message PopUp Timeout:
Is there an INI variable that can be changed to reduce the on-screen time of panic message popups? "XY has Panicked / Gone Berserk"
No, it's hardcoded: https://github.com/OpenXcom/OpenXcom/blob/master/src/Battlescape/InfoboxState.h#L39
But you can press any key or any mouse button to close it.
-
https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods)
No, it's hardcoded: https://github.com/OpenXcom/OpenXcom/blob/master/src/Battlescape/InfoboxState.h#L39 (https://github.com/OpenXcom/OpenXcom/blob/master/src/Battlescape/InfoboxState.h#L39)
But you can press any key or any mouse button to close it.
Thank You. I would change the code and place a PanicMessageDisplayTime variable into options.cfg.
-
https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods
Ah yeah, only for sprites - that's the part i forgot. Thanks :)
-
Ah yeah, only for sprites - that's the part i forgot. Thanks :)
Well, everything else you could reference already before.
What do you have in mind?
-
Well, everything else you could reference already before.
What do you have in mind?
The problem I currently have is that I have some submods for OXCF. One of them introduces new soldier types, among other things. These soldiers are supposed to use the same armor types as the regular ones. Right now I have to add armor defintions (i.e. which armors they are allowed to use, and the default armors for some special map/mission types) every time the mod introduces new armors.
If possible i'd prefer to re-use the existing armor definitions, but simply add my soldier type(s) to the list of units - i.e replace
units:
- STR_SOLDIER
with
units:
- STR_SOLDIER
- STR_CUSTOM_SOLDIER
Yes, i can do that manually on every release, but it's not what i'd call elegant. I either have to include all of the original armor definitions and search&replace the entries, or i can sift through the original definations and copy&paste the new ones into my own definition rul. Either way the mod needs to be updated by hand. If i had a way to reference the entries the mod would work work with new releases without having to be updated.
I'm not sure this is even possible using YAML.
-
There is no easy way for the game to know if you intend to replace list entries or only add to the list entries... so current modding system assumes you intend to replace.
-
There is no easy way for the game to know if you intend to replace list entries or only add to the list entries... so current modding system assumes you intend to replace.
I'm not sure if i follow, but why would that be a problem?
-
Let's say vanilla research is:
research:
- name: STR_PSI_AMP
dependencies:
- STR_PSI_LAB
and your mod is:
research:
- name: STR_PSI_AMP
dependencies:
- STR_SUNFLOWER
How should the game know if you meant the final result to be:
research:
- name: STR_PSI_AMP
dependencies:
- STR_SUNFLOWER
or
research:
- name: STR_PSI_AMP
dependencies:
- STR_PSI_LAB
- STR_SUNFLOWER
-
Like i said in my initial post, i just want to replace the whole list. I don't necessarily need to 'add' the soldier type - i can simply replace the list with STR_SOLDIER + STR_CUSTOM_SOLDIER. That's not the problem i'm running into.
My question is how would go on referencing all entries containing STR_SOLDIER in the unit list without having to sort through them by hand every time a new armor gets added. And as far as i can tell that's not really trivial. What i want to do is copy all armor entries from one soldier/unit to another (or rather the other way around, seeing how armor is handled), without having to actually copy&paste all entries by hand. Something like "if this armor supports soldier_type_x, it should also support soldier_type_y".
-
Like i said in my initial post, i just want to replace the whole list. I don't necessarily need to 'add' the soldier type - i can simply replace the list with STR_SOLDIER + STR_CUSTOM_SOLDIER. That's not the problem i'm running into.
You CAN simply replace one with another... what I am reading is that you don't want to do it simply... instead you want to do it with some supercomplicated logic so that the game does it AUTOMAGICALLY for you.
What i want to do is copy all armor entries from one soldier/unit to another (or rather the other way around, seeing how armor is handled), without having to actually copy&paste all entries by hand.
When you mod, everything existing is copypasted without you having to copypaste it.
Something like "if this armor supports soldier_type_x, it should also support soldier_type_y".
But that's not copypasting.
That's adding support for automated replacement of old values with new values based on your defined rules.
Nothing like that exists... especially not if you want it to be a global rule, i.e. not having to define a rule on each entity (e.g. on each armor or each soldier).
Even simpler example:
Rules like "change all weapons with power 50 to power 60" are NOT available.
-
There is no easy way for the game to know if you intend to replace list entries or only add to the list entries... so current modding system assumes you intend to replace.
There are others case of this behavior that must be maintained as default.
The wish is to add some contents to a huge master mod, as example I would like to add some variant of a battleship to Area51 mod:
- type: STR_BATTLESHIP
size: STR_VERY_LARGE
sprite: 6
damageMax: 3200
speedMax: 5000
radarRange: 1000
accel: 6
power: 148
range: 65
score: 700
reload: 24
breakOffTime: 4000
battlescapeTerrainData:
name: UFO_160
mapDataSets:
- BLANKS
- U_EXT02
- U_WALL02
- U_PODS
- U_BITS
mapBlocks:
- name: UFO_160
width: 30
length: 30
I found in the forum a mod with this rule:
ufos:
- type: STR_BATTLESHIP
size: STR_VERY_LARGE
sprite: 6
damageMax: 3000
speedMax: 5000
accel: 6
power: 140
range: 65
score: 700
reload: 24
breakOffTime: 4000
battlescapeTerrainData:
name: UFO_160
mapDataSets:
- BLANKS
- U_EXT02
- U_WALL02
- U_PODS
- U_BITS
- UFOL83
mapBlocks:
- name: UFO_BS1
width: 30
length: 30
- name: UFO_BS2
width: 30
length: 30
- name: UFO_BS3
width: 30
length: 30
- name: UFO_BS4
width: 30
length: 30
- name: UFO_BS5
width: 30
length: 30
If I add them as a sub mod I "loose" the original UFO_160.map and the objects attributes of the master mod.
I would love to do so:
add_ufos_block:
- type: STR_BATTLESHIP
mapDataSets:
- UFOL83
mapBlocks:
- name: UFO_BS1
width: 30
length: 30
- name: UFO_BS2
width: 30
length: 30
- name: UFO_BS3
width: 30
length: 30
- name: UFO_BS4
width: 30
length: 30
- name: UFO_BS5
width: 30
length: 30
It could be usefull for all objects with a list of map blocks, such as terrains.
-
It could be usefull for all objects with a list of map blocks, such as terrains.
See attribute "addOnly": https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Terrains
-
You CAN simply replace one with another... what I am reading is that you don't want to do it simply... instead you want to do it with some supercomplicated logic so that the game does it AUTOMAGICALLY for you.
To be fair, you asked me what i had in mind. I also wouldn't call it 'automagically' - what i'm looking for is a way to inherit armor types (or soldiers types).
When you mod, everything existing is copypasted without you having to copypaste it.
Yes, but in order to actually modify stuff i have to copy and paste it. There is no simple way to add a new soldier type that references existing soldier types in regards to what armor it is able to use. I have to replace each unit list of every armor that soldier type is supposed to use. Why can't we simply reference an existing soldier type? Something like
soldiers:
- type: STR_CUSTOM_SOLDIER
[Stats...]
armor: STR_SUIT_UC
armorForAvatar: STR_SUIT_UC
armorRef: STR_SOLDIER
And the game would allow that unit to use all armors that contain STR_SOLDIER in their unit list. But i guess that would fall under the 'global replace' rule?
-
If you want some rule set have common part there is already tool for that: `refNode`
This allow you to define somewhere in yaml file some common part and then reuse it in other places:
items:
- &STR_LASER_RIFLE # Let's mark laser rifle info with an anchor
type: STR_LASER_RIFLE
size: 0.2
costSell: 36900
weight: 8
#
# a million other attributes...
#
- type: STR_LASER_SNIPER_RIFLE
refNode: *STR_LASER_RIFLE # First, let's inherit everything from the STR_LASER_RIFLE anchor.
bigSprite: xxx # And now let's give it a new sprite,
accuracyAimed: 160 # increase aimed shot accuracy
tuAuto: 0 # and disable auto shot.
This is example from beginning of https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#
In your case you could do:
dummySoldiers:
- &STR_SOLDIER_REF
[all common stats...]
soldiers:
- type: STR_CUSTOM_SOLDIER
refNode: *STR_SOLDIER_REF
[all custom stats...]
-
If you want some rule set have common part there is already tool for that: `refNode`
Yeah, i know abour refNode, but as far as i can tell it doesn't work across different ruleset (and by extension across mods), and it can't be used as a placeholder in lists (unless i am mistaken).
-
This is true, this work because it depend on yaml node references. To have some more then we would need rewrite all code responsible for loading rulesets, possible but will take lot of time to do. This could complicate and slow down loading code if done incorrectly.
If lot of modders have same problem case like you then it worth fix in code. If only few then we only transferring work to others and this is ineffectual because there is more modders than programmers (only Meridain is working on OXCE "full" time).
-
This is true, this work because it depend on yaml node references. To have some more then we would need rewrite all code responsible for loading rulesets, possible but will take lot of time to do. This could complicate and slow down loading code if done incorrectly.
If lot of modders have same problem case like you then it worth fix in code. If only few then we only transferring work to others and this is ineffectual because there is more modders than programmers (only Meridain is working on OXCE "full" time).
Yeah, i had a look at the YAML documentation beforehand and wasn't able to find anything along the lines of what i was looking for. I doubt that many others would have a need for this, seeing how this is basically for a submod.
-
See attribute "addOnly": https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Terrains
:o :-[
thank you very much
-
Thanks for new version !
But big pb ! :-[
v5.6.1
TFTD
Nota ;
C:\_GAMES\OpenXcom_Ex\standard\xcom2\Resources\UI\globe_tftd.png exist !
902 octets - 27x3
New Game... create first base... named first base... ok... Boom !
Found the issue.
Fixed.
Download new version at the usual place.
-
Found the issue.
Fixed.
Download new version at the usual place.
Thank you very much !
-
Reverse the Throw Grenade vs. Unprime grenade menu order?
Its very un-intuitive and counterproductive the current way. I want it the intuitive, natural way:
Throw Grenade
Unprime grenade
Naturally in combat I want to throw the FRIGGIN' grenade really fast and I do NOT wish to FCKN BUMP into its deactivate menu.. right?
Was it a Microsoft Engineer who coded this like placing the START button right beside the SHUTDOWN so the computer can be shut down accidentally???
-
I completely agree.
Whenever modders enable the unprime option, I disable it locally... it's easy, you can do it yourself.
Who would ever need to unprime a grenade, right?
-
I completely agree.
Whenever modders enable the unprime option, I disable it locally... it's easy, you can do it yourself.
Who would ever need to unprime a grenade, right?
Good! How to disable this option?
I scoured the files for the string "unprime", but only found it in the yml and by every grenade. There must be a central switch for this "feature" to be erased from existence?
-
Good! How to disable this option?
I scoured the files for the string "unprime", but only found it in the yml and by every grenade. There must be a central switch for this "feature" to be erased from existence?
Search and replace, takes a second.
-
Search and replace, takes a second.
The order of the two menu items is defined somewhere specifically?
Or you mean, just go to
items_XCOMFILES.rul
and delete all
unprimeActionName: STR_UNPRIME_GRENADE
?
-
I mean just delete
or replace with unprimeActionName: ""
or replace with #unprimeActionName: STR_UNPRIME_GRENADE
or replace with notWorking: STR_UNPRIME_GRENADE
or whatever kind of disable you prefer :)
-
Personally I like to have both (prime/unprime) for each grenade and explosive. :)
I use it... sometimes.
So I went through the "items" file and added the missing lines. ;)
Everyone has their own preferences! 8)
-
I mean just delete
or replace with unprimeActionName: ""
or replace with #unprimeActionName: STR_UNPRIME_GRENADE
or replace with notWorking: STR_UNPRIME_GRENADE
or whatever kind of disable you prefer :)
Thank You! You made my grenadiers very happy!
-
Personally I like to have both (prime/unprime) for each grenade and explosive. :)
I use it... sometimes.
So I went through the "items" file and added the missing lines. ;)
Everyone has their own preferences! 8)
Can you post a screenshot, how your grenade menu looks like now, after you did the mod?
-
Hi. Very short (maybe kinda dumb) question.
How does the ToArmor: attribute works?
I understand that the difference between ToArmor and ToArmorPre is the moment when the damage to the armor is applied. But, I wanted to know if ToArmor can fail to do any damage to the armor.
I guess it is something like this.
Armor: 100
wDamage: 100
ToArmor: 0.1
if you roll 50%, 50, then you do no damage to the armor. But, if it is ToArmorPre, you do 5 damage to the armor
if wDamage is 150, you do 15 with ToArmorPre, and 5 with ToArmor.
It is correct?
-
Can you post a screenshot, how your grenade menu looks like now, after you did the mod?
If you want....
(https://www.mediafire.com/?weqitego9kctc7x)
-
It is correct?
yes
-
This is for code check, if anything can be done:
SLOWDOWN FIX:
The game was noticeably slowing down "almost to a crawl" that was impeding gameplay. Here is the fix I found:
There are too many checks in the probably unoptimized code for constantly - I mean every couple frames - to check the state of most equipment??! WTH?? Lot of equipment lying on the floor of any craft is an FPS hog!
As a consequence:
You might notice during equipment loadout and on Battlescape your game has suddenly slowed down considerably.
To fix this:
While you are still on the base, press ALT+CTRL+X to clear all junk from your ship - Voilá! Instant SpeedUp - and then for the mission only pack the very few belongings you need: medipacks, grenades, maybe some ammo, but just a little heap!
As a result the game will be lightning fast again!! I noticed this on a big map with many monsters & lots of units and smoke/fire explosions. I thought it was my many units. No.
-
The code was optimised several times.
Don't take thousands of items with you on a mission.
-
The code was optimised several times.
Don't take thousands of items with you on a mission.
Okay. Makes sense. After all there is even a shortcut for it.
-
List of Targets to Select in Line of Sight First
How difficult would be to code that if a soldier is facing "north" then the targets with the red rectangle icons would be list-ordered to be the first as well: [1], [2], [3], etc.. would mean targets towards the north, in the line of sight of the soldier.
Currently my soldier is facing north and the red target select rectangle points to a target toward the south. If I press [1] => the camera centers on the target far behind my soldier and if I shoot then I'll hit my men behind me securing my back.
This would be some true Tactical Combat feature?
-
Currently my soldier is facing north and the red target select rectangle points to a target toward the south.
That should not be possible.
Red rectangle shows only enemies in the line of sight of the soldier.
Do you have a screenshot/save where this can be seen?
-
That should not be possible.
Red rectangle shows only enemies in the line of sight of the soldier.
Do you have a screenshot/save where this can be seen?
This occurs to me frequently with many units. When I click on the red [1] an enemy is selected far in the back of my soldier.
Will supply save + screenshot soon.
-
This sounds strange. Are you by any chance red/green colour blind? Because OXCE displays different target icons depending on which targets the selected unit can see.
-
Is there a place I can find the special keys within OXCE
e.g. CTRL+H - lets me know what happened on hit
I am especially interested in knowing how to change armors at loadout and also how to check which soldiers havent gotten experience during battlescape.
-
Is there a place I can find the special keys within OXCE
e.g. CTRL+H - lets me know what happened on hit
https://openxcom.org/forum/index.php/topic,6424.0.html
Crtl+H to show the hit/miss log for the last "action". (This is not meant to tell you how much damage is being done, only if it's hitting / actually hurting the enemy)
-
Last night Windows made a big update....
Since this morning no OpenXcom games have been running. XFiles/OXCE 5.6.1 / 2 !
I have a white screen!
Any ideas?
Tks !
SOLVED !
Apparently I can no longer use OpenGL after this Windows update!
So I changed two lines in the Options.cfg file!
useOpenGL: false
useOpenGLShader: Shaders/Raw.OpenGL.shader
RE-SOLVED !
Everything's back to normal!
The update of Windows 10 had removed the drivers from my graphics card and it had replaced my drivers with a generic Microsoft driver.
-
Question to the creators:
Would you please attempt to estimate, how much money would you need to develop
Persistent Stormable Fortifications
?
Persistent = persists, if not defeated, just breached, command centre is not taken, but the attacking party is forced to leave. Or the attacking party only intends to gather some XP, so at game begin - like a Ratman Village in XPiratez or some low level Bandit Hideout, I land my forces at any such fortifications, fire a few shots, kill a couple enemies and when the going gets though - highest difficulty / ironman - I just leave. Leaving the fortification in a "harassed" state.
The Persistent Fortification at this point becomes highlighted on the Geoscape, like a detected alien base.
Harassed Fortification = not beaten and regenerates SLOWLY, like in a month or two or three months max it will regenerate its soldiers numbers back to its original state PLUS a couple additions, like +soldiers, +weapons, etc.. Because next time they will be expecting us, but ONLY if they have fully regenerated!!!
Harassed + Wounded + Not Regenerated Fortification:
This is the goal of this feature: I continually harass a place/base and grind them down, kill a couple of their soldiers a couple times to reduce their number on multiple visits, while these repeatedly battered fortifications persist (until destroyed). So these places can be visited multiple times, like attacking Zenthil Keep in Pools of Darkness again and the soldiers always come out and shout:
- You won't beat us so easily!!
This feature would probably spawn many ideas, like Persistent Alien base, or in this case any fortification, Alien Citadel, Government High Rise Complex, Secret Area-51 Compound, Terrorist SuperHQ, Cult Nexus, anything.
Notice please that BASE DEFENSE already is such a persistent fortification, since if the aliens storm my base and I beat them, I suffer casualties, certain of my rooms are destroyed, many of my soldiers die ==> my XCOM-force is weakened and we become a Harassed + Wounded / Battered + persistent fortification, until my base is destroyed ==> aggressive alien retaliation
ONLY in the above case, it is the complete reverse! I want this BASE DEFENSE opportunity for the aliens too! And I want any MISSION like in XPiratez or The XCOM Files, any location be generated with this persistence feature in mind. In case anything goes wrong and I have to flee. Fleeing and planning revenge is the most important feature in tactical RPGs, I think, because they give the player strong emotions.
-
Let's say a week at 40 CHF/hour.
-
Let's say a week at 40 CHF/hour.
Thank You! Considering an emotionally involved programmer - "This has become a personal matter!", etc.. - maybe 10-14 hrs a day and bug fixing, another requested week or two, to polish and "just give it more love":
Seven 14 hrs workdays = 98 hrs = 40 * 98 CHF / week = ~3920 CHF per week.
+
Estimated polishing, any contingency during coding coming up, might mean plus 2 weeks = 8000 CHF
Realistically if anything unexpected comes up and requires added engineering hours, probably 3 weeks of work worth about 12000 CHF
((Then of course later paying for (difficult) bugfixing + important related community requests that are really good ideas and are very worthy to implement, but need serious work hours.))
Okay. Very nice! I needed the amount money to think about and make plans.
THANK YOU!!
-
I'm not an emotionally involved programmer, I work 8.5 hours a day (=42 hours a week). Working 14 hours a day only creates problems, no exceptions.
Also, I don't do this for money, my entire donation income from the last 5 years is 24 CHF (thanks to 2 generous donators).
Lastly, although being paid by time and material sounds really cool, I don't know if anybody actually does that.
In the last 15 years in the industry, I have seen only fixed price contracts... if you're ever in a situation that you need to outsource something, keep that in mind :)
All that being said, if you're a rich guy who can afford it, I would gladly do business with you.
Otherwise, your request will just end up on my todolist and may or may not happen sooner or later, or never. In this particular case probably later than sooner.
-
How to enable full light (or increase it by steps) at dark maps when using debug mode? Can't find info in wiki.
-
@Meridian, do you maintain some release notes for each OXCE release?
-
@Meridian, do you maintain some release notes for each OXCE release?
Yes, each release is announced in this thread, together with release notes.
I seem to have forgotten the 5.6.2 tho... here goes:
New OXCE v5.6.2 is up.
2019-08-15
- Prevent overcrowding of crafts in starting base
- Fixed CTD when going into MODS menu and not restarting the game
- Fixed AI not using grenades in certain situations
- "Save pre-primed grenades" user option now also applies to non-grenade items
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
I'm trying to mod the Autolaser shoot sound, to lower its volume, but when I define
extraSounds:
- type: BATTLE.CAT
files:
11: Resources/Sounds/Autolaser.wav
Then the simple lasgun [its lesser brother] sound effect is played MIXED together with the autolaser.wav
WTF is happening here?
--
I have an idea: packing a new sample2.cat. Let's see what happens..
Apparently when the game first loads the sounds into memory -it takes a long time and I should have to be able to reset the entire game so it loads everything again- , because now, upon subsequent starts, it just finds the old RAM addresses again, sounds that are still there in memory and loads everything together. Vanilla original and the new sounds.
So If I make a new sound it will be mixed with the sound position stored in RAM. :D
No cigar!
Now these two sounds are being played mixed together: one from memory, one from the sample2.cat file. ;D ;D ;D 0B 5F EF 01 43 27 laser shot
aand:
13 59 41 03 6C 34 laser/plasma hit
-
1/ Which version of OXCE are you using exactly?
2/ Which mod are you trying to change? And which version exactly?
3/ Can you upload your mod? The one that's not working.
I have an idea: packing a new sample2.cat. Let's see what happens..
Do not change original CAT files, it won't always work properly, as explained here: https://openxcom.org/forum/index.php/topic,7355.msg116263.html#msg116263
Then the simple lasgun [its lesser brother] sound effect is played MIXED together with the autolaser.wav
OpenXcom is not even theoretically capable of mixing two sounds into one, something else must be wrong.
Apparently when the game first loads the sounds into memory -it takes a long time and I should have to be able to reset the entire game so it loads everything again- , because now, upon subsequent starts, it just finds the old RAM addresses again, sounds that are still there in memory and loads everything together. Vanilla original and the new sounds.
So If I make a new sound it will be mixed with the sound position stored in RAM. :D
When you quit and start the game again, it DOES load everything again. It's not even theoretically possible to "find old RAM addresses again". The reason why subsequent starts are quicker is because of the harddisk cache.
-
I'm in a bandit cave. Mistook playing back mixed sounds with the fact that, where I shot was a close rock wall and the game had to play the correct autolaser sound effect, but then the shot hit almost immediately and the game had to play to laser hit effect as well, giving the appearance that both sounds were played at once mixed together. Because they were. Correctly.
On normal missions - with open, wide spaces - the autolaser sounded correctly - too loud - .. .. .. then its "hit-object" sound played out, to which I paid no attention, since the volume level of that one was okay. ;D
All right. So lets try this one again..
Okay, it works with the extrasounds method. Now: onto what I wanted to do originally:
1. mastering this autolaser shooting sound effect to make it amazing and
2. giving you new effects, for exotic, hand-held, mega-blaster-lasers! :D
-
My day-time job deals a lot with "minefield" questions, so it came "naturally" at the time of posting (yes, I'm at work ATM). :)
As per situations. I'm playing Piratez at the moment and my interaction comes from OXCE+ and the mod. I see a pull down menu on the top left that allows the filtering of items based on all sort of categories. I see also pull down menus on the craft inventory screen, like the one that says "equipped", where one can "top-off" items as needed. A similar feature may come useful for bases.
My intended use is for example, if I have assigned certain satellite bases to store each different class of items, like one base for craft parts, another for raw materials, another for surplus weapons, etc. Then after a mission where my local storage is overflow, or any other time, I can dispatch the excess to each of the corresponding bases. The ability to filter and show only items existing at the destination (from the pull down menu, for example), would come very handy.
I guess this may not be an issue for other mods, but for Piratez and its hundreds of different items, this would easy the pain a bit :)
Added, see screenshot.
-
While we're at it, may I request a global variable to make grav shields stack?
vars:
gravStacking: true
It won't significantly increase base defense power in most setups, but may allow you to slightly reduce the number of facilities used. Such as: 1 grav shield and 5 fusion defense = 10x fusion defense for 6 facility space. But 2 grav shield and 3 fusion defense = 9x fusion defense for 5 facility space.
On the other hand, mods like Tech-Comm might implement using large fractions of your base for defense, and trying to calculate how many grav shields vs defenses gives you the best ratio.
Grav shields stack in OpenXcom since early 2013.
-
Added, see screenshot.
Thank you!
Not to abuse Meridian's kindness, but I have another request (previously asked) :) :
- An option for transfer the loot after a battle (like the sell button but for transfer).
Currently this screen is triggered only when there is no room at the craft's original base. I don't know if the game code would allow that feature to work with the existing "sell" mechanic. I can see myself selling the loot and transfer the rest for some missions.
-
Okay, so, after downloading and updating to the latest Android app I keep getting crashes now. I'm still using the same version of the steam version and everything, nothing should have changed. Unless it requires TFTD now? Or something? How in the world did I break this. ~.~
-
Okay, so, after downloading and updating to the latest Android app I keep getting crashes now. I'm still using the same version of the steam version and everything, nothing should have changed. Unless it requires TFTD now? Or something? How in the world did I break this. ~.~
No, it doesn't need TFTD.
Can you try with this UFO data and let me know if it helped? <link removed>
-
Not to abuse Meridian's kindness, but I have another request (previously asked) :) :
- An option for transfer the loot after a battle (like the sell button but for transfer).
Currently this screen is triggered only when there is no room at the craft's original base. I don't know if the game code would allow that feature to work with the existing "sell" mechanic. I can see myself selling the loot and transfer the rest for some missions.
Don't edit your posts if you want me to see what you write... I found this only by accident.
I don't mind double posting, you can post even 100x times in a row in my thread if you want.
Btw. the request is on the todo list... it's just not easy to implement... it will take some time until I convince myself to look at it.
-
No, it doesn't need TFTD.
Can you try with this UFO data and let me know if it helped? <link removed>
No go, sadly, thanks for that suggestion though! I wonder what happened between updates.
-
No go, sadly, thanks for that suggestion though! I wonder what happened between updates.
Try uninstalling the old OXCE.
And delete everything except UFO directory... including options.cfg, standard directory, common directory, mods directory.
Then install fresh.
-
thank you! The deletion of everything except for the ufo file and reinstalling worked for now it seems. Hopefully won't break adding pirates! thank you, again! <3
-
Not to abuse Meridian's kindness, but I have another request (previously asked) :) :
- An option for transfer the loot after a battle (like the sell button but for transfer).
Added.
It was easier than I originally expected (famous last words).
-
After around 4 years my script are finally capable to:
[27-09-2019_21-56-19] [DEBUG] Script debug log at 0x1a: Hello World!
[27-09-2019_21-56-19] [DEBUG] Script debug log at 0x1a: Hello World!
[27-09-2019_21-56-19] [DEBUG] Script debug log at 0x1a: Hello World!
[27-09-2019_21-56-19] [DEBUG] Script debug log at 0x1a: Hello World!
[27-09-2019_21-56-19] [DEBUG] Script debug log at 0x1a: Hello World!
[27-09-2019_21-56-19] [DEBUG] Script debug log at 0x1a: Hello World!
debug_log "Hello World!";
This will allow in long run changing text in UI based on special conditions.
-
Where can i find actual validator for VSCode? Thanks.
-
Where can i find actual validator for VSCode? Thanks.
https://openxcom.org/forum/index.php/topic,6552.0.html
-
Ah, it was updated. Thanks.
-
How do you show accuracy in this, like x-piratez does?
-
How do you show accuracy in this, like x-piratez does?
X-piratez shows the accuracy same way as this.
-
New OXCE v6.0 is up.
2019-10-13
- Added Korean language
- Added scripts to soldier bonuses
- Support for one-time geoscape events: https://openxcom.org/forum/index.php/topic,7215.msg117828.html#msg117828
- Support for multiple game endings: https://openxcom.org/forum/index.php/topic,7476.0.html
- Soldier transformations: random stat improvements (within a range): https://openxcom.org/forum/index.php/topic,7196.msg117768.html#msg117768
- Soldier transformations: reroll individual stats: https://openxcom.org/forum/index.php/topic,7196.msg117767.html#msg117767
- Soldier transformation into an item (sacrifice, specialist to build a facility, etc.): https://openxcom.org/forum/index.php/topic,7196.msg117767.html#msg117767
- Checking research requirements on craft weapon clips: https://openxcom.org/forum/index.php/topic,7316.0.html
- Commendations can be prerequisites for soldier transformations: https://openxcom.org/forum/index.php/topic,7405.msg117870.html#msg117870
- "manaPool" keyword for soldier stat strings
- Minimum soldier rank requirement for a soldier transformation: https://openxcom.org/forum/index.php/topic,7405.msg117870.html#msg117870
- Infinite production can be changed to maximum possible production using a left-click on the "down arrow"
- Mission/Arc/Event script funds triggers: https://openxcom.org/forum/index.php/topic,7215.msg116973.html#msg116973
- Resize Ufopedia to fit all category buttons if possible
- Configurable TUs when waking up at the beginning of a new turn (global parameter 'tuRecoveryWakeUpNewTurn')
- Mana recovery via medikit (item parameter 'manaRecovery')
- "Stunning improves morale" mod option (global parameter 'stunningImprovesMorale')
- Flag for hidden Commendations pedia articles (ufopaedia article parameter 'hiddenCommendation')
- Support for elevated UFOs
- Allowed negative mana recovery per day
- One random item vs all items in RuleEvent (event parameter 'randomItem')
- Allowed transfers in the Debriefing
- Allowed multiple sales in the Debriefing
- Unhardcoded most of GUI backgrounds (interface parameter 'backgroundImage')
- Mission/Arc/Event script score triggers: https://openxcom.org/forum/index.php/topic,7215.msg116973.html#msg116973
- Mission/Arc/Event script item triggers: https://openxcom.org/forum/index.php/topic,7096.msg116970.html#msg116970
- "Items at destination" filter for base transfers
- Operation name generator: https://openxcom.org/forum/index.php/topic,6420.0.html
- Base name generator: https://openxcom.org/forum/index.php/topic,7376.0.html
- Random ambient sounds: https://openxcom.org/forum/index.php/topic,6647.0.html
- Soldier bonuses (from transformations and commendations): https://openxcom.org/forum/index.php/topic,7405.0.html
- More zombie types: https://openxcom.org/forum/index.php/topic,7404.0.html
- Added support for underwater weapon vapor clouds for UFO-based hybrid mods: https://openxcom.org/forum/index.php/topic,7390.msg116775.html#msg116775
- Added Geoscape event scripts: https://openxcom.org/forum/index.php/topic,7215.msg116753.html#msg116753
- Added "Auto update" user option
- Added mission abort penalty (alien deployment parameter 'abortPenalty')
- Added support for fake underwater xcom bases: https://openxcom.org/forum/index.php/topic,7356.msg116774.html#msg116774
- Added starting conditions by globe texture: https://openxcom.org/forum/index.php/topic,7356.msg116717.html#msg116717
- Added fake underwater globe textures support: https://openxcom.org/forum/index.php/topic,7374.msg116684.html#msg116684
- Added "Auto Night Vision threshold" user option
- Removed "Highlight new topics" user option
- Added "Sell All But One" hotkey ("Z" by default)
- Added death sounds by armor and gender: https://openxcom.org/forum/index.php/topic,7371.msg116561.html#msg116561
- Added unit response sounds (by soldier/unit, armor, gender or name): https://openxcom.org/forum/index.php/topic,7371.0.html
- Before a battle starts the turn number is zero for Y-scripts (instead of 1)
- Added UFO detection Y-scripts
- Added "Raw screenshots" user option (hidden)
- Smoother globe shadows
- Fixed inventory drawing performance issue
- Fixed TFTD resources loading performance issue
- various bugfixes
- c++17 support required for compilation
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html
Updated ruleset reference: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
Staggering (in a good way)
-
New OXCE v6.1 is up.
2019-10-30
- Soldier sorting includes stat bonuses now
- Ability to use globe texture/terrain in mapScripts: https://openxcom.org/forum/index.php/topic,7536.0.html
- Fixed rounding in polynomial formula calculations for stats (nearest integer as before)
- Fix/Prevent invalid/negative escape countdown (UFOs with short break off time never broke off on higher difficulties)
- Ability to specify precise item position within the default inv slot: https://openxcom.org/forum/index.php/topic,4187.msg118725.html#msg118725
- Speed up chain terrain explosions
- Consider 'explosionSpeed' also for AOE explosions: https://openxcom.org/forum/index.php/topic,7509.msg118724.html#msg118724
- More item lists for geoscape events + custom music: https://openxcom.org/forum/index.php/topic,7215.msg118723.html#msg118723
- Unit stats cannot go into minus
- Improved staff salaries & item maintenance: https://openxcom.org/forum/index.php/topic,4774.msg118449.html#msg118449
- Inventory stats improvements: https://openxcom.org/forum/index.php/topic,7515.0.html
- Equipment filter improvement: for firearms, check the ammo category too (if present onboard)
- Civilian spawn node types: https://openxcom.org/forum/index.php/topic,6477.0.html
- Reroll mana pool stat on save upgrades
- Soldier bonuses for pilots
- Statistical (bullet) saving now works on consumable medikits too
- It's possible to move an item with negative size into an overfull base
- "We can now..." UIs consider also bonus research (getOneFree): https://openxcom.org/forum/index.php/topic,6551.0.html
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html
Updated ruleset reference: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
New OXCE v6.1.1 is up.
2019-11-02
- Fixed rounding in stat calculations
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
So, I'm super late to the party. (I stuck with stable OpenXcom for a while way back; found Nightlies had better features and switch over a couple years ago; just now realized OCXE is a thing.) So forgive me if the following question is already answered elsewhere:
I JUST got OXCE to try out (so I'm on the newest version; update checker agrees) and noticed that interception is not predictive like in the Nightlies. I checked for the setting and realize it's completely gone. (Re-checked in Nightlies to make sure I was looking in the correct spot.) Was support for predictive interception trajectories dropped?
-
Was support for predictive interception trajectories dropped?
Yes, the feature is very buggy... and I don't like bugs, so I removed it completely.
-
Yes, the feature is very buggy... and I don't like bugs, so I removed it completely.
Ah. I think I know what you mean. (I've seen the feature do some odd or questionable things before. Though it worked for me more often than not.)
Any plans to re-implement it in a non-buggy way, or is it just one of those things that would be hard to get right given the circumstances or is more involved than a player would think? (I know it can be an time-consuming art to make something actually stupidly complex under the hood look seamless and effortless to a user. That, and users tend not to think about the effort put into programming.)
-
Any plans to re-implement it in a non-buggy way... ?
SupSuper has done at least a dozen of fixes in the nightlies... but with little to zero improvement IMO.
I think the feature is beyond repair.
-
Getting this error (see attachment). I think it's due to the fact that negative indexes for bigobs are now invalid.
I can't seem to find the thread/post (by yankes iirc) which explained the fix.
For example the spitter in question uses:
bigSprite: -2
What index should I use to get the same graphics? I'll run a find/replace and fix all of them.
edit: found it
-
Getting this error (see attachment). I think it's due to the fact that negative indexes for bigobs are now invalid.
I can't seem to find the thread/post (by yankes iirc) which explained the fix.
For example the spitter in question uses:
bigSprite: -2
What index should I use to get the same graphics? I'll run a find/replace and fix all of them.
https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods
Just copy the graphics into your mod and use a normal positive index like for any other bigobs you've added before.
-
https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods
Just copy the graphics into your mod and use a normal positive index like for any other bigobs you've added before.
Thanks. I wasn't using those indexes (my mod starts from 99 onward) so I simply used them:
bigSprite: -2 ---> bigSprite: 60
-
Thanks. I wasn't using those indexes (my mod starts from 99 onward) so I simply used them:
bigSprite: -2 ---> bigSprite: 60
And does it work?
I'm pretty sure it doesn't (unless you defined bigsprite 60 in your mod too).
-
Still haven't tested, but it does say:
If you were using these bigobs in your mod, you have 2 options how to fix it:
What I get from this is that I should use the other fixes only if I have those indexes already occupied.
Tested: lol nope it doesn't work
-
What I get from this is that I should use the other fixes only if I have those indexes already occupied.
No, that's not what it says :(
It says that if you had a negative index used anywhere, it will stop working (in 100% of cases) and you will need to fix it in one of the 2 provided ways.
-
When trying to update OXCE version received:
Error for 'STR_TANK_CANNON_ALLOY': offset '9106' exceeds mod size limit 1000 in set 'BIGOBS.PCK'
Can get around, expand at least to 10,000, or completely remove this restriction?
-
Can get around, expand at least to 10,000, or completely remove this restriction?
The restriction is there to prevent conflicts between mods, save memory and to improve performance.
I recommend to use smaller indices before you start using bigger ones.
If you are already using most of the indices below 1000, you can tell OpenXcom to reserve more memory for your mod in the metadata.yml file. Example:
name: "X-Com Files"
version: "1.0.2"
requiredExtendedVersion: "6.1.1"
author: "Solarius Scorch"
description: "snip"
id: x-com-files
master: xcom1
reservedSpace: 2 # this reserves 2,000 indices in the memory... if you want to reserve 10,000 indices you can write reservedSpace: 10
-
If you are already using most of the indices below 1000, you can tell OpenXcom to reserve more memory for your mod in the metadata.yml file. Example:
Thank you very much. Now everything works.
-
I see there are several options to define psi devices/weapons. Can the AI use them or is it always going to fallback on the ALIEN_PSI_WEAPON ?
-
I see there are several options to define psi devices/weapons. Can the AI use them or is it always going to fallback on the ALIEN_PSI_WEAPON ?
AI can use other weapons too.
-
- type: STR_PSICLONE
requires:
- STR_PSICLONE
size: 0.1
costSell: 63000
weight: 5
bigSprite: 456
floorSprite: 456
handSprite: 456
hitAnimation: 96
psiAnimation: 96
hitSound: 36
psiSound: 96
battleType: 9
twoHanded: false
invWidth: 1
invHeight: 2
accuracyMultiplier: # but what is the base accuracy? if they're multipliers and base accuracy is 0, then 0*x=0
psiSkill: 0.5
flatHundred: 0.5
tuUse: 25
tuMindControl: 0 # diables mind control
tuPanic: 25
flatRate: true
recoveryPoints: 8
armor: 15
attraction: 1
psiRequired: false
#aimRange: 1 # what about this, can dropoff work without it...?
dropoff: 1 # does this reduce the accuracy over distance of mind control and panic too, or only the stun attack???
# what i'm trying to achieve is the chance of panic success to decrease with distance
psiAttackName: STR_STUN_UNIT
damageType: 6 # stun
power: 50
powerRangeReduction: 1
damageBonus:
psiStrength: 0.5
damageAlter:
ArmorEffectiveness: 0
FixRadius: 0
RandomType: 2
IgnoreDirection: true
LOSRequired: false
This seems to work. If I assign it to an unit with psiSkill=0, will the unit use this?
(Also I have lot's of doubts about how this all works... :-[)
Maybe I should ass these in there:
accuracyPanic: 60
accuracyMindControl: 0
accuracyUse: 50 # how does this accuracy work? I want the attack to always hit, like a psi attack
-
Meridian please tell us how "mindPower" (facilities) works? The search provides links only to your presentations without any explanation.
-
Meridian please tell us how "mindPower" (facilities) works? The search provides links only to your presentations without any explanation.
Vanilla mind shield facility has a mind power of 1.
If you build 2 mind shield facilities in vanilla, they have together a mind power of 2.
In OXCE, instead of building 3 mind shields with power 1, you could also build just 1 mind shield with power 3... both would have the same effect.
-
Vanilla mind shield facility has a mind power of 1.
If you build 2 mind shield facilities in vanilla, they have together a mind power of 2.
In OXCE, instead of building 3 mind shields with power 1, you could also build just 1 mind shield with power 3... both would have the same effect.
Oh, if I knew before ... Thanks for the answer. I think that for this parameter it is worth giving a more detailed description in the "ruleset reference", so that more questions would not arise. It says - "The power of the mind shield provided by this facility.", which misled me.
-
Is it doable to make a code addition to let modder define UFO in alienDeployment, and then transfer this info to map generation? As for now for many thinks like Cult houses in XCF we need to define the whole mapscript for such deployment - to add specific ufo into mapscript. There is a lot of copypasting because of it. And it does not let me use terrain-specific mapscripts with such a deployment, where is a need to define a ufo. That multiply copypasting to the near-impossible limit.
UPD: looks like there are some ways (https://openxcom.org/forum/index.php/topic,7631.0.html) =)
-
New OXCE v6.2 is up.
2019-11-29
- BREAKING CHANGE: Option for extended running behavior: https://openxcom.org/forum/index.php/topic,7623.0.html
- BREAKING CHANGE: Option for extended weapon reload cost: https://openxcom.org/forum/index.php/topic,7613.0.html
- Weapon/ammo category "sharing": https://openxcom.org/forum/index.php/topic,7632.0.html
- Medikit targets: https://openxcom.org/forum/index.php/topic,7633.0.html
- EXPERIMENTAL: Options>Folders GUI
- Mod startup check: Manufacturing time must be greater than zero
- Unhardcoded alien inventory offsets: see 'alienInventoryOffsetX' and 'alienInventoryOffsetBigUnit'
- Don't load custom mods from the "standard" folder
- A few more hotkeys: https://openxcom.org/forum/index.php/topic,7561.0.html
- Consider monthly performance bonus during arc/mission/event scripts
- Fix grenade timer during civilian missions
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html (https://openxcom.org/forum/index.php/topic,6552.0.html)
Updated ruleset reference: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
how to define damage types?
should i just add the extra modifiers to all the armors? but then how to name them?
-
You don't have to change all armors, if you don't define anything it will be considered 100%.
STR_DAMAGE_10: "10"
STR_DAMAGE_11: "11"
STR_DAMAGE_12: "12"
STR_DAMAGE_13: "13"
STR_DAMAGE_14: "14"
STR_DAMAGE_15: "15"
STR_DAMAGE_16: "16"
STR_DAMAGE_17: "17"
STR_DAMAGE_18: "18"
STR_DAMAGE_19: "19"
-
Tell me, does the option that changes the order of loading units into ships exist?
Still continue to disappear 2x2 soldiers on some ships. And all because they are loaded after loading HWP. With 1x1 HWP and 2x2 soldiers, need a different loading algorithm.
-
Loading order is:
1. HWPs
2. 2x2 soldiers
3. 1x1 soldiers
-
Loading order is:
1. HWPs
2. 2x2 soldiers
3. 1x1 soldiers
Yes I know. It is in this that's the problem.
-
How about turning it into:
2x2 HWPs
2x2 Soldiers
1x1 HWPs
1x1 Soldiers
-
What a brilliant idea.
I would never think of that.
-
Apparently this is very difficult to implement. I, in turn, found a temporary solution - adding additional spawn cells. True, it looks monstrous when the tank is respawn on the roof of the ship. :D I'd like to hope that this measure is really temporary.
-
Apparently this is very difficult to implement. I, in turn, found a temporary solution - adding additional spawn cells. True, it looks monstrous when the tank is respawn on the roof of the ship. :D I'd like to hope that this measure is really temporary.
If you send me a pm with your craft map and load order, I can send you back an optimized version that should work for your needs without making significant changes.
-
If you send me a pm with your craft map and load order, I can send you back an optimized version that should work for your needs without making significant changes.
Thank you for the offer, but I already did everything myself. On some ships (such as Sentinel, Tactical Lightning), in the with the current loading system, a vanishing tank has nowhere to go. Only on the roof.
-
Yes I can. And ".log" in the appendage. Strangely, a lot of things have been written in ".log", but everything works exactly as intended. And about the sound is nothing.
Issue found and fixed (hopefully).
Thanks goes to Stoddard.
I'd like to hope that this measure is really temporary.
Load order changed.
-
Meridian, thanks to you and Stoddard. Waiting for updates. :)
-
I bet i saw somewhere something about shot vapor in ufo1. A weak ago or like that. But now i can not find it. Is it possible?
-
I bet i saw somewhere something about shot vapor in ufo1. A weak ago or like that. But now i can not find it. Is it possible?
https://openxcom.org/forum/index.php/topic,7390.msg116775.html#msg116775
-
Many thanks.
Also, looks like a bug:
I am testing growing alien bases, and i see this situation:
1. aliens landing for base building.
2. ranger fly near landed b-ship for search base location.
3. base found, but not near ranger. It can be in thousand of kilometers, but founded by ranger, patrolling near UFO.
upd: here is minimod for testing.
Upd. 2:
https://openxcom.org/forum/index.php/topic,7390.msg116775.html#msg116775
And on depth level = 0 no vapor possible?
-
Also, looks like a bug:
I am testing growing alien bases, and i see this situation:
1. aliens landing for base building.
2. ranger fly near landed b-ship for search base location.
3. base found, but not near ranger. It can be in thousand of kilometers, but founded by ranger, patrolling near UFO.
and which part of this is the bug?
If you mean that the base is not built where the UFO lands... that's normal... bases are never built where UFO lands.
Bases are built already when the UFO spawns (not when it lands)... and they are built in a random place defined by the "spawnZone" areas of the alien mission.
Upd. 2:And on depth level = 0 no vapor possible?
Not at the moment.
That would break TFTD.
But I can probably make it optional, if you want it... what's the intended use case?
-
Bug is, that ranger patrols in area of ufo landing, and alien base became visible far far away from there. like patrol in Spain and base in Norwegian.
And it is not coincidence, if no ranger patrolling - no base found.
About vapor - because beams was not supported by community, i wanted to create "smoke shot" for some unusual weapons.
-
Bug is, that ranger patrols in area of ufo landing, and alien base became visible far far away from there. like patrol in Spain and base in Norwegian.
And it is not coincidence, if no ranger patrolling - no base found.
What is the sight range of the ranger?
Default is 1696 (about as much as displayed on the screenshot)... which is enough to spot a south norwegian base from central spain :)
-
Default is 1696???
Gosh... Twenty times more than i expected.
Ok, my fault. Sorry.
-
We all know that downed UFOs explode power units. And where is it regulated and what determines the strength of their explosion? And is it somehow regulated?
-
We all know that downed UFOs explode power units. And where is it regulated
in the source code
and what determines the strength of their explosion?
RNG (180-250, HE)
And is it somehow regulated?
in the source code
-
RNG (180-250, HE)
Can this be taken out into an adjustable global option?
-
what's wrong with it?
-
Just want more control over the game. For example, the spread of damage is more to do, the type of damage is changed, the probability of an explosion for each UFO is different, and so on. :)
-
Would be nice to be able to set explosion (with custom parameters like power) to a given specialType (in terrain), not just Power Sources.
-
I don’t remember where I read it, but there was information that the interruptPercentage "alienMissions" also works on landing UFOs when you them ground assault. Is this true, or is there an additional termination parameter after ground assault?
-
I don’t remember where I read it, but there was information that the interruptPercentage "alienMissions" also works on landing UFOs when you them ground assault. Is this true, or is there an additional termination parameter after ground assault?
Yes, it is true: https://openxcom.org/forum/index.php/topic,6461.msg102052.html#msg102052
-
Understood, thanks. Just have a situation where interrupt the construction of alien bases are not favorable, and the ship "delicious" landed. Have to let go.
-
Understood, thanks. Just have a situation where interrupt the construction of alien bases are not favorable, and the ship "delicious" landed. Have to let go.
There's a way to get virtually any outcome you want.
A.) Alien base never fails to be built
- METHOD: don't use interruption on Alien Base or Alien Infiltration mission
B.) Countries can be prevented from leaving the project, but alien bases still get built
- METHOD 1: increase weights for Alien Base mission (make non-interruptible), decrease weights for Alien Infiltration mission (make interruptible)
- METHOD 2: allow countries to rejoin when base is destroyed
- METHOD 3 (ADVANCED): edit Alien Infiltration mission to change the base that it builds or make it not even build a base at all
C.) Infiltration is interrupted by shooting the craft down, but not by taking them on land
- METHOD: Add a wave of three UFOs after the final craft, on a timer of perhaps 60 (try different values and see). You want the final UFO to spawn on the globe around the same time as the big UFOs start landing. (My mod has the timer at 240 which has been well-timed to make the base appear during and towards the end of the landing event.)
PM me if you want more details on how to do one of these, or if you have a different functionality goal.
edit: I tested some timers and I think 60 is fairly good for the final 3 ships. That means you get about 3 hours from appearance of the Battleship until the base is built and the infiltration is completed. Time variation can be anywhere from 1.5 to 4.5 hours but will tend toward the center. In my run, the battleship took ~3.5 hours to land, and other ships were already landing by the time it arrived.
-
It is unclear for me what is the difference between OXC and OXCE(+).
I could not find any documentation about it. Even wikipedia does not have an entry about OXCE.
-
It is unclear for me what is the difference between OXC and OXCE(+).
I could not find any documentation about it. Even wikipedia does not have an entry about OXCE.
Check sticky topics on this subforum then.
For example https://openxcom.org/forum/index.php/topic,5251.0.html
-
New OXCE v6.3 is up.
2019-12-30
- Research/Manufacture UI QoL (mouse wheel up/down +/-1, with ctrl +/-10)
- Different starting base per difficulty level: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Starting_Base
- Ability to hide missions in New Battle mode: https://openxcom.org/forum/index.php/topic,7685.0.html
- Stats for nerds -- craft weapons
- Don't hide other radar circles when showing craft range
- Check alien containment after reload (shame on you autosave cheaters!)
- Direct Craft UI access from Intercept UI (right-click)
- New hit log (ctrl+alt+H)
- Changed soldier/HWP load order (2x2 hwps, 2x2 soldiers, 1x1 hwps, 1x1 soldiers)
- Memorial quick filter
- Stack items given by a geoscape event together (+new multi-item attribute): https://openxcom.org/forum/index.php/topic,7215.msg118723.html#msg118723
- Configurable medikit action name ('medikitActionName')
- Some improvements for summoned friendly units (inventory handling)
- Support for spawning alien bases on technical globe regions
- UFO hunt alert sound ('huntAlertSound')
- Weapon/ammo category "sharing" is now optional ('shareAmmoCategories')
- Custom UFO for dummy/blank 'addUFO' mapscript command (by Finnik): https://openxcom.org/forum/index.php/topic,7631.0.html
- Battlescape rendering performance improvements
- various bugfixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html
Updated ruleset reference: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
Thank you Meridian for version 6.3. I'm about to test it with XCF v 1.1.2.
By the way, any clue on when my antivirus program (Symantec) would stop complaining about the file being too new?
Unfortunately, I can't control the AV settings too much while I use my work laptop at home :)
-
Meridian, thanks so much for the update.
By the way, are the mods in the "standard" folder really needed? Does anyone use them? Those who update OXCE already have everything, and if not, they can be taken from the OpenXcom client if they are needed. Maybe should remove them from the OXCE archive?
-
Meridian, thanks so much for the update.
By the way, are the mods in the "standard" folder really needed? Does anyone use them? Those who update OXCE already have everything, and if not, they can be taken from the OpenXcom client if they are needed. Maybe should remove them from the OXCE archive?
They cannot be taken from OpenXcom, they are incompatible.
OXCE makes updates to language files, interface files, resources, etc.
-
New OXCE v6.3.1 is up.
2020-01-01
- Fix cancel new base CTD (by Hardcode84) (>1 year old)
- Fix "Dont reselect unit" CTD (7 months old)
- critical: Fix hit log CTD (1 week old)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
New OXCE v6.3.2 is up.
2020-01-04
- critical: Fixed unit drawing bug (mostly TFTD crashes)
- Increased max craft weapon types per slot from 4 to 8
- Show more info in Options > Folders
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
New OXCE v6.3.3 is up.
2020-01-05
- more fixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
Meridian, is it possible to change the color of the radar circles?
And yes, when passing under units hanging one level higher - they are visible during movement. It looks monstrous, although no errors are recorded. I don't expect I'll be able to clearly explain not knowing the language, but... Just try walking under the hovertank.
-
Meridian, is it possible to change the color of the radar circles?
There is no radar circle color.
Color of each pixel is calculated separately using complicated logic (considering land/ocean, current time of the day, original pixel color, etc.)
And yes, when passing under units hanging one level higher - they are visible during movement. It looks monstrous, although no errors are recorded. I don't expect I'll be able to clearly explain not knowing the language, but... Just try walking under the hovertank.
Thanks, will report to Yankes.
-
New OXCE v6.3.4 is up.
2020-01-11
- Custom groups for addLine mapscript command (by Finnik)
- Fix unit drawing error (hovertank rendered when a unit moved below it)
- Fix grenade skip (2nd grenade exploded half-turn later)
- Fix alien base self destruct CTD
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
To Meridian
Can the following proposal be implemented: If a player ignores the crash site, the crew of the shot down UFO gets to the nearest town, and welcome to the terror mission.
Sorry for my poor English/
-
To Meridian
Can the following proposal be implemented: If a player ignores the crash site, the crew of the shot down UFO gets to the nearest town, and welcome to the terror mission.
Sorry for my poor English/
I like that, peraphs only with medium/large vessels?
-
I think we need a "critical mass" of live aliens. Like 5+ for Superman, and more for other levels. Or work from UFO level.
-
To Meridian
Can the following proposal be implemented: If a player ignores the crash site, the crew of the shot down UFO gets to the nearest town, and welcome to the terror mission.
Sorry for my poor English/
Same should also happen with aborted crash recoveries.
-
Is there a problem with the attached openxcom extended as I have no mods activated but it won't launch the game? This seems to occur with the latest one as the oxce of 26/01/20 works fine.
-
This should be fixed already
-
New OXCE v6.4 is up.
2020-03-14
QoL:
- Added "Unassigned" category in Buy/Sell/Transfer GUIs (only applies to mods using custom item categories)
- Condensed "facility built" popups (only show one if multiple facilities of the same type are built)
- Pressing X again in Sell GUI deselects all items
- Purple box indicator also for stunned allies with negative health regen
- Ability to save/load soldier equipment layout including armor
- Research lookup and spawned item now shown in the tech tree viewer
- Debug hotkey to reveal all UFOs and alien bases (ctrl+7)
- Added win64 version to auto-updater
Modding:
- BREAKING CHANGE: Extended HWP load order unhardcoding ('extendedHwpLoadOrder') - default is vanilla again
- Support for defining manuf. project shortcuts: https://openxcom.org/forum/index.php/topic,5199.msg124405.html#msg124405
- Random alternate terrain in map scripts (by Finnik): https://openxcom.org/forum/index.php/topic,7758.0.html
- Custom groups for addLine mapscript command (by Finnik): https://openxcom.org/forum/index.php/topic,7750.0.html
- Flag to allow objective type recovery: https://openxcom.org/forum/index.php/topic,7755.msg122277.html#msg122277
- Increased max craft weapon types per slot from 4 to 8
- From OXC: Allow ammo to work only on land/water
- Soldier skills (by memmaker): https://openxcom.org/forum/index.php/topic,7974.0.html
- Allow soldier type to be displayed in the inventory screen (by memmaker): https://openxcom.org/forum/index.php/topic,7861.0.html
- Allows special weapons to be defined by soldier type (by memmaker): https://openxcom.org/forum/index.php/topic,7859.0.html
- More options for psi amp targeting (by memmaker): https://openxcom.org/forum/index.php/topic,7860.0.html
- Callsigns for soldiers in battlescape (by memmaker): https://openxcom.org/forum/index.php/topic,7825.0.html
Scripting:
- Soldier skills script hook (see above)
- Flash messages in BattleScape for scripts (by memmaker): https://openxcom.org/forum/index.php/topic,7826.0.html
- Medikit use script hook (by memmaker): https://openxcom.org/forum/index.php/topic,7824.0.html
Bugfixes:
- Fixed various bugs with units waking up too early or too late
- Fixed definition of "night" in soldier diaries
- Do not allow soldier bonuses to "unlock" psi skill
- various bug fixes
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html
Updated ruleset reference: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
-
- Ability to save/load soldier equipment layout including armor
Great!
Thank you for this release!
-
Thanks for W32 version ! :)
-
- BREAKING CHANGE: Extended HWP load order unhardcoding ('extendedHwpLoadOrder') - default is vanilla again
what does this mean/affect ?
-
what does this mean/affect ?
If set to true, craft load order is: 2x2 HWPs, 2x2 soldiers, 1x1 HWPs, 1x1 soldiers.
If false, craft load order is: all HWPs, all soldiers.
Default is false now, same as vanilla.
(it was true only very shortly... I think only in oxce 6.3.x)
-
Thanks for the updates. Good work.
Regarding Auto-update. Microsoft recently announced the end of support for Win-7 and released the final patch, which caused users a lot of problems. I was saved from them by the fact that I have the habit of disabling Auto-update where possible and updating everything manually. Hopefully, Auto-update will not be in the future, the only way to upgrade?
-
As this small feature, I will post there, I added new feature to have item script for psi attack calculation that is run before current script from unit.
As side bonus it is responsible for all calculation of basic psi attack probability, you can now overwrite whole logic of this to fit your needs.
-
Hi, Meridian I apologize in advance if I write in the wrong topic, I only registered today, although I have been on the site for several months now.
In general, I wanted to offer one idea (I do not know how much you will not like it)) I will try to be brief.
My brother and I love to play X-Com and I like to play, say, PERFECT.
I did not really like the XCOM remake
When I speak perfectly, I mean that not one of my soldiers died (and did not receive serious injuries), and in the process I like to fantasize in my head how this could have happened in 3D (I have a lot of imagination, and therefore the gameplay produces more pleasant impressions)
Of course, this requires constant Save / Load, but it does not bring me much discomfort, because I can do quick save and load.
So what am I talking about? Oh yes, I wanted to propose the idea of recording a battle in which the battle will smoothly take place, beautifully and spectacularly (as part of a normal battle, just a smooth repetition without too much).
Of course, the proposal to save the battle record in the results after the battle, and the ability to download and view in a separate menu, choosing records.
I know that the idea itself smacks of at least strange, but it's just an idea and I wanted to know what you think about it.
Yes, just your thoughts about it will be very interesting to me. Thank you in advance for your response. (I hope this is not a short no answer))) :D
-
So what am I talking about? Oh yes, I wanted to propose the idea of recording a battle in which the battle will smoothly take place, beautifully and spectacularly (as part of a normal battle, just a smooth repetition without too much).
Of course, the proposal to save the battle record in the results after the battle, and the ability to download and view in a separate menu, choosing records.
I do not understand this part.
Can you say it in different words maybe?
-
I do not understand this part.
Can you say it in different words maybe?
Yes, I will try.
Do you know about battle play recording in turn-based games? I wanted to offer the ability to record and save the entire battle in the game.
I will try to describe it. You play for yourself, think about each movement for a long time, and, as a rule, a battle (or a game, like in chess) takes a lot of time if this is an important battle.
And after a triumphal victory, you could (of course, after you clicked on the button “Save battle record”) see this very record, which we say you wanted to show to someone.
At its core, combat recording is a repetition of all actions that took place to the very end. Without thinking, just a little faster, because you no longer fight, but you follow your victory.
Let me give you an example, the Counter-Strike demo is a repetition of all your actions, as well as the adversary who plays the game.
I don’t know if I can explain it more comfortably, but, frankly, it’s just a repetition without delay, when you think: “Who will go where, who will shoot at whom”.
I apologize if I described everything vaguely :-[
-
To me this comes across as a request for "Replay" functionality.
Meaning that the game stores all your actions (move to, shoot at, change heading, etc) and the resulting game state of each action during a battle. Not only for your side, but also for the aliens and civvies,
The replay itself would than be something alike the "New Battle" option, but instead of accepting user input (and AI calculating its next move) it will take the list of stored actions and perform them sequentially (with a slight delay between each action).
Am i correct in my assumption?
-
Yes, you described everything better than me.
Hmm, I have to be more precise and talk less, otherwise I will continue to lead people into a stupor.
-
It is theoretically possible, but a lot of effort.
-
It is theoretically possible, but a lot of effort.
I know that the description of actions itself indicates a lot of work on this function.
But I wonder what you think about this? Is this feature quite suitable for X-Com? Or is this a bad idea. (I mean anyone who reads this)
-
It's a good idea. it'd be much easier to share your epic battles/enjoy them yourself.
it'd also be great for people interested in the story of their soldiers.
I'd certainly enjoy it.
Sounds like a very far future thing at best though.
-
It's a good idea. it'd be much easier to share your epic battles/enjoy them yourself.
it'd also be great for people interested in the story of their soldiers.
I'd certainly enjoy it.
Sounds like a very far future thing at best though.
Exactly) you think exactly like me)
Yes, if they work on it, it will not appear soon, but it is not scary.
-
Small bugreport (or feature description):
if unit have specab: 1 (explode on death) and its armor have both corpseBattle and corpseGeo, it will not explode. At least with power, described in battle corpse item.
-
Small bugreport (or feature description):
if unit have specab: 1 (explode on death) and its armor have both corpseBattle and corpseGeo, it will not explode. At least with power, described in battle corpse item.
Explosion power is described in corpseGeo item: https://github.com/OpenXcom/OpenXcom/blob/master/src/Battlescape/ExplosionBState.cpp#L89
Don't know if that's right or wrong... try asking SupSuper/Warboy.
-
Odd. But i get over it with destruction of corpse. So it will be not recovered.
-
Odd. But i get over it with destruction of corpse. So it will be not recovered.
You can also just add power to the corpseGeo item, no?
-
No, because this corpseGeo used for many other purposes.
-
Asking that here because this is OXCE mechanics. Here 2 screenshots:
(https://i.postimg.cc/tsWPBy56/screen082.png) (https://postimg.cc/tsWPBy56)
(https://i.postimg.cc/VrgH5pHS/screen083.png) (https://postimg.cc/VrgH5pHS)
Current TWoTS mod rules allow you produce 4 Gauss pistols using 1 magnetic navigation. But screenshots shows only 1 produced unit. It's kinda confused because we can't exactly produce 1 pistol, otherwise it will require 1/4 magnetic and it's not possible right? So I have a question - can you change production screen in case if multiply production rule used, so amount of product will be like 4,8.. and etc. I mean total production screen units = special materials (could require more than 1 and it's ok of cource) x multiplyer (if it's more than 1). Sorry for terrible English, hope you understand what I meant. May be in future versions of OXCE?
-
No.
It is 1 unit of manuf. project "Gauss Pistol", not 1 unit of item "Gauss Pistol".
What would you want to see in the "Units to Produce" if the project would manufacture 7 gauss pistols, 2 gauss rifles, 17 electroflares and 4 mindprobes at once? 7+2+17+4 = 30 ?
The manufactured items (per 1 project) are already displayed 1 screen earlier, see screenshot.
And there is a possibility to rename the project as well, for example from "Gauss Pistol" to "Gauss Pistol (x4)".
-
Oh, thank you Meridian for quick reply and explanation. And "Gauss Pistol (x4)" will solve any issues as I think. Because it's easy to understand now what total amount of production multiplied, that's what I want. So, the modder just need to adjust some .rul files for this right?
-
And there is a possibility to rename the project as well, for example from "Gauss Pistol" to "Gauss Pistol (x4)".
Oh, I forget about it. My fault, will be fixed.
-
New OXCE v6.4.2 is up.
2020-03-15
- MUCH MUCH faster alien hidden movement (regardless of alien movement speed setting)
- much faster player movement speed at higher player movement speed settings in Options (same as in year 2018 and earlier versions)
- (supposedly) more battery drain on laptops/phones (same as in year 2018) -- not confirmed; and not quantified
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Some of you have already tried this version (it's been published via auto-update) and everybody so far reports big improvements and no side effects.
I'd like to ask everyone else for feedback as well.
IMPORTANT:
To benefit from speed improvements, you need the following settings in Options menu:
1. "Advanced>FPS limit" must be different than 0 (I recommend 60)
2a. Either use software rendering (Video>Display Filter = Disabled)
2b. Or use OpenGL rendering (for example Video>Display Filter = Raw*) AND also set vSyncForOpenGL: false in options.cfg file --- and just to repeat again, DO NOT set "Advanced>FPS Limit" to 0!
This will make OXCE able to run at the same speed as in this video (OpenXcom version from year 2018): https://www.youtube.com/watch?v=hjIrqlsJjQ0
So that you have a benchmark to compare against.
Feedback is most welcome... positive and more importantly also negative.
-
New OXCE v6.4.2 is up.
How do I see these changes do not affect the version of Win32?
-
How do I see these changes do not affect the version of Win32?
I don't understand the question.
-
Excuse me, but is this speed up is because of animation speed increased, or because of massive code optimisation?
-
I don't understand the question.
And already it is not necessary. Everything works. Thanks for the updates. :)
-
Excuse me, but is this speed up is because of animation speed increased, or because of massive code optimisation?
It's not code optimisation.
It's complicated to explain (and I don't fully understand it either), but you can think of it as animation speed increase.
-
Actually? Add more features to play with resources. and additional complexity options.
Project: Economics X-com
Tasks of the Economy:
// Change the price "total per month"
// Change the price "random per month"
// Change in price "events:
fixed> + price; -price;
percentage> * x% ""
// Change the price for the "people" position separately
// Change the price for the position of the "machine" separate
// Price balance in the range: from Minimum price to Maximum price.
// The fall in the price of goods over time "in the absence of its procurement"
// Price increase when buying a product for a limited time
// Rising hiring prices with the deaths of Agents, + x%
// Price fall while saving Agents / month, --x%
// Increase in the price of the maintenance of Agents depending on the ranks, + x% / rank
// Increase in the price of hiring Engineers and Scientists from their existing number, + x% / person
// Payments to relatives for the deaths of Agents
// Compensation payments upon dismissal of people monthly salary
//Inputs:
//Starting price
//Current price
//The coefficient of price change when recalculating from the current price to the new price
//Output:
//New price
// minimum share price of the starting price (by default, a quarter = 25%)
// maximum price increase (by default four times = 400%)
I used google translate if there are any grammatical errors.
-
1. Meridians job to do:), but shouldn't you make a new thread for this?
2. This would be AMAZING to have available as a modder.
-
Back to "Gauss Pistol (x4)" question. Modder has changed produce message to "Gauss Pistol (x4)" now, but another thing now bothering me. First time red popup screen when this project completed. It's now has that multiply modifier too: "Gauss Pistol (x4)". So can we have two different options: Normal message after research finished which could looks like: "Gauss Pistol", but have correct multiply amount "Gauss Pistol (x4)" in production screen when you start it? Or it's not possible? Two different lines in .rul files one for research complete and ready for production screen and second for starting production in workshops?
-
Don't l ow if possible but may be possivle to ha e bullets ricochet when metal and wooden surfaces are hit?
-
Don't l ow if possible but may be possivle to ha e bullets ricochet when metal and wooden surfaces are hit?
If we went into such realms of fantasy, I would first request terrain penetration... So a bullet wouldn't disappear after destroying a paper wall, but continue onwards with an appropriate power decrease.
But it's not very X-Comy, so I won't do that.
-
New interesting PR from memmaker was merged to OXCE, point was that it allow arbitrary change spawn unit, this mean you can now alter what unit will spawn after zombify attack.
-
If we went into such realms of fantasy, I would first request terrain penetration... So a bullet wouldn't disappear after destroying a paper wall, but continue onwards with an appropriate power decrease.
But it's not very X-Comy, so I won't do that.
Sorry for the typos, but it cannot be set without tampering with rocket science things? Cannot be a simple terrain attribute, or for instance as a condition (if wodden hit then play xx) i'm not into IT so i hope it might give the idea 8) :o
-
As far as I understand it, terrain does not even have a material attribute.
For ricochets, such as you described them, several additions would have to be added.
A) Terrain material in MCD file. (So that we can know if it is wood, metal or something else. There is sound which walking over it makes at offset 0x34, which is closest, but you can't tell wood from dirt on that one.)
B) An option to select what damage types ricochet off which materials, and at what maximal angles. You would not want plasma, for example to bounce off of metal. Or for that matter, a bullet hitting a wooden fence straight, then bouncing back and hitting the soldier who fired it.
C) The geometry would have to recognise at what angle it was hit, to determine if the ricochet happens, and where to.
D) As Solarius Scorch mentioned, there should be other interactions, such as overpenetration, passing straight through, no damage to specific materials (electric to metal).
-
Back to "Gauss Pistol (x4)" question. Modder has changed produce message to "Gauss Pistol (x4)" now, but another thing now bothering me. First time red popup screen when this project completed. It's now has that multiply modifier too: "Gauss Pistol (x4)". So can we have two different options: Normal message after research finished which could looks like: "Gauss Pistol", but have correct multiply amount "Gauss Pistol (x4)" in production screen when you start it? Or it's not possible? Two different lines in .rul files one for research complete and ready for production screen and second for starting production in workshops?
The manufacturing recipe must have a different name from the name of the item it produces. Example:
manufacture:
- name: STR_GAUSS_PISTOL_X4
producedItems:
STR_GAUSS_PISTOL: 4
-
Is any way to save aquanaut who had "frozen (stunned) to death" status? Or it's impossible remove it even with med-kit and he(she) eventually will die?
-
A large dose of stimulants will save them.
-
Yeah, thanks, just did it and save a guy. Thanks for fast reply.
-
How to prevent aliens enter my ships? What should I remove in rul files?
-
That would be in the OXCE code, not in .rul files.
-
Lol, why wouldn't they enter your ships?
"Commence the assault!"
"Leader, they put a sign on the door, it says 'no ayys allowed'."
"Drat! Abort mission."
-
"Sir, the door isn't locked..."
"Soldier, we may not enter without proper pleasantries, as it says right here!"
-
Lol, why wouldn't they enter your ships?
"Commence the assault!"
"Leader, they put a sign on the door, it says 'no ayys allowed'."
"Drat! Abort mission."
Very funny? Because in vanilla they can't and I stay there all time killing them one by one. Now it's almost impossible to hide.
-
I never noticed such AI behavior in vanilla. Once I found the last alien hiding in my Skyranger in vanilla =)
-
Yes, this is neither sensible nor confirmed by experience.
-
someone has trouble with my mod, he posted his log and it says it uses OXCE 6.4.3.. but isn't 6.4.2 the latest? wut?
[05-04-2020_21-06-41] [INFO] OpenXcom Version: Extended 6.4.3 (v2020-04-05)log attached.
-
someone has trouble with my mod, he posted his log and it says it uses OXCE 6.4.3.. but isn't 6.4.2 the latest? wut?
[05-04-2020_21-06-41] [INFO] OpenXcom Version: Extended 6.4.3 (v2020-04-05)log attached.
There are unofficial nightly builds after every change.
They live on the bleeding edge.
6.4.2 is the latest official.
-
I suspected something similar. No issues on 6.4.2 too *breathes a sigh of relief*. Thanks.
-
Posting it's here because I think this is OXCE related bug. Nagas can use fans as holes in the USO and just moves up through it. I'm adding save file, it's Ironman, so set it off if you need.
(https://i.postimg.cc/wyKX37zc/screen088.png) (https://postimg.cc/wyKX37zc)
Arrows mark their movement up-down. It's currently should be under fan on first floor.
-
Do you check OXC or Vanilla how they behave? I don't think we change any thing in that aspect in OXCE.
-
Posting it's here because I think this is OXCE related bug. Nagas can use fans as holes in the USO and just moves up through it. I'm adding save file, it's Ironman, so set it off if you need.
(https://i.postimg.cc/wyKX37zc/screen088.png) (https://postimg.cc/wyKX37zc)
Arrows mark their movement up-down. It's currently should be under fan on first floor.
Why is that a bug? Xcom units (e.g. your shrimp drone) can do that too.
-
Ok, I never tried with drone this trick yet, thanks for explanation. That Naga who magically appears from fan just scary me =)
-
Hi,
I'm new so I probably doing something stupid but here it goes:
My OS is Ubuntu 18.04.4 - user has admin rights.
- I have the XCOM Ufo Defense vanilla files incl. patch
- I downloaded the latest version of Openxcom Extended
- Unzipped the 7z file, all good.
- Copied the vanilla folders to the UFO folder (according to the readme.txt file in the UFO folder)
- Now ,in the parent directory I have the file OpenXomEx... it has the checkbox "allow executing file as a program" checked.
but I cannot run it, it's no executable? it's a shared lib of some kind...
I want to use OpenXcom Extended to run the open Xcom files mod...
Any help much appreciated.
-
It is a known bug in one of ubuntu's components.
Try the procedure as described by Meridian in the topic this bug was first encountered:
https://openxcom.org/forum/index.php/topic,7361.msg116438.html#msg116438 (https://openxcom.org/forum/index.php/topic,7361.msg116438.html#msg116438)
If that solves your problem but you still insist on starting via clicking an icon you can use my workaround as posted in that same topic:
https://openxcom.org/forum/index.php/topic,7361.msg116347.html#msg116347 (https://openxcom.org/forum/index.php/topic,7361.msg116347.html#msg116347)
-
Questions: why aquanauts miss the shots if they have 120% accuracy? How that possible and why more than 100%? Is it possible to change human death sounds for two different types (female, male) in tftd like in original USO using .rul files or it's hard coded?
-
Questions: why aquanauts miss the shots if they have 120% accuracy? How that possible and why more than 100%?
Because it is not 120%.
It's just 120.
Without %.
Is it possible to change human death sounds for two different types (female, male) in tftd like in original USO using .rul files?
Yes.
-
Because it is not 120%.
Then what is this? Why % present?
(https://i.postimg.cc/ppTkmcTz/screen089.png) (https://postimg.cc/ppTkmcTz)
-
It was probably the best option for Gollop to communicate to the player 2 things [1]:
* The bigger the number, the better
* It has something to do with how likely you are to hit the target
[1] Baring aside creating some glyph nobody would understand without reading the manual.
-
Bear in mind I haven't looked through the code on this, but the percent chance given is the actual chance to hit a 2x2 square of target voxels plus 20. The reason for the plus 20 is the fact that a hitbox is generally larger than a 2x2 voxel square. The actual chance to hit is impossible to quantify as sometimes it hits the target voxel square but one of the voxels in the square is obstructed so it looks like it misses to the player.
TLDR: Hit chances are a reference and nothing more concrete.
-
Bear in mind I haven't looked through the code on this, but the percent chance given is the actual chance to hit a 2x2 square of target voxels plus 20. The reason for the plus 20 is the fact that a hitbox is generally larger than a 2x2 voxel square. The actual chance to hit is impossible to quantify as sometimes it hits the target voxel square but one of the voxels in the square is obstructed so it looks like it misses to the player.
TLDR: Hit chances are a reference and nothing more concrete.
There are no hit chances on ranged attacks in OpenXcom, full stop.
Don't try to invent any, and please don't confuse the people even more than they are.
There is also no 2x2 target approximation, nor any +20 magical constants, or anything of that kind.
Just isn't.
Seriously.
OpenXcom can easily show you accuracy of 340% or 10000000% if the modder decides to pump up soldier or weapon stats.
-
And still miss :D
Another other side, there is small probability that if you place in specific place shooter and target then overall number of hits will be similar to to this "percent" show in UI. But again as Meridian said, this is outside of OXC logic a engine do not do any calcinations as this.
-
Bear in mind I haven't looked through the code on this,
As I said, thanks for the clarification, I thought there was some percent math going on with target voxels.
TLDR: Hit chances are a reference and nothing more concrete.
As stated
-
Can't put down Gas cannon from poor guy. I've tried use arrow in right bottom corner to make a space on floor but it's not working =(. So is this bug, feature (Triton space limitation is NOT set to 80), or I just unlucky with my hands and mouse?
(https://i.postimg.cc/PPkFjj81/screen090.png) (https://postimg.cc/PPkFjj81)
-
Can't put down Gas cannon from poor guy. I've tried use arrow in right bottom corner to make a space on floor but it's not working =(. So is this bug, feature (Triton space limitation is NOT set to 80), or I just unlucky with my hands and mouse?
(https://i.postimg.cc/PPkFjj81/screen090.png) (https://postimg.cc/PPkFjj81)
Ctrl+click on it
-
"100%" chance to hit can roll a miss, but it won't very often. The vast majority of times it'll have an actual miss is because it's not aiming at the target. This is an extremely common problem. There's a tiny place where the shot aims for, and a good fraction of shots travel along a line that would intersect that tiny place that the weapon is aiming for, and it's about the size of a 9x9x9 voxel cube. The fraction of shots that intersect this target area is similar to the accuracy as a percentage for most values, especially anywhere from "10%" to "90%" accuracy. Thus while it is not an actual percentage chance to hit, you can pretend it is in your head and your results will not significantly vary from that, provided the target area is inside the hitbox of what you're aiming at.
Sometimes (way too often, in fact), the target area that the soldier aims for is partially or completely protruding from the hitbox of the thing you told them to fire upon. This is especially common when shooting units, as their vanilla hitboxes are a fairly narrow cylinder. If your soldier has greater than 90 applied shot accuracy, their shot trajectory will generally intersect with the small target area they elect to fire upon. If that target area is within the unit's hitbox and it isn't occluded, they will generally hit the unit. If it's outside of the unit's hitbox, they will basically always miss, no matter how many times you play the shot over. The only way to fix it is to fire from a different position, as the way the soldier chooses their target area seems to be based on the position of the target tile relative to the position of the one who is firing. It applies to aliens shooting at you as well--it's very possible to be in a place from which a given alien can't hit you.
When the shot does not intersect with this small target area, it chooses a nearly random trajectory whose angle tends to go wider the lower the shot's effective accuracy. It's more likely to go near the target than it is to go wide, but not by a very big margin. On low accuracy shots (~25 or less), it is possible for the shot to go further than 45º from the target. On high accuracy shots (~75 or more), a straying shot usually won't go more than about 15º from the target, but that's still more than far enough to miss with only 1 tile separation between the shooter and the target unit. Large targets (cyberdiscs, reapers, sectopods), using vanilla hitboxes, the hitboxes are vastly larger than with small units. Because of this, your actual hit rate at shorter ranges (approx. 3-10 tiles distance) varies greatly by target size. For a small unit, hit rate is roughly identical to the rate that the target area is intersected, provided that area is inside the unit's hitbox. For a large unit, stray shots frequently if not usually still hit.
Compared to real life shooting, the X-Com units have abysmal accuracy. But also in real life, chance to hit a target varies greatly by the target's movement. Headshotting a non-moving snakeman at 30 yards with iron sights is a trivial task for a rookie shooter, but trying to hit a snakeman rapidly weaving side to side at 30 yards is very difficult without significant marksmanship training.
Technically speaking, the shot accuracy is not a percent chance to hit. But the actual % chance to hit (the target area) is so similar to the shot accuracy value at most accuracies that it is an effective shorthand to keep in mind either when firing or when explaining shooting strategies. The primary discrepancies are positioning of the target area relative to the target's hitbox (which varies depending on relative position of the target), and hitboxes not matching their sprites.
-
Screenshot or didn't happen.
show exactly save when this behavior happens then we can discus when we can see exactly what code do.
current behavior is same as vanilla and if I recall correct Meridian is fine with it and all glitch it can have,
if you want it change you should send it to OXC not OXCE.
-
Let me back to Naga who used fan as hole and climb up. You said what my drones can do same. But they can't here save file for TWoTS. Drone on the roof of dreadnought, but it couldn't descend down. What I'm doing wrong or may be indecent with Naga still bug?
-
Let me back to Naga who used fan as hole and climb up. You said what my drones can do same. But they can't here save file for TWoTS. Drone on the roof of dreadnought, but it couldn't descend down. What I'm doing wrong or may be indecent with Naga still bug?
They can in the save you provided earlier, attached for reference.
I moved the drone below the fan so you can easily try it.
I don't know what you're doing wrong, probably just different maps behaving differently; I am really not interested in checking everything.
-
Ok, that's explain things, then more question - could it be USO layout bug or feature, which if I understand correctly, present in .rul files? I mean instead of wall in place of fan present hole or vice versa? Because visual style in game is one thing, but floor and walls should be programmed separated in .rul files right? And if wall or block is missing is it possible to move through it even visual it looks like solid object?
-
Ok, that's explain things, then more question - could it be USO layout bug or feature, which if I understand correctly, present in .rul files? I mean instead of wall in place of fan present hole or vice versa? Because visual style in game is one thing, but floor and walls should be programmed separated in .rul files right? And if wall or block is missing is it possible to move through it even visual it looks like solid object?
Ok, my area of responsibility.
Reason of all that is a new USO maps. In a case when one can fly through roof fan, this part is made not as roof, but as wall by author of these maps, Blank. In vanilla maps roof is impassable.
If you think that it is wrong - i may change that.
-
Guys can you explain me how "killed by x-com operatives" penalty applies? Example: I just did pirate ship mission in TWoTS and attempted to save civilian lady by throwing stun grenade to her. Sadly, but she had wounds from enemy and died before I can reach her and use medkit. Final screen calculate her is "killed by x-com operatives". But why? How it works? Game check who last try use grenade, rifle etc and not check what that was not fatal grenade it all? Not a bug, I assume? Or may be will be changed in future? If not, what should I do to avoid such situations - check the human sprite on wounds before using grenades via middle mouse click?
-
It's calculated by "last 'attack' that hit the unit." Even a medikit counts as an 'attack.' And because you knocked them unconscious, it definitely affected them. So, according to the engine, your stun grenade was at fault.
-
Asking it here, not sure what this is OXCE bug (behavior) or mod. TWoTS latest 2.45 attempting to heal civilian body on the ground but it literally missing on floor when I click on aquanaut who staying on it and holding medkit.
Screenshots and save file to check:
(https://i.postimg.cc/R3rT80FD/screen095.png) (https://postimg.cc/R3rT80FD)
P.S.
Additional info: before poor guy get wounded and accidentally shooted near him to kill calcenite 2nd form. May be this effected his body and it's gone? But why then corpse still present on floor with wound mark and missing via inventory screen?
P.P.S.
Updated save file, still strange sprite missing but I can heal a guy.
-
I can see the medikit just fine.
-
Can I change the default working directories? C:\Users\...
-
Yes.
-
Where can I change the path? It doesn't change the game settings.
P.S. It's been dealt with. Just move the folders to the work directory.
-
I'm not talking about medkit, it's missing body of wounded guy on the floor when you use "I" on you aquanaut who step on it.
-
I'm not talking about medkit, it's missing body of wounded guy on the floor when you use "I" on you aquanaut who step on it.
that's normal... same as in TFTD
-
Really? But why? No sprite for dead (wounded) civilian body? Same mechanics like impossible to pick up due to missing 2x2 unit (Hallucinoid or etc)?
-
no sprite
-
Why when I canceled production I'm not getting refund and my money are gone? I understand when I produce multiply items, so no refund for already produced, but when I making single expensive item and it's not ready yet money just gone.
-
same as vanilla
-
Any possibility to change it? May be with some yes/no via main menu option in future OXCE releases?
-
Any possibility to change it? May be with some yes/no via main menu option in future OXCE releases?
It can already be changed. There is a refund attribute in manufacture ruleset.
-
About Hunter Killers. I'm asking myself now - what the reason use dogfight screen when it attacks any x-com craft what have no weapons to protect itself and not have escort too. The result one - you will lose you ship, will you wait until USO kills it eventually or just press self destruct button. But it useful and result could be same if you running out of ammo on you interceptor and enemy USO still not destroyed. May be in future just remove it and use information screen like "You craft were destroyed but enemy USO"? It's just save time. Not great suggestion may be, so glad to hear you opinions or ideas.
-
You have time to Alt-F4 :>
-
Regarding HKs:
Would it be possible for crafts to retain their target after escaping interception?
When a craft is faster than a HK, it can escape the interception. But when landing at the base, crafts slow down.
I have had cases, when a craft ran out of ammo and was caught just as it was landing. It could escape the interception, but the zoom-in for the next interception started before I could order it to go somewhere else, to outpace the UFO.
But because after escaping interception, the craft tries to return to base, it just continued trying to land.
-
I pushed small change yester day to scripts, I allowed to get tag from rule (like RuleArmor or RuleItem) from game object (BattleItem or BattleUnit).
This skip some boilerplate when you want check one tag armor tag from some unit and you need access armor itself before hand.
-
How many interceptors can escort you craft? 2 maximum? Any limitation in code and dogfight phase?
-
At least three, but I bet 6-9.
-
There's not a limit on the number of craft that can follow one, but only 4 are allowed in an interception at once, and you can't bring in new craft unless all your interceptors are at standoff range and you can minimize the windows.
-
There's not a limit on the number of craft that can follow one, but only 4 are allowed in an interception at once, and you can't bring in new craft unless all your interceptors are at standoff range and you can minimize the windows.
Huh, I figured at numbers greater than the the dogfight windows would split 2x3, good to know though :)
-
New OXCE v6.5 is up.
2020-05-08
QoL:
- QoL/Bugfix: User option for palette flicker fix (in options.cfg only): https://openxcom.org/forum/index.php/topic,8212.0.html
- QoL/Bugfix: Don't flash weapon bigobs during autoshots: https://openxcom.org/forum/index.php/topic,8080.0.html
- QoL/Modding: Ability to not follow projectiles (to prevent minigun seizures): https://openxcom.org/forum/index.php/topic,8210.0.html
- Daily Pilot Experience GUI: https://openxcom.org/forum/index.php/topic,8209.0.html
- Added vSyncForOpenGL to advanced user options: https://openxcom.org/forum/index.php/topic,8208.0.html
- Personal equipment templates: https://openxcom.org/forum/index.php/topic,8206.0.html
- Improved scroll-allocation in Research/Manufacture GUIs: https://openxcom.org/forum/index.php/topic,8207.0.html
- Improved display and sorting in Psi/Martial Training GUIs: https://openxcom.org/forum/index.php/topic,8205.0.html
- Option to sort soldiers by "idle days"
- Added mission site despawn penalty indicator: https://openxcom.org/forum/index.php/topic,8204.0.html
- Added slacking indicator: https://openxcom.org/forum/index.php/topic,8203.0.html
- Show number of remaining getOneFrees in TechTreeViewer
- Don't show disabled research as not-yet-researched in TechTreeViewer
- Tiny QoL in manufacturing GUI (scroll from 1 to 10, not to 11)
- Added hotkeys for top-level basescape menu (by fbacall): https://openxcom.org/forum/index.php/topic,8202.0.html
Modding:
- EXPERIMENTAL: Global switch for reactions to melee attacks: https://openxcom.org/forum/index.php/topic,8166.msg127065.html#msg127065
- Armor flag to allow 2 main weapons for xcom (autoequip, built-in weapons): https://openxcom.org/forum/index.php/topic,8214.0.html
- BREAKING CHANGE: sanitized aim penalty for wounded hands: https://openxcom.org/forum/index.php/topic,6459.0.html
- Added custom facility upgrade/build time reduction scaling: https://openxcom.org/forum/index.php/topic,5960.msg127568.html#msg127568
- BREAKING CHANGE: Fixed rounding and scaling of build time reduction: https://openxcom.org/forum/index.php/topic,5960.msg127568.html#msg127568
- Support for surface weapon vapor trail: https://openxcom.org/forum/index.php/topic,7390.msg127428.html#msg127428
- BREAKING CHANGE: Soft/hard upper limit option for soldier transformations: https://openxcom.org/forum/index.php/topic,6331.msg127435.html#msg127435
- Added unmanned UFO flag: https://openxcom.org/forum/index.php/topic,8213.0.html
- Added listOrder to soldier bonuses: https://openxcom.org/forum/index.php/topic,7405.msg127418.html#msg127418
- Sight range/chance for base facilities: https://openxcom.org/forum/index.php/topic,8119.msg127420.html#msg127420
- Option for civilians to pick up weapons too ... this one is a lot of fun ;) https://openxcom.org/forum/index.php/topic,6882.msg127421.html#msg127421
- Option to inform players about important event gateways in TTV: https://openxcom.org/forum/index.php/topic,7215.msg127424.html#msg127424
- Ability to filter regions and mission zones in geoscape debug mode
- Draw inventory grid labels using listOrder, not alphabetically
- Improved grid label rendering (first draw the grid lines, then the items, and grid labels as last)
- Changed how canBeBuiltOver and buildOverFacilities interact: https://openxcom.org/forum/index.php/topic,8017.msg125175.html#msg125175
- Avoid rounding down contry funding change to zero
- Allow recovery of live aliens as items: https://openxcom.org/forum/index.php/topic,6868.msg109164.html#msg109164
- Added new type of geoscape soldier recovery stat (existing: fatal wound recovery, mana recovery; new: health/HP recovery)
- Added facility triggers to Event, Arc and Mission Scripts: https://openxcom.org/forum/index.php/topic,7096.msg127425.html#msg127425
Hybrid modding (by Finnik):
- Added "allowAlienBasesOnWrongTextures" global switch
- Support for fake underwater alien bases
- Support for locking fake underwater XCOM bases behind a research gate
- BREAKING CHANGE: Support for UFO landing on fake water texture
- Support for UFO splashdown survival (over fake water texture)
Scripting (by Yankes and memmaker):
- Add support for script tags in RuleMod (i.e. global tags)
- Added newTurnUnit and newTurnItem calls before the first player phase
- Ability to access ruleset objects by name (items, armors, soldiers, skills)
- Ability to change spawn unit
- Ability to access inventory items by item name, inventory slot name or both
- Added a unit reference to createItem script hook when the unit is known (aliens, hwps, fixed weapons)
- Psi attack formula now fully scriptable (added second hook handling psi weapon attributes)
- Ability to consider weapon, ammo, attack type and soldier skill in bonus formulas (e.g. bonus to accuracy, bonus to power, etc.)
Bugfixes:
- Fixed wrong (abort) cutscene playing on forced mission loss
- Improved checks handling unpriming of grenades
- Fix sorting by stats for dead soldiers
- Don't show negative psi skill in transformations GUI
- Make sure the UFO HK attacks its primary target first!
- Fix UFO HK not able to outrun more than 1 interceptor
- Re-added "missileAttraction" attribute (was removed by mistake during merge)
- Do not bind keyboard events to unrecognized keys
- Autoequip improvement (now considers allowed slots)
- Fixed inventory layout saving (it was not possible to remove saved armor type)
- Fixed road crossing glitch after reload
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
OpenXcom ruleset validator has been updated too: https://openxcom.org/forum/index.php/topic,6552.0.html
Updated ruleset reference: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom) (https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom))
I will be adding descriptions of individual features as separate forum posts over the weekend... come back on Monday Saturday 16.5.2020 to learn more!
-
- BREAKING CHANGE: sanitized aim penalty for wounded hands
if a weapon is not in your hands (e.g. a special weapon) it doesn't suffer penalty from fatal wounds on hands anymore
- BREAKING CHANGE: Fixed rounding and scaline of build time reduction
these are bugfixes really, but listed here for completeness;
the build time reduction when upgrading base facilities should now be calculated properly in all cases, modders may want to review their build time costs when upgrading (e.g. weed/boom farms in PirateZ)
- BREAKING CHANGE: Soft/hard upper limit option for soldier transformations
soldier transformations supported only hard limits on stat caps... meaning stats were always capped at maximum
however training in missions allows to go slightly over the maximum
to not lose this useful quirk, the transformations can be configured to have soft limits = if the soldier is already above the maximum before the transformation, don't reduce his overflown stats
soft limits are now applied by default when transformation doesn't change the soldier type
can be changed by the modder at will
- BREAKING CHANGE: Support for UFO landing on fake water texture
this is the only real breaking change... and only for hybrid mods
until now land textures and fake underwater globe textures were equal for UFO landing... UFO didn't consider them (fake underwater was the same for them as land)
from now on, the modder can specify the chance of landing on land vs landing on fake underwater texture
(don't forget to balance your missionZones for all regions, so that they contain enough fake underwater texture areas if you haven't done that already!)
fakeWaterLandingChance: 0 = landing allowed only on proper land texture (default)
fakeWaterLandingChance: 100 = landing allowed only on fake underwater texture
fakeWaterLandingChance: 50 = 50% chance to land on one or another.... this is very roughly equal to the previous behavior
-
- (Intentionally) Crash on missing research ruleset (instead of just logging and ignoring it)
I used not existing tech for mission triggers. Those missions should show up again and again until they are played/won once.
research:
- name: STR_SMUGGLER_DONE
dependencies:
- STR_NEVER
missionScripts:
- type: bonus_smuggler
researchTriggers:
STR_SMUGGLER_DONE: false
...
alienDeployments:
- type: STR_SMUGGLERISLAND
unlockedResearch: STR_SMUGGLER_DONE
...
How do I solve this Problem now?
-
Create this research, make it "needItem: true"
-
Or make it depend on itself.
-
I have option for auto check version, but when I start the OXCE it still says me what it on latest version. What I'm doing wrong?
-
I have option for auto check version, but when I start the OXCE it still says me what it on latest version. What I'm doing wrong?
Auto-update is always released later than the manual download.
-
Is there any way to use a soldier transformation to remove a commendation?
Is there any way to store the lowest hp a soldier was at in battle(probably doable with scripts, will figure it out), and then use it as the criteria for a commendation?
I want to implement something like war wounds, where if the soldier gets too low on hp during a battle, they get a commendation with big stat penalties as if they received a lasting injury which then has to be removed with a soldier transformation.
-
Is there any way to use a soldier transformation to remove a commendation?
No.
Is there any way to store the lowest hp a soldier was at in battle(probably doable with scripts, will figure it out), and then use it as the criteria for a commendation?
No.
-
k.
-
Vadracas.
Soldier transformations remove all commendations if they have "reset = true". Or you can apply a soldier bonus to negate the commendation bonus, and forbid the transformation from happening again.
Scripts that give/remove commendations are not possible. Scripts that permanently modify stats without using commendations likely are possible, but it's an ugly hack. totalTimesWounded or totalHit5Times could substitute for your relative hp commendation.
-
Soldier transformations remove all commendations if they have "reset = true". Or you can apply a soldier bonus to negate the commendation bonus, and forbid the transformation from happening again.
They don't remove any commendations.
Only transformation soldier bonuses are removed.
Commendations (and commendation soldier bonuses) are NOT removed.
-
How many turns is allowed per mission until game crash? 999? More? If I stay in ship cowardly and leave it and just waiting while aliens come to me.
-
How many turns is allowed per mission until game crash? 999? More? If I stay in ship cowardly and leave it and just waiting while aliens come to me.
I don't know, I never tried it.
Let us know if you find out.
-
I tried looking at it. I do not know YAML, but if I understand this line from SavedBattleGame.cpp correctly,
_turn = node["turn"].as<int>(_turn);then _turn is an integer.
So presumably something strange would happen if the mission took as long, as is integer in that YAML. Which is presumably either 2 147 483 647 or 4 294 967 295, depending on whether or not the integer is signed.
-
Save file is only small part possible "crash" sources, you can easy play game not saving at all.
To see if any thing crash you need track all use of this variable and see if any use handle correctly big numbers.
Theoretical example could be "Next Turn Screen" have hardcoded space for only 4 characters to display, then if you send value 10000 it could crash.
This could probably happens if we would use C but in C++ many buffers automatically grown to meet required space.
-
How experience system working when you use grenades - who get experience, aquanaut who prime it or aquanaut who pick it and threw? Instant grenades mode is off and enemy hit by blast radius.
-
aquanaut who threw, no skills are needed to prime in this game.
-
Ok, thank you, forget ask about disturbance grenades - same algorithm I assume? When enemy step on and it triggered experience goes to person who threw?
-
Pretty sure throwing exp comes from grenades in this way: In the ruleset, the grenade is tagged to give throwing Exp, then, once the grenade is primed, when you throw the grenade it will give throwing Exp.
I think-but this has been modified before and I'm not 100% sure this is how it works.
-
I added new functionality to OXCE nightly:
For many list like `requires` or `requiresBuy` you can use new syntax like:
Base mod:
items:
- type: STR_PISTOL
requiresBuy:
- STR_X
- STR_Y
- type: STR_PSI_AMP
requires:
- STR_X
- STR_Y
Another mod:
items:
- type: STR_PISTOL
requiresBuy: !add
- STR_Z
- type: STR_PSI_AMP
requires: !remove
- STR_Y
Now `STR_PISTOL` need have additionally need `STR_Z` AND `STR_X`, `STR_Y` to buy
But `STR_PSI_AMP` need only `STR_X` from research.
With this you can easier add or remove some positions from list without know full lists.
This reduce many cases where mods extension could easy break by small change in main mod.
For now only two `!add` and `!remove` basic operations are supported but in future it will be more complex too available (like `!replace`).
As some list have very strick order I could not add for now way to override them but in future depending on demand I could add ways to override them too.
-
Hello, I joined because I wanted to ask something: are smoke grenades supposed to hurt units with normal and personal armor? (and some of the weaker aliens like Sectoids?) They don't in the vanilla game/OpenXcom and I haven't been able to find anything about it online. Power Suit units and Tanks don't get damaged at all, so I'm not sure if this is a bug or an intended feature of OXCE.
-
Hello, I joined because I wanted to ask something: are smoke grenades supposed to hurt units with normal and personal armor? (and some of the weaker aliens like Sectoids?) They don't in the vanilla game/OpenXcom and I haven't been able to find anything about it online. Power Suit units and Tanks don't get damaged at all, so I'm not sure if this is a bug or an intended feature of OXCE.
Hi,
smoke grenades are not supposed to hurt anyone.
They also don't hurt anyone in OXCE, same as in OpenXcom and in the original... unless you have specifically modded them to do some damage.
M.
-
Smoke itself causes small amount of stun damage to units in it at the start of their turn which ignores armor but not resists. So if an armor says it takes 0% smoke damage, it will take 0% smoke damage. If it doesn't mention smoke damage, it will take 100% smoke damage, even if it has 50 armor. Tanks also have resists, they're just not shown in the UFOpaedia in vanilla. The grenade does no damage, only the smoke it causes.
-
Smoke itself causes small amount of stun damage to units in it at the start of their turn which ignores armor but not resists. So if an armor says it takes 0% smoke damage, it will take 0% smoke damage. If it doesn't mention smoke damage, it will take 100% smoke damage, even if it has 50 armor. Tanks also have resists, they're just not shown in the UFOpaedia in vanilla. The grenade does no damage, only the smoke it causes.
Which is exactly the same as in the original and in OpenXcom.
It was really not necessary to write it here and confuse the poor guy who asked even more.
-
On a reread he said "They don't in vanilla" so yeah "same as vanilla" is the best answer.
-
Hi,
smoke grenades are not supposed to hurt anyone.
They also don't hurt anyone in OXCE, same as in OpenXcom and in the original... unless you have specifically modded them to do some damage.
M.
Alright, I did a little bit of testing (downloaded latest OXCE version 6.5, got the files from steam, installed on a clean computer so no mods or previous saves). And it seems like the 'instant grenades' option turns smoke grenades into normal grenades in OXCE (the damage is applied on hit, same as normal grenades, and the ground gets visually scorched alongside the smoke).
I then downloaded OpenXcom on another computer and the instant smoke grenades seemed to work properly there (no damage, no visual changes other than the smoke).
Disabling instant grenades in the OXCE version of the game makes smoke grenades work 'properly' again (not sure if it affects any other weapons, I only started playing a week ago and haven't gotten very far).
This is all in the base game, I have no other mods installed and haven't really touched the other options (yet).
-
Alright, I did a little bit of testing (downloaded latest OXCE version 6.5, got the files from steam, installed on a clean computer so no mods or previous saves). And it seems like the 'instant grenades' option turns smoke grenades into normal grenades in OXCE (the damage is applied on hit, same as normal grenades, and the ground gets visually scorched alongside the smoke).
I then downloaded OpenXcom on another computer and the instant smoke grenades seemed to work properly there (no damage, no visual changes other than the smoke).
Disabling instant grenades in the OXCE version of the game makes smoke grenades work 'properly' again (not sure if it affects any other weapons, I only started playing a week ago and haven't gotten very far).
This is all in the base game, I have no other mods installed and haven't really touched the other options (yet).
This seems to be a bug with special grenades in general. I was playing Equal Terms and discovered, that incendiary grenades from it do a large explosion when on instant grenades, while without instant grenades, they just create a small patch of fire.
-
...it seems like the 'instant grenades' option turns smoke grenades into normal grenades in OXCE (the damage is applied on hit, same as normal grenades, and the ground gets visually scorched alongside the smoke).
Thanks for the report. This is indeed not intended.
(I've never used the instant grenades option, so I never noticed.)
It will be fixed.
-
Question about night vision. How to change it for on/off mode with keyboard? I mean not press and hold space bar all time. I know about threshold value too, it's great but can't find exactly how to turn on/off it by single keyboard button press. Sorry if it has been already answered.
-
Question about night vision. How to change it for on/off mode with keyboard? I mean not press and hold space bar all time. I know about threshold value too, it's great but can't find exactly how to turn on/off it by single keyboard button press. Sorry if it has been already answered.
Scroll Lock
-
This can be changed in the options also, I have mine configured for N.
-
Thank you guys, I have desktop and laptop, but last one has not that button, thanks again, gotta set for it something else than Scroll Lock :)
-
About experience. I just found what when my aquanaut threw Magna-pack explosive to enemy, he's not get experience after enemy get killed by explosion (used ctrl+e to check who not get exp yet). The pack was primed by another guy. What I'm doing wrong or why it happened? A few posts before people said what person who throw will get experience. But seems it's not working like mentioned. Or this is "hidden" throwing experience what not affected by ctrl+e combination and all aquanauts need shoot and hit target?
-
It's a bug in oxce 6.5, will be fixed in oxce 6.5.1.
-
A very small request: please from that version on may we get a changelog.txt file, on win and linux?
-
Here you go ;)
https://openxcom.org/forum/index.php/topic,6586.495.html
-
A very small request: please from that version on may we get a changelog.txt file, on win and linux?
You don't.
Changelog is here on the forum.
-
New OXCE v6.5.1 is up.
2020-05-21
QoL:
- Option to choose preferred hand for reactions (right-click on the hand in the battlescape HUD); indicator is moddable via sprite called "reactionIndicator" (same size as bigobs)
- Civilians and summoned player units now kindly return any borrowed xcom equipment
Modding:
- Separate option for civilians picking up weapons: https://openxcom.org/forum/index.php/topic,6882.msg127660.html#msg127660
- Moddable recommended user options ('recommendedUserOptions'): https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Recommended.2FFixed_User_Options
- Option to include soldier bonuses in minStats check in transformations ('includeBonusesForMinStats'): https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Soldier_Transformation
- Option to modify ruleset lists without completely redefining them (!add and !remove YAML tags) : https://openxcom.org/forum/index.php/topic,6586.msg127524.html#msg127524
Bugfixes:
- Fixed recovery of the last bleeding alien
- Fixed grenades not giving experience
- Fixed "instant grenades"
- Fixed facility triggers in mission/arc/event scripts
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
Are recommended user options taken into account when you revert options/config to default or are there any plans to introduce a seperate button for this?
I've missed this, what was the bug that was fixed concerning instant grenades?
-
Are recommended user options taken into account when you revert options/config to default
yes
or are there any plans to introduce a seperate button for this?
no
I've missed this, what was the bug that was fixed concerning instant grenades?
Instant smoke grenades don't kill you anymore.
-
I just finished "training" mission in TWoST killing few creepers. I had four aquanauts on board with gas cannons loaded explosives rounds. All what I did is killing few enemies until all get experience. After I abort the mission. But I was surprised when on statistic mission screen I got throwing accuracy bonus for all my guys. I'm not threw any items just grab and put down same cannons while rotating aquanauts in fire queue. Is it normal? Is this just bonus throwing experience or may be another small bug? Long ago I've read what you guys (developers of OXCE) removed free throwing experience bug fixing exploit using for throw just random staff like flares and e.t.c. that why I'm asking.
Update:
Another mission, guys who used gas cannons and keeps them in hands all battle got throwing experience too. It' may be "feature" of projectile weapons, because rounds using parabola trajectory what count as throwing?
-
Hi Meridian, I am getting some strange crashes with my mod with the upgrade to OXCE 6.5.1 It didn't happen before with 6.5
Firstly, did you modified any code for ArmorTransformation?
I am getting this list of warning in the bug report. It never happen before.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_UNDERWATERTEST. Please review the ruleset.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_UNDERWATERTESTMIDDEEP. Please review the ruleset.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_UNDERWATERTESTREALLYDEEP. Please review the ruleset.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_LANDONLY. Please review the ruleset.
Second for soldier transformation, for forbiddenPreviousTransformations and requiredPreviousTransformations, I am getting a node error.
Please verify. Thanks. I have included by error log.
-
Hi Meridian, I am getting some strange crashes with my mod with the upgrade to OXCE 6.5.1 It didn't happen before with 6.5
Firstly, did you modified any code for ArmorTransformation?
I didn't. Yankes probably did.
I am getting this list of warning in the bug report. It never happen before.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_UNDERWATERTEST. Please review the ruleset.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_UNDERWATERTESTMIDDEEP. Please review the ruleset.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_UNDERWATERTESTREALLYDEEP. Please review the ruleset.
[22-05-2020_03-38-06] [ERROR] There are invalid/obsolete attributes in starting condition STR_LANDONLY. Please review the ruleset.
These warnings exist already since May 2019, more than a year.
Second for soldier transformation, for forbiddenPreviousTransformations and requiredPreviousTransformations, I am getting a node error.
Please verify. Thanks. I have included by error log.
Looks like YAML syntax error in the ruleset.
-
Another mission, guys who used gas cannons and keeps them in hands all battle got throwing experience too. It' may be "feature" of projectile weapons, because rounds using parabola trajectory what count as throwing?
Yes, it's described here: https://openxcom.org/forum/index.php/topic,4230.0.html
-
Is anyway lock difficulty of mod using rule set files? Like example, when player start the game he has no option but one difficulty only and Ironman set on and can not be changed (buttons grey out).
-
Is anyway lock difficulty of mod using rule set files? Like example, when player start the game he has no option but one difficulty only and Ironman set on and can not be changed (buttons grey out).
You can change difficulty coefficients so that all difficulties are the same... like for example in the 40k mod.
Ironman cannot be fixed.
-
Promotion question. I've set "only soldiers who were on battlefield promotion" on, but often when I land and just abort the mission people get promoted which unfair. Is any way prevent this or may be in future release OXCE engine will promoted people who only get experience? This last one is my suggestion of course if its possible to make.
-
yeah, we could rename it from "only soldiers who were on battlefield promotion" to "only soldiers who were on battlefield and got some experience promotion"
-
New OXCE v6.5.3 is up.
2020-05-28
QoL:
- Field Promotions user option update (soldiers now need to gain experience during the mission to be eligible for promotion)
Scripting:
- Allowed scripts to turn off unit status indicators
Bugfixes:
- Fixed draw order of units on stairs (was broken in 6.5.1)
- Fixed splitting Unicode strings (e.g. russian soldier names)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
- Option to choose preferred hand for reactions (right-click on the hand in the battlescape HUD); indicator is moddable via sprite called "reactionIndicator" (same size as bigobs)
Just noticed this. I LOVE IT! Million thanks for the continued OXCE goodies.
-
grateful for the continued efforts. It's like opening presents on a regular basis.
-
grateful for the continued efforts. It's like opening presents on a regular basis.
Oh, I found it but I thought what this yellow dot is disable you weapon. I read wiki what says what game prefer right hand for reaction. Glad what this feature exists now.
Gentlemen, apologies for asking this again, but this "accuracy" number what shows when you aiming with soldier (aquanaut) totally confuse me now. On sniper rifles it could be more than 100% which literally illogical, but even with this, for example 120%, my aquanauts missing what makes me angry. How exactly aiming working and what this numbers represents? Dose OXCE calculate this number and firing accuracy in soldiers (aquanauts) stats and make real % chance of hit which hidden? If I'm right, I have request make new option for future OXCE releases what will show real fully calculated number same for shooting and throwing. That will be great, it it's possible due to game engine and limitations.
-
it's just 120, not 120%... forget the %
openxcom doesn't calculate any chance to hit for ranged weapon, that concept doesn't exist
https://www.ufopaedia.org/index.php/Accuracy_formula#Use_of_Accuracy
-
I just had a civilian steal an alien artifact during a mission - said artifact wasn't recovered during debriefing. Would it be possible to recover weapons picked up by civilans at the end of a mission?
-
I just had a civilian steal an alien artifact during a mission - said artifact wasn't recovered during debriefing. Would it be possible to recover weapons picked up by civilans at the end of a mission?
You're the police, stop them :)
-
I just had a civilian steal an alien artifact during a mission - said artifact wasn't recovered during debriefing. Would it be possible to recover weapons picked up by civilans at the end of a mission?
they already nicely return xcom stuff
they don't return alien stuff... they can steal it just as you can... implemented according to requirements
-
they already nicely return xcom stuff
they don't return alien stuff... they can steal it just as you can... implemented according to requirements
I've just discussed it with Dioxine. The conclusions were as follows:
- In XCF, it's fine as it is. Alien tech gets stolen, pops out somewhere later - the usual. The drawback is that it incentivizes stunning civilians, which is cringy, but I can live with it.
- In Piratez, all civilians (or most) will be recovered as some items (basically "thank you for saving me" letter or something like that), and therefore you will get their stuff. The drawback is that you'll get all civilians' weapons, but these are usually very simple and inexpensive, so whatever.
-
- In Piratez, all civilians (or most) will be recovered as some items (basically "thank you for saving me" letter or something like that), and therefore you will get their stuff. The drawback is that you'll get all civilians' weapons, but these are usually very simple and inexpensive, so whatever.
civilians don't pick up items in piratez
and I didn't understand that part with "getting their stuff"... how are you gonna get that without killing/stunning them?
-
civilians don't pick up items in piratez
But they will (assuming I understood Dio correctly).
and I didn't understand that part with "getting their stuff"... how are you gonna get that without killing/stunning them?
Civilians are spawned with items and if they get recovered, they will also bring their weapons.
(This is based on what Dio said, I haven't studied this and may well be wrong.)
-
Yesterday on OXCE nightly was push change that make checking items linked to units and armors (e.g. corpses). If there is invalid items game will throw error on load.
As side effect, armors that had storage item `STR_NONE` can now remove it as it by definition not exists at all, and game work fine if you do not define any thing for storage item (but if you use incorrect item then game will not load it).
-
I am not up-to-date on the known issues list for OXCE, but melee weapons and units on stairs don't seem to get along. Is there any way to fix this?
-
What version you use? Some have bug that make draw unit incorrectly and probably affect hit logic too
-
I pushed another expansion of `!add` tags to rule files, added too special tag `!info` to check what is supported.
sometype:
- type: X
property: !info
- A
This will give in logs line like:
Options aviable for X at line 3 are: !!seq !add !remove
-
Playing TWoTS latest version and experimenting with debug mode I've found what gas tanks with 12 rounds maximum not spend their ammo when shooting. Is it should be because of debug mode activated? Can't remember now what happened with aquanaut ammo, but 100% sure about those tanks.
-
Playing TWoTS latest version and experimenting with debug mode I've found what gas tanks with 12 rounds maximum not spend their ammo when shooting. Is it should be because of debug mode activated? Can't remember now what happened with aquanaut ammo, but 100% sure about those tanks.
No ammo will be spent in debug mode.
-
What version you use? Some have bug that make draw unit incorrectly and probably affect hit logic too
6.5.1 / 2020-05-21
Having trouble hitting units on stairs with melee attacks (as in, the hit sound plays, but no damage is dealt).
-
6.5.1 / 2020-05-21
Having trouble hitting units on stairs with melee attacks (as in, the hit sound plays, but no damage is dealt).
(hopefully) Fixed in 6.5.3 / 2020-05-28
-
Version 6.5.3.1 aquanauts who has melee and ranged weapon in hands always use ranged for reaction regardless of choosing melee by left click (yellow dot set on knife). Bug or selecting weapon for reaction fire works only for ranged version? It will be great use this feature for melee reaction as well, especially if second weapon ranged or both hands used for melee only.
-
it works for melee too
if melee can't be used (for example if you are not in melee range), ranged will be used instead
-
Ok, that explain things. But how make use melee only avoiding spend TU on ranged? For example aquanaut kneeling with knife and harpoon in other hand and waiting while creeper come in close range to react with knife. Is only way then unequip harpoon or unload it? It's kinda inconveniently because I need spend TU putting weapon down and picking it up at new turn. So option do NOT use ranged if it has ammo and melee preferred for reaction will be very useful.
P.S.
Suggestion. Red dot on weapon what disable it completely for reaction fire:
(https://i.postimg.cc/NyhzPPXW/screen112.png) (https://postimg.cc/NyhzPPXW)
-
I am not sure where to post this, this concerns scripts (shields in particular). I'm playing XCF right now and had a sectiod turn around and reaction fire upon moving after depleting it's shield.
It faced away from my agent and did not reaction fire when I shot at it and depleted it's shield, but it turned around and reaction fired when I subsequently moved the agent. I'm not sure if this is a limitation of the shield script, intended or simpyl a bug. Can somebody shed some light onto this?
-
I am not sure where to post this, this concerns scripts (shields in particular). I'm playing XCF right now and had a sectiod turn around and reaction fire upon moving after depleting it's shield.
It faced away from my agent and did not reaction fire when I shot at it and depleted it's shield, but it turned around and reaction fired when I subsequently moved the agent. I'm not sure if this is a limitation of the shield script, intended or simpyl a bug. Can somebody shed some light onto this?
This is unrelated to shields, it happens also without shields.
It's a known quirk of OXC and probably also of the original game.
-
Ah, okay, that's good to know. Thanks!
-
No reaction after shot but reaction after move is not quirk but fundamental behavior of reaction.
Every unit have ReactionScore value that is based on current TU.
When you have highest reaction nobody can attack you, but if you fall bellow other start shoot at you.
In this case after shoot you have still initiative because your reaction score was bigger, but after one step alien have chance to react.
You can image this like:
Hitting target inform him that you are there, and he want to turn araound but he is too slow to have any effect. When you move, you giving him this precious second to react and shoot back at you.
-
I'm aware of that. It's just that the TU reduction from shooting was quite substential, while the one from walking was not. Must have been right on the edge.
BTW, I just discoverd that during outfitting/deployment the numbers indicating how many items are in a pile vanish if you switch to a player unit that has been spawned for that mission and then switch back to your soldiers.
Case in point would be the "David Vincent" mission in XCF. If during deployment you switch to David Vincent (unit can't access your items, i.e. ground is empty) and then switch forward/backward to your units the items on the ground are missing the numerical indicators. They only reappear if you click the "scroll right" button (which probably redraws them).
EDIT:
I'm also having some trouble with units on slopes, I think the drawing order is a bit off:
(https://abload.de/thumb/screen011u1j6j.png) (https://abload.de/image.php?img=screen011u1j6j.png)
-
EDIT:
I'm also having some trouble with units on slopes, I think the drawing order is a bit off:
fixed in oxce v6.5.3
-
I have trouble with latest builds on linux (6.5.5 including latest daily) with Area51 mod
The error I see: error processing 'ZOMBIE_ARMOR' in armors: Item STR_ZOMBIE_CORPSE not found
Logfile:
[01-07-2020_19-42-39] [INFO] OpenXcom Version: Extended 6.5.5 (v2020-06-21)
[01-07-2020_19-42-39] [INFO] Platform: Linux
[01-07-2020_19-42-39] [INFO] Data folder is:
[01-07-2020_19-42-39] [INFO] Data search is:
[01-07-2020_19-42-39] [INFO] - /home/zx/.local/share/openxcom/
[01-07-2020_19-42-39] [INFO] - /usr/local/share/openxcom/
[01-07-2020_19-42-39] [INFO] - /usr/share/openxcom/
[01-07-2020_19-42-39] [INFO] - /usr/local/share/openxcom/
[01-07-2020_19-42-39] [INFO] - /usr/share/openxcom/
[01-07-2020_19-42-39] [INFO] - ./
[01-07-2020_19-42-39] [INFO] User folder is: /home/zx/.local/share/openxcom/
[01-07-2020_19-42-39] [INFO] Config folder is: /home/zx/.config/openxcom/
[01-07-2020_19-42-39] [INFO] Options loaded successfully.
[01-07-2020_19-42-39] [INFO] SDL initialized successfully.
[01-07-2020_19-42-39] [INFO] SDL_mixer initialized successfully.
[01-07-2020_19-42-39] [INFO] Attempted locale: en_US.utf8
[01-07-2020_19-42-39] [INFO] Detected locale: en_US.utf8
[01-07-2020_19-42-39] [INFO] Attempting to set display to 1280x800x32...
[01-07-2020_19-42-40] [INFO] Display set to 1280x800x32.
[01-07-2020_19-42-40] [INFO] Loading data...
[01-07-2020_19-42-40] [INFO] Scanning standard mods in '/usr/share/openxcom/'...
[01-07-2020_19-42-40] [ERROR] Invalid standard mod 'Area51', skipping.
[01-07-2020_19-42-40] [INFO] Scanning user mods in '/home/zx/.local/share/openxcom/'...
[01-07-2020_19-42-40] [INFO] Active mods:
[01-07-2020_19-42-40] [INFO] - xcom1 v1.0
[01-07-2020_19-42-40] [INFO] - area51 v0.972
[01-07-2020_19-42-40] [INFO] Loading rulesets...
[01-07-2020_19-42-41] [ERROR] There are invalid/obsolete attributes in starting condition STR_XENOPHOBIA_A. Please review the ruleset.
[01-07-2020_19-42-41] [ERROR] There are invalid/obsolete attributes in starting condition STR_XENOPHOBIA_B. Please review the ruleset.
[01-07-2020_19-42-41] [ERROR] There are invalid/obsolete attributes in starting condition STR_XENOPHOBIA_C. Please review the ruleset.
[01-07-2020_19-42-41] [ERROR] Crossing the prime meridian in mission zones requires a different syntax, region: STR_SOUTH_ATLANTIC, zone: 1, area: 6, lonMin: 359.82, lonMax: 0.95
[01-07-2020_19-42-41] [ERROR] Wrong example: [350, 8, 20, 30]
[01-07-2020_19-42-41] [ERROR] Correct example: [350, 368, 20, 30]
[01-07-2020_19-42-41] [ERROR] Error processing 'ZOMBIE_ARMOR' in armors: Item STR_ZOMBIE_CORPSE not found
-
Find this:
- type: ZOMBIE_ARMOR
spriteInv: INV_ZOMBIE
spriteSheet: ZOMBIE.PCK
corpseBattle:
- STR_ZOMBIE_CORPSE
in armors_Area_51.rul, and delete the last two lines to get this:
- type: ZOMBIE_ARMOR
spriteInv: INV_ZOMBIE
spriteSheet: ZOMBIE.PCK
-
delete the last two lines to get this:
Thanks, that helped. :)
-
I'm getting random tab-outs/minimize to desktop during gameplay and i'm not sure if this is related to me upgrading to 6.5.3 - anybody having similar issues?
-
I am currently encountering segfaults on 6.5.3 when the game tries to recover panicking/surrendering units that can transform and have a valid
corpseBattle:
entry. Case in point would be a panicking Space Technomad in XCF, see here (https://openxcom.org/forum/index.php/topic,5047.msg129515.html?PHPSESSID=oukgnfq4tepinfcvqih5s7ff3c#msg129515) and follow-up here (https://openxcom.org/forum/index.php?PHPSESSID=oukgnfq4tepinfcvqih5s7ff3c&?topic=5047.msg129583#msg129583). An invalid/non-existing item doesn't lead to a crash.
Is this a known problem?
-
Is this a known problem?
Can you provide the log file?
There is a known issue, but it should be super rare.
-
[08-07-2020_12-41-08] [INFO] SDL_mixer initialized successfully.
[08-07-2020_12-41-20] [FATAL] A fatal error has occurred: Segmentation fault.
[08-07-2020_12-41-20] [FATAL] 0x5a1100 OpenXcom::CrossPlatform::stackTrace(void*)
[08-07-2020_12-41-20] [FATAL] 0x5a1f70 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[08-07-2020_12-41-20] [FATAL] 0x41c7f0 signalLogger(int)
[08-07-2020_12-41-20] [FATAL] 0x97ffe0 OpenXcom::UfopaediaStartState::think()
[08-07-2020_12-41-20] [FATAL] 0x76e471cc _C_specific_handler
[08-07-2020_12-41-20] [FATAL] 0x76e5be00 _chkstk
[08-07-2020_12-41-20] [FATAL] 0x76e2fed0 RtlInitializeResource
[08-07-2020_12-41-20] [FATAL] 0x76e5b510 KiUserExceptionDispatcher
[08-07-2020_12-41-20] [FATAL] 0x5265d0 OpenXcom::DebriefingState::recoverAlien(OpenXcom::BattleUnit*, OpenXcom::Base*)
[08-07-2020_12-41-20] [FATAL] 0x527920 OpenXcom::DebriefingState::prepareDebriefing()
[08-07-2020_12-41-20] [FATAL] 0x52ca20 OpenXcom::DebriefingState::DebriefingState()
[08-07-2020_12-41-20] [FATAL] 0x510a50 OpenXcom::BattlescapeState::finishBattle(bool, int)
[08-07-2020_12-41-20] [FATAL] 0x5b9360 OpenXcom::Game::run()
[08-07-2020_12-41-20] [FATAL] 0x41c950 SDL_main
[08-07-2020_12-41-20] [FATAL] 0x981b10 console_main
[08-07-2020_12-41-20] [FATAL] 0x981c30 WinMain
[08-07-2020_12-41-20] [FATAL] ??
[08-07-2020_12-41-20] [FATAL] ??
[08-07-2020_12-41-20] [FATAL] 0x76ce5560 BaseThreadInitThunk
[08-07-2020_12-41-20] [FATAL] 0x76e43710 RtlUserThreadStart
[08-07-2020_12-41-23] [FATAL] OpenXcom has crashed: Segmentation fault.
That should be the relevant part, let me know if you need the rest of the log or the save file.
-
That should be the relevant part, let me know if you need the rest of the log or the save file.
Save would be nice.
-
This should work without any mods beside XCF (at least it does for me).
Segfault happens in XCF 1.4 if you destroy the bot, leading to the other enemy units surrendering.
A workaround - whether intended or not - has been introduced in XCF 1.4a, where the corpseitem for CYBERWEB_SPACE_TECHNOMAD has been changed from STR_CYBERWEB_TECHNOMAD_CORPSE to STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE (which is not defined). Replacing STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE with any valid item definition leads to a segfault upon enemy units surrendering.
-
doesn't crash for me
which oxce build are you using exactly? (exact package download name pls)
-
Extended-6.5.3-01283d3a0-2020-05-28-win64.7z
If you're using 1.4a, can you replace armors_XCOMFILES.rul with the one attached to this post?
For some reason in 1.4a the mission also doesn't automatically end upon destroying the bot, but the game crashed upon ending the turn (which leads to the units surrendering).
EDIT:
Just double-checking, this is the bot that needs to be destroyed:
(https://abload.de/thumb/screen000b8k79.png) (https://abload.de/image.php?img=screen000b8k79.png)
-
New OXCE and XCF do not crash for me.
-
Extended-6.5.3-01283d3a0-2020-05-28-win64.7z
I'm using the same one, with XCF openxcom_xfiles_1.4.zip from mod.io, but no crash.
It's quite likely that rare known bug I mentioned earlier.
-
If you're using 1.4a, can you replace armors_XCOMFILES.rul with the one attached to this post?
For some reason in 1.4a the mission also doesn't automatically end upon destroying the bot, but the game crashed upon ending the turn (which leads to the units surrendering).
With XCF openxcom_xfiles_1.4a.zip + your custom armors_XCOMFILES.rul it does crash.
And it's not the rare known bug.
It's simply that item "STR_CYBERWEB_SPACE_TECHNOMAD" does not exist, so the game cannot check if the alien should be transformed into items or not.... this feature here highlighted in yellow: https://openxcom.org/forum/index.php/topic,6868.msg127441.html#msg127441
-
But that's the case for 1.4 as well as 1.4a - the only difference is that the corpseitem exists in 1.4 (and crashes the game) and doesn't in 1.4a.
The only thing I did was change the corpseitem.
Why does the corpseitem make any difference if the unit in question is surrendering? And why does a valid corpseitem crash the game, while using an invalid one doesn't?
EDIT:
This is the armordefinition in question (from 1.4a):
- type: STR_CYBERWEB_SPACE_TECHNOMAD_ARMOR
spriteSheet: CYBERWEB_SPACE_TECHNOMAD.PCK
spriteInv: inventory_SPACE_TECHNOMAD
corpseBattle:
- STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE
STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE does not exist. This doesn't crash the game.
- type: STR_CYBERWEB_SPACE_TECHNOMAD_ARMOR
spriteSheet: CYBERWEB_SPACE_TECHNOMAD.PCK
spriteInv: inventory_SPACE_TECHNOMAD
corpseBattle:
- STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE
This is the "old" (1.4) armor definition. STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE exists. This crashes the game.
Note that the unit is surrendering and is not killed.
-
With invalid corpse item, the game didn't even try to recover the live alien, so it didn't crash. The crashing part was skipped.
With a valid corpse item, the game tried to recover the live alien... but crashed on not existing "live alien item".
-
This is the "old" (1.4) armor definition. STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE exists. This crashes the game.
In the old 1.4 that I downloaded from mod.io, STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE does not exist.
Same as in 1.4a
So you have either added it and forgot about it, or there are multiple versions of XCF 1.4 in circulation.
-
I meant
STR_CYBERWEB_TECHNOMAD_CORPSE
instead of
STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE
in 1.4. STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE does indeed not exist, while STR_CYBERWEB_TECHNOMAD_CORPSE does.
Sorry, I think this is a mess-up on my side. I checked the old/archived versions I have saved, and none of them actually list STR_CYBERWEB_TECHNOMAD_CORPSE under the SPACE_TECHNOMAD armor. They only list the none-existing STR_CYBERWEB_SPACE_TECHNOMAD_CORPSE item.
???
No idea how this happended, but this explains why it wasn't reproducible. Again, sorry for the confusion.
Just to double-check: the game initially checks for a valid corpsebattle/corpseitem entry and only recovers live aliens if these actually exist? Meaning valid corpsebattle/corpseitem are necessary to recover live alien units?
-
Just to double-check: the game initially checks for a valid corpsebattle/corpseitem entry and only recovers live aliens if these actually exist? Meaning corpsebattle/corpseitem are necessary to recover live alien units?
Yes, OXC and OXCE first check "corpse item" and its "recover" flag when recovering both dead aliens and live aliens.
After this check, more stuff happens.
E.g. to recover a live sectoid or a dead sectoid, the game checks STR_SECTOID_CORPSE in both cases.
A dead sectoid is then recovered as STR_SECTOID_CORPSE and a live sectoid is recovered as STR_SECTOID_SOLDIER or STR_SECTOID_MEDIC, etc.
If any of these things is missing, the game may, should and mostly will crash.
For example, if you would:
1. add STR_ZOMBIE_CORPSE item to vanilla OXCE and make it recoverable
2. and allow a vanilla OXCE zombie to surrender or to be mind-controlled with psionic capture option enabled...
...the game would crash (because of missing STR_ZOMBIE item).
PS: I have added a condition to check this and ignore the OXCE live alien transformation feature instead of crashing: https://github.com/MeridianOXC/OpenXcom/commit/20ff2957130f2035d4fa16c0a6e24daee3a72cc9
-
Okay, thanks again for clearing this up :)
I probably should have checked the old archives first :P
-
Hi Meridian While I was away, I got a good and useful idea for the next update (if it was possible and not discussed)
The fact is that when the ship returned to the base, it was first refueled, then the weapon was reloaded, and then repaired.
I had frequent cases when the ship is more or less in good condition, but its repair will last 1-2 days, there is no ammunition and there is nothing to destroy the enemy, because it is first repaired, then refueled and only then rebooted. weapons (although refueling is fast enough)
Is it possible (more precisely, it is possible) to change the order of these actions in order to simplify the war with the enemies of the Emperor? (yes, chaos got me. there are many of them)
Thank you in advance!
-
It would be possible to change it.
But I don't want to change it, I want to stay compatible with the original.
-
Meridian! I have one more suggestion ... This will be useful for mods.
Can you make certain armor or weapons available only to a soldier with the appropriate rank? “As an example: in a 40K mod, Astartes with the title Captain can wear captain's armor when an ordinary Battle Brother cannot.
-
I'll consider it if the 40k modders show interest in it.
-
Quick question, since I haven't found anything in the reference:
Is it possible to modify movement costs on a per-armor basis, especially the amount of TUs it takes to transition from ground to air and movement costs while in the air/hovering?
-
Is it possible to modify movement costs on a per-armor basis, especially the amount of TUs it takes to transition from ground to air and movement costs while in the air/hovering?
No, movement cost depends on what you're walking on/flying through/swimming through.
Who is walking makes no difference.
-
How hard woudl it be to implement an armor-based modifier that adds or substracts a certain amount of TUs based on the movement/transitions? Would that even be feasible?
-
I suppose it would have to be a multiplier of the movement cost. Still, considering how low these numbers are (4 or 6 TUs, not even counting running), it would probably lead to weird effects if the multiplier isn't chosen carefully.
-
How hard woudl it be to implement an armor-based modifier that adds or substracts a certain amount of TUs based on the movement/transitions? Would that even be feasible?
Hard and VERY frustrating.
Just unhardcoding the kneel/unkneel/turn costs is on my todolist for years. And I didn't have the mental strength to start it yet.
-
I suppose it would have to be a multiplier of the movement cost. Still, considering how low these numbers are (4 or 6 TUs, not even counting running), it would probably lead to weird effects if the multiplier isn't chosen carefully.
I was thinking more about a bonus/malus instead of an actual multiplier (as in, movement on the ground costs +2, flying +4) for that very reason, I might have worded that badly. I am trying to mod a flying armor that is downsized and takes more time to traverse from walking to flying and isn't quite as fast in the air.
I have no idea if this can be done via scripts instead. I was hoping I simply missed something in the reference, but seeing how niche this is I'll shelve this idea for the time being. Thanks for the explanation Meridian :)
-
Hello, everyone!
Can anyone tell me where I could find the changelog for openxcom extended?
-
Can anyone tell me where I could find the changelog for openxcom extended?
Here: https://openxcom.org/forum/index.php/topic,4187.0.html
-
New OXCE v6.6 is up.
2020-08-22
QoL:
- Color-coded disabled research in TechTreeViewer (UFO=grey, TFTD=red)
- Save also worn armor in the personal equipment layout
- Display summary of destroyed base facilities after a missile strike
- Improved "don't follow projectiles" option a bit
Modding:
- 'manaExperience' - now also supported for psi-amps (incl. unsuccessful attempts)
- 'turnBeforeFirstStep' - option to charge TUs for turning before the first step
- 'turnCost' - unhardcoded TU cost of turning (doesn't apply to tank turret movement)
- Removed unused 'difficultyBasedRetaliationDelay' mod option
- Added 'difficultyDemigod' mod option (from OXC)
- Added XcomUtil_Fighter_Transports_TFTD standard mod
- Added XcomUtil_Triton_Weapon_Slot standard mod
Other:
- Craft weapons+ammo and HWPs+ammo now count properly towards storage limits... this was done to fix various situations where player was stuck on SELL screen
* Hangars in xcom1/xcom2 were given +5 storage space to offset new storage counting and to be compatible with original XCOM (not with OpenXcom)
* Used/Total storage space at the beginning of the game is as follows:
* XCOM: 36/50 (14 free)
* OXC: 40/50 (10 free)
* OXCE: 51/65 (14 free)
- Added mod option to define whether a base facility should have any storage tiles during base defense or not
* Hangars in xcom1/xcom2 were marked as not having any storage tiles
Scripting:
- RuleItem.getPower, RuleItem.getDamageType and many more damage-related getters
- RuleItem.hasCategory
- Tile.getPosition.getX, Tile.getPosition.getY, Tile.getPosition.getZ, Tile.getFire, Tile.getSmoke, Tile.getShade, Tile.getUnit, Tile.getFloorSpecialTileType, Tile.getObjectSpecialTileType
Bugfixes:
- Fixed crash-land condition for kamikaze and unmanned UFOs
- Fixed validations when building base facilities after a missile strike or base defense
- Fixed average monthly rating calculation in Statistics screen
- Shooting at yourself doesn't count as being shot at (diaries/commendations)
- Fixed item distribution during base defense (checkerboard pattern), broken since oxce v6.0
- Added storage check after geoscape events
- Added storage check after missile strikes
Ruleset validation:
- Displaying up to 30 validation errors at once
- Added more ruleset consistency checks
Technical:
- Removed palette switching on all images every time a new screen is opened
- Fixed crash/UB when recovering psi-captured zombies
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
Good! Please note that in linux (usin Ubuntu MATE) still in 6.6 gives a bug "GMINTRO01 music not found", don't know if it's xpiratez related but it's solved by set playintro=true to false in options.cfg. Log is attached anyway :)
-
New OXCE v6.6.1 is up.
2020-09-09
QoL:
- Improved hit log calculations a bit (when hp/stun damage are negative)
Modding:
- Added support for a fixed location/name starting base (Important: fix either location or location+name... never fix only the name, game will not work correctly if you fix only the name!!)
- Research projects with base cost = 1 cannot roll final cost = 0 anymore
Bugfixes:
- Fixed alien containment dismantle check
- Fixed a crash when AI used up one ammo from a multi-ammo weapon
- OXC: enemy melee reaction doesn't invalidate attacker's aim status anymore
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
Hi all,
Back after 5 years, OMG :o
I should not be here as often as in the past, but... what a GREAT JOB !!!
Many thanks to Meridian (and other) for all this amazing features, improvements, capabilities, etc.
Congrats to Solar to be so resilient !
And I'm forced to mention SupSuper and Warboy, whithout them nothing of that would exist : this game project is clearly the best all over the world ::)
Hum... Just back, and already a SUGGESTION lol : what about moving [Documentation] threads in a specific theme "DOCUMENTATION"
OMG so much to read, I had a look at the [Done]
And also congrats for documenting, very wise and very helpful initiative
So many new features as soldier classes, a total 40K conversion, a new mod web site. Even possibilities to write scripts. Will have to learn how to, but should made easy thanks to all these nice [Documentation] threads
Congratulations and Thanks for all of this :D
-
Welcome back :)
A lot has changed over the last 5 years... but it's still good old xcom. Check out the Discord channel too if you haven't already...
-
It will take me days even weeks to discover all of that, but it's the price to pay for the amazing job you did all here
I already found the release notes (since the merge of OXCE and OXCE+) ::)
-
Auto sell option when you produce a craft (for example I chose a Cormorant from TWoTS) not working. The button sell is pressed on, but when production is done ship not sold and present in Sub Pen. Another problem - I can't set infinite option for production ship too, it says no free Sub Pens even I have one free Sub Pen for it and auto sell option is on. Comments?
-
Comments?
These are not OXCE features, they are OXC features... and they are not supported for crafts as far as I know.
Feel free to make a suggestion for OXC.
-
As for the infinite option problem. The error message works as intended since you only have one sub penn free (taking into account that auto sell does not work on craft).
The production always starts with one unit, this one claims your only free hangar. When you try to increase the production (by one or infinite) OXC checks if there are free hangars left for the additional crafts. Since you started with only one free hangar that check returns false, hence the message "No Free Sub Pens".
If you have more than 1 free hangar the infinite option will maximize the crafts you can produce based on the number of free hangars. Something you can easily check (sell all crafts in a base with multiple hangars and then try to produce multiple crafts, it will stop once the number of empty hangars is reached).
-
Thank you all for explanation, I'm not complaining, just found how it works and posted here. So auto sell not working for crafts and this is not bug? Usually I'm not produce crafts for profit, it was small exception because I haven't researched any other production items yet, like med-kits.
-
Once again since linux users gonna need libSDL, may we get from next version an AppImage build? More info here (https://docs.appimage.org/user-guide/index.html)
-
Once again since linux users gonna need libSDL, may we get from next version an AppImage build? More info here (https://docs.appimage.org/user-guide/index.html)
If you create it, you can have it.
I will not create it.
And don't ask me again, I answered this question at least five times already.
-
Excuse me for stupid question (I know it somewhere in documentation exist), but how I can pop up search box (what keyboard buttons I should press) where I can type name of item when use sorting, researching, transfer and e.t.c?
-
Q key
-
Remind me, please, which option rigidly fixes stat points received for missions, not allowing soldiers to exceed statCaps under any circumstances? And is there such an option?
-
Remind me, please, which option rigidly fixes stat points received for missions, not allowing soldiers to exceed statCaps under any circumstances? And is there such an option?
No, there is no such option.
-
No, there is no such option.
Very sad. I wanted to use ARMOR_GAINS_EXTRA_SECONDARY_STATS_PERCENT, but in the absence of hard limits, this script spoils everything for me. Apparently I have to without him.
-
Very sad. I wanted to use ARMOR_GAINS_EXTRA_SECONDARY_STATS_PERCENT, but in the absence of hard limits, this script spoils everything for me. Apparently I have to without him.
You can change the script to apply the hard limits.
-
You can change the script to apply the hard limits.
I'm trying. :) Sooner or later, something is possible and will work out.
-
I couldn't do anything with this script, but it is as a cheating tool with the experience of a soldier - great!
-
In which particular file should add "extendedMeleeReactions"? This option does not work for me in either "difficulty.rul" or "vars.rul". Or do need to adjust the weapon for reaction separately?
-
In which particular file should add "extendedMeleeReactions"? This option does not work for me in either "difficulty.rul" or "vars.rul". Or do need to adjust the weapon for reaction separately?
Any file, but it needs to be inside "constants:" parent attribute.
Example here: https://openxcom.org/forum/index.php/topic,8166.msg127065.html#msg127065
-
Any file, but it needs to be inside "constants:" parent attribute.
Example here: https://openxcom.org/forum/index.php/topic,8166.msg127065.html#msg127065
It was written in Ruleset_Reference_Nightly, but translator failed... Understood. Thanks.
-
Is it possible to do endless research like "Future Technology" in Civilization 2?
-
Question about Distruptor pulse launcher - I've found what even with 120% (I know now what is not real accuracy %) it missing a lot - torpedo follows few way point but after that just flew out of battle map screen. Why that happened? New OXCE mechanics or it should be by default?
-
Question about Distruptor pulse launcher - I've found what even with 120% (I know now what is not real accuracy %) it missing a lot - torpedo follows few way point but after that just flew out of battle map screen. Why that happened? New OXCE mechanics or it should be by default?
There are no new mechanics.
After the last waypoint, the missile just continues in the same direction... and if it doesn't hit anything along the way, it goes out of the battle map.
-
This is strange and still confuse me. I set way points as forward, next up, next right and last is down to hit the colony roof in the middle. But instead of it the missile going up flew to roof and not moving down to hit but just off the map. It's just ignore last way point completely. Plus in few mission, usually with medium USO aliens has a lot of D.P.L.s but they missing too. Not every time of course.
Here the screenshots what I made in debug mode New battle:
(https://i.postimg.cc/MX1KPTFX/screen004.png) (https://postimg.cc/MX1KPTFX)
(https://i.postimg.cc/7J4D83Wh/screen005.png) (https://postimg.cc/7J4D83Wh)
But my last way point inside the base. May that's why it not working? It's just ignoring roof wall at all.
P.S.
I did 4th way point just one tile below 3rd on the roof but missile still missing and disappearing
(https://i.postimg.cc/NyhQkvkR/screen006.png) (https://postimg.cc/NyhQkvkR)
Save file to test. The guy who shoot has 78% on dpl:
-
It works for me just fine, see attached video.
-
I don't have recording software to show you problem, only what I can say is try set save scumming on and reload before using launcher. When enable it the missile hit but when I turn it off it miss. I think it's RNG and this weapon still can miss. If I found how record it I'll post it here. New OBS absolutely terrible I can't even capture game window :(
-
can you give me exact [x,y,z] coordinates of all 4 waypoints?
(click on a tile in debug mode to show the coordinates in the top left corner)
-
Here we go: 19,48,0 for first 19,48,3 is second 29,32,3 third and 29,32,2 last. Did it few times to make sure what I set way points in same place. I'm using guy in gold armor in front.
-
Here we go: 19,48,0 for first 19,48,3 is second 29,32,3 third and 29,32,2 last. Did it few times to make sure what I set way points in same place. I'm using guy in gold armor in front.
Yes, the missile went above the top floor.
Normal behavior, launchers also have (usually small) trajectory deviations like normal weapons.
To prevent it, send the missile along z-level=2, that way it won't go off the map.
-
Ok, thank you for investigation and explanation, much appreciated. And seems that's why aliens sometimes miss with it too. To be honest I'm glad of last fact, because it's give you chance survive on open space map.
-
I hope this is the right topic to ask my question.
When you're on the ground and if you try to retrieve an object, you get the message "Alien object" as long as no search has been done!
It's perfect!
But at the end of the mission we see the name of the object. This makes future searches much easier. Especially for very old players like me!
In several other games of the same kind as UFO/TFTD one knows the name of the object only after research. In the meantime we see in stores and in the laboratory "alien object" or "alien weapon"!
So my question is simple: is it possible to do the same thing in OXCE?
Tks !
Translated by https://www.deepl.com/translator
-
So my question is simple: is it possible to do the same thing in OXCE?
no
-
Clear... fast and accurate! :'(
What a shame!
-
So I've set up my OXC and OXCE installs (both standalone) in separate folders on non-system partition (Win7) and noticed there is a clash between the two because they both use the same options.cfg file in Documents folder. OXCE reads OXC settings fine initially, but after I make changes in OXCE and run OXC, extra options from OXCE are wiped when I run it again and need to be set again.
Is there any way to force separate config for each? For example to use OXC for vanilla games and OXCE for mods, without needing to adjust extra options every time OXCE is ran after OXC. Thought the strength of standalone was keeping stuff localized inside their own folders. Took a quick look at XPiratez and it handles it locally, inside dedicated .\user subfolder. There's gotta be a simple trick I missed.
EDIT (as I'm writing this no less...): Aaand indeed there is (https://openxcom.org/forum/index.php?topic=5186.0). Or, if one is feeling extra adventurous (https://github.com/OpenXcom/OpenXcom#directory-locations). Standalone powah!
Honestly didn't expect search engine to find an answer but I gave it a shoot anyway (bit too late). Gonna hit Post anyway, maybe someone finds it amusing if not helpful.
-
I have a question about pilot system. If interceptor weapon has 50% accuracy and pilot bring 15% accuracy bonus how it affect weapon on board? Will it change to 65% total? What exactly those 15%? Same for dodging bonus. Thanks in advance.
-
Yes, it will be 65%.
They add up.
-
New OXCE v6.7 is up.
2020-10-18
QoL:
- Show hours per unit in ManufactureInfo GUI
- Soldier bonus stats change summary table (in Soldier Bonus GUI)
- Dogfight multi-commands (R-click): https://openxcom.org/forum/index.php/topic,8655.0.html
- More default item categories (armors, prisoners) in Buy/Sell/Transfer UIs
- Show only "supported" races in New Battle GUI
- Transformations Overview GUI (by ohartenstein23)
- M-click in Build Facilities GUI: https://openxcom.org/forum/index.php/topic,7233.0.html
- Fast airborne transfer by selecting a new base as craft destination (by ohartenstein23)
- Allowed armors shown as a scrollable list (in "What can I wear?" GUI)
- Hotkey 'End' to reset interception music in Ufopedia
- Ufopedia multi-page indicator (for item articles): https://openxcom.org/forum/index.php/topic,8091.0.html
- Craft weapons can now be enabled/disabled in the hangar (click on icon)
- Stat strings update more often (after dogfight, every day after training)
- Added options.cfg entry for Intercept GUI display mode
Modding:
- BREAKING CHANGE: Combined display of vanilla+custom categories: 'useCustomCategories' (true/false) changed to 'displayCustomCategories' (0/1/2)
- Game over (win/lose) support after a research cutscene
- EXPERIMENTAL: Death traps: https://openxcom.org/forum/index.php/topic,7671.msg132978.html#msg132978
- EXPERIMENTAL: Melee terrain damage: https://openxcom.org/forum/index.php/topic,8634.0.html
- Psi camouflage: https://openxcom.org/forum/index.php/topic,7816.0.html
- Research gate for building new xcom bases: `newBaseUnlockResearch`
- Option to sort new research list by cost/name: `enableNewResearchSorting`
- Throw range limits + underwater throw range factor: https://openxcom.org/forum/index.php/topic,8273.0.html
- Finished research can now spawn geoscape events directly: https://openxcom.org/forum/index.php/topic,7698.0.html
- Ability to spawn persons via geoscape events: https://openxcom.org/forum/index.php/topic,7215.msg132650.html#msg132650
- Spawned soldier template (via Manufacturing): https://openxcom.org/forum/index.php/topic,8615.0.html
- Support for limited craft storage space: https://openxcom.org/forum/index.php/topic,8577.msg132148.html#msg132148
- Added automatic off-centre shooting (by karadoc)... as user option
Scripting:
- Get/set fatal wounds per body part, get/set current armor per body side
- Added scripts hooks for melee hit chance
Bugfixes:
- Prevent psionic capture of uncapturable units
- Fixed throwing items through ceilings and walls (OG bug)
- Fixed custom initial base bug
- Fixed soft and hard limit auto-detection in transformation stats update
- Fixed order-dependent facility upgrading
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Wiki ruleset reference and VSCode ruleset validator were updated.
PS: MacOS build will be available in a few days.
-
Thank you so much for the update. A lot of useful things. Especially impressive is the opportunity to finally create a branch of specialized cargo ships.
-
Thank you so much for your efforts, mate! You are such a good man, Meridian. :D
I totally love the new Event additions you have made, I've been waiting for them since a long time
-
Gentlemen may I ask question about Psy/MC attacks - what circumstances trigger it? Let's set all option to defaults - I mean what aliens can attack regardless of line of sight. When they exactly start doing it? When they spot x-com units, when certain amount of turns has passed or something else? What priority they will use? Weak Psy/MC units, high ranked units or units with most powerful weapons in hands?
-
They don't need line of sight (by default).
But they need to be aware of you, i.e. someone must have spotted you.
As for the rest, they use psi if they have good psi skills and they prefer weak psi soldiers. RNG is also a big factor.
There is no turn limit (by default), no rank preference, no powerful weapons preference.
-
Gentlemen may I ask question about Psy/MC attacks - what circumstances trigger it? Let's set all option to defaults - I mean what aliens can attack regardless of line of sight. When they exactly start doing it? When they spot x-com units, when certain amount of turns has passed or something else? What priority they will use? Weak Psy/MC units, high ranked units or units with most powerful weapons in hands?
Based on my last 3 months playing vanilla TFTD (dunno exactly how OXCE differs but my guess is not by much):
- aliens need to have PSI/MC capable unit on map
- your soldier only needs to be spotted, horizontal distance is irrelevant but affects success rate the most (under 20 tiles and is practically a guaranteed success but over let's say 30 and it will never succeed, under same conditions)
- they prioritize: spotted, then weakest resistance (fixed PSI/MC strength, even if you aren't there yet)
- at 20th turn aliens get a free peak at all your solders
Now the most confusing part:
- when you hit an alien with direct fire, that soldier becomes visible to all aliens on map (and remains visible for number of turns equal to hidden Intelligence attribute value every alien has, max I think is 4), obstacles or distance don't matter to visibility
Last part probably isn't 100% correct. Maybe hit alien must only be wounded and they are remembering only for one turn instead, with Intelligence coming into effect in some other circumstances. Or it is 100%. Hell if I know. One thing I clearly remember, after my PTSD wore off, is if you are getting frustrated - you are playing it right!
-
This is may be because some graphics settings in my OXCE but I want to ask anyway:
(https://i.postimg.cc/Cdm63b5H/screen117.png) (https://postimg.cc/Cdm63b5H)
I mean this pink back screen. If I remember correctly in early version when message about out of space pops out you can still see normal green back layout with items on it. Is this new OXCE feature or I mistake and it was before ? Using latest version.
-
It is an issue with the latest version.
Just visual.
I've tested it only in geoscape where it doesn't happen, on all other places it does. I will fix it today.
-
Question about throwing. The guy in front who have a flare in his hand trying throw it to another guy in front but flare just drops to his own feet. So: 1. I'm unlucky with trowing accuracy (but this is strange I did this 3 times in row and all was unsuccessful) 2. This is kneeling behavior. 3. It's because Triton roof affect throwing on distance. 4. May be a bug. Save file attached, don't forget remove Ironman mode there.
-
I'm going to be burned with this question... but since I can't find explanations and I don't understand the English language... I dare!
With OXCE 6.7 new keyboard/mouse commands appear. Example "M-click" in the research screen.
There was also "M-click" during the tactical to see the enemy and his weapons...
All these commands work very well with "OXCE 6.7 + XFiles" ! Thank you very much!
But why in an OXCE 6.7 game without any other pack these commands don't work ?
There must be something I didn't understand... sorry ! :-[
-
Question about throwing. The guy in front who have a flare in his hand trying throw it to another guy in front but flare just drops to his own feet. So: 1. I'm unlucky with trowing accuracy (but this is strange I did this 3 times in row and all was unsuccessful) 2. This is kneeling behavior. 3. It's because Triton roof affect throwing on distance. 4. May be a bug. Save file attached, don't forget remove Ironman mode there.
It's a bug.
Caused by a recent fix for throwing through ceilings and walls.
We will look at it.
-
You probably know it already, but if guy who doing it standing it works fine. Same for kneeling but if direction is diagonal it's success too.
P.S.
To avoid double posting let's just edit my message with new interesting info: I drown very small USO (TWoTS) and wait while day come. Landing there, terrain was volcanic. I begin the mission and in few turns it's over because alien(s) died from wounds. I haven't discovered them visually. I got strange mission debriefing screen - only 7 aqua plastics. So I have a question - why? I know what all equipment in USO could be destroyed due to crash, same for aliens weapons and even bodies, but where gone corpse of last alien who was alive when mission starts? It's just gone. Really strange. Sorry I don't have a save file to reproduce it.
-
P.S.
To avoid double posting let's just edit my message with new interesting info: I drown very small USO (TWoTS) and wait while day come. Landing there, terrain was volcanic. I begin the mission and in few turns it's over because alien(s) died from wounds. I haven't discovered them visually. I got strange mission debriefing screen - only 7 aqua plastics. So I have a question - why? I know what all equipment in USO could be destroyed due to crash, same for aliens weapons and even bodies, but where gone corpse of last alien who was alive when mission starts? It's just gone. Really strange. Sorry I don't have a save file to reproduce it.
can't reproduce
-
New OXCE v6.7.2 is up.
2020-10-24
QoL:
- Added Psi Training Finished GUI
- Removed automatic personal lights toggle
Modding:
- Option to ignore death traps by (original) faction: https://openxcom.org/forum/index.php/topic,7671.msg133202.html#msg133202
Bugfixes:
- Fixed visual bug with the Sell GUI
Android:
- Scan user mods also in the data folder (Android and iOS): https://openxcom.org/forum/index.php/topic,6591.msg133302.html#msg133302
- Updated icon for Android
- Updated UFO universal data patch for Android
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
I'm finding a lot of mods getting broken from 6.5 onwards, I've submitted bug reports to those modules (Though several have not been updated in quite a while so dubious if they'll ever get fixed) but something to be aware of.
Also any chance of extending debug so it can tell you at which module it has found a problem?
Perhaps on startup if debug mode is enabled it loads each module in order and does a check to make sure everything is valid before loading the next module instead of loading everything then checking which seems to be the case jus tnow, since if you enable a module in the mods menu and there's an error it will tell you what module has the error, will save new people a lot of time on setup, I spent hours figuring out which modules were having issues as I had to delete them one by one to find which one it was.
-
Also any chance of extending debug so it can tell you at which module it has found a problem?
Perhaps on startup if debug mode is enabled it loads each module in order and does a check to make sure everything is valid before loading the next module instead of loading everything then checking which seems to be the case jus tnow, since if you enable a module in the mods menu and there's an error it will tell you what module has the error, will save new people a lot of time on setup, I spent hours figuring out which modules were having issues as I had to delete them one by one to find which one it was.
1/ That's not technically possible in the current architecture.
2/ Also, there are submods, which work only in combination with parent mods.
And unfortunately even "partial" mods, which don't work standalone, but work together with other "parts".
To find out (and fix) issues you can enable mods one by one, instead of enabling everything and then guessing what's wrong where.
That should reduce the time to fix it from hours to minutes.
At least it does for me.
-
Meridian, are there (or are planning) options for managing the cost and time of transfers between bases?
-
Meridian, are there (or are planning) options for managing the cost and time of transfers between bases?
Currently I don't know of any such request.
-
Consider that now he is. :)
-
Consider that now he is. :)
Well, I need some details too... how should it work?
-
Well, I need some details too... how should it work?
First, would like to know the default time and cost. How is the transfer price and time calculated?
Options (transferBaseTime: 1.0) and (transferBaseCost: 1.0) must manage divider \ factor of default values.
-
First, would like to know the default time and cost. How is the transfer price and time calculated?
It's based on distance.
Maximum distance is 102.4 (for example between north pole and south pole).
Transfer cost is:
- distance*1 for items
- distance*5 for personnel
- distance*25 for craft
Transfer time is: 6 + distance/10... so anywhere between 6 and 16 hours.
-
Can use a multiplier of the default values. Working with integers, it seems, will not work.
-
Meridian, I'm sorry to bother you, but there is one more thing. If soldierDiaries (soldierDiaries: false) is disabled, can the "DIARY" and "STATISTICS" buttons be disabled? And what's the point in them, with statistics disabled?
-
Meridian, I'm sorry to bother you, but there is one more thing. If soldierDiaries (soldierDiaries: false) is disabled, can the "DIARY" and "STATISTICS" buttons be disabled? And what's the point in them, with statistics disabled?
I will disable the Diary.
In Statistics, I will only hide the fields that depend on the Diary.
PS: if you load a save, which does contain soldier diaries, they will also not be visible
-
Thanks.
It is sometimes interesting to play without statistics. In a retro style, might say.
Ideally, if the statistics were disabled, the counter of the stunned remained, like the counter of the killed. But I already wrote about it.
-
Is there a quick way, while maintaining the inability to use alien artifacts, to allow them to be loaded onto the ship?
-
Is there a quick way, while maintaining the inability to use alien artifacts, to allow them to be loaded onto the ship?
no
-
Encountering some issues modding OXCE (on android). Dunno if I did something wrong or what.
Coelacanth/Gauss
Changed the gauss cannon ammo to do explosive damage and reduced power to 50.
But in DamageAlter I tweaked all the stats including ToTile to do 3 times what it would normally do (and turned randomHealth, randomWound, randomStun off). And added ResistType: 4 and FixRadius: 3.
The idea here is a shot so powerful it causes a small explosion and concentrated damage. But by using 50 Power it visually displays a small explosion to match its size. By doing x3 stats it should effectively leverage on everything as if it was 150 damage (then 120, 90 adjacent).
But...
Then noticed in Ship Terror Mission the shots are Not damaging the regular steel walls that a Sonic Pulser will blow open (even at Power 50 and ToTile 1.5). With several shots, so its not just crap damage rolls.
And on a different ammo type (Gas Cannon AP) that I did the same thing to it Is Not displaying in the Ufopaedia that it does (ResistType: 1) Armor Piercing, it still lists High Explosive there.
Has ResistType and ToTile been turned off?
-
Can't say anything without seeing the full runnable mod.
-
Can't say anything without seeing the full runnable mod.
As noted the hwp gauss doesn't seem to do much damage. Two hits to the coral shale only damaged the urchins on it. I forget the mcd armor of the shale pieces but it should be getting hit vs 75.
-
As noted the hwp gauss doesn't seem to do much damage. Two hits to the coral shale only damaged the urchins on it. I forget the mcd armor of the shale pieces but it should be getting hit vs 75.
You have 56 syntax errors there.
Sample attached as screenshot.
-
Question about panic, berserk and losing morale as aliens. I know what OXCE long time ago has changed algorithm about how aliens lose moral, it's in patch (release) notes. That's fine. I'm accepting the rules. According the last, enemy morale drops slow in large groups. But I've found strange thing what confuse me - playing TWoTS on experienced I almost not encountered any panics from missions what have big USOs (large or very large) and vise versa - on superhuman when I kills a lot of enemies they start panic or even surrender. So why this happened? How it working - on % of remain live aliens on map in compare with 100% of them when mission starts or it's fixed number not depending on %, so low difficulty has less enemies on map at beginning and chance of panic significantly lowers? Could it be affected but mod .rul files with (or) errors in it? How difficulty works? Thank for answers in advance.
-
Idea is simple, if enemy loose 1% of its units it should not make panic. Even its is 100 units (of 10000).
You can image this as if there is lot of units then each morale loose is multiplied by 0.01, if there is only 10 units then its multiplied by 1
-
You have 56 syntax errors there.
Sample attached as screenshot.
They're Case-Sensitive?
Sorry about that, didn't know.
-
Sorry for asking again about pilots but I'm using now interceptor which require two of them. So question - how additional evasion and accuracy stats works now? Is it adding average of both guys? I mean formula is addstat=(statguy1+statguy2)/2 ? I'm asking because both my guys has +18 on accuracy if they used alone in one pilot interceptor craft. But now in two pilots the bonus stats stays +18 not +36. Thanks for explanation in advance.
-
Sorry for asking again about pilots but I'm using now interceptor which require two of them. So question - how additional evasion and accuracy stats works now? Is it adding average of both guys? I mean formula is addstat=(statguy1+statguy2)/2 ? I'm asking because both my guys has +18 on accuracy if they used alone in one pilot interceptor craft. But now in two pilots the bonus stats stays +18 not +36. Thanks for explanation in advance.
yes, it's averaged
-
Sorry for asking it here, but I have not saw Nord for long time (hope he is fine!). TWoTS latest. For some reason I can't dismantle one empty sub pen at base 1 until I sell D.U.P head torpedoes and other ship equipment. Is this because I'm almost lack of space and sub pens provide some small additional storage space too? Save file for investigation.
-
Sorry for asking it here, but I have not saw Nord for long time (hope he is fine!). TWoTS latest. For some reason I can't dismantle one empty sub pen at base 1 until I sell D.U.P head torpedoes and other ship equipment. Is this because I'm almost lack of space and sub pens provide some small additional storage space too? Save file for investigation.
Without looking at your save: Probably yes.
Hangars do give some storage space and it is probably the same in this mod. You can check in the Stats for Nerds section of the Hangar ufopaedia.
-
Yes, you right, it's provide 5 storage space. I was inpatient and haven't check the stats before posting my stupid message. Apologizes everyone. Playing games using OXCE a lot and always missing some obvious things :)
-
Took me an unreasonable amount of time to get this to work but:
Portable Xcom Files! It takes four and a half minutes to load, but it works 8)
-
Hehe, nice.
-
I am so honored!
-
New OXCE v6.8 is up.
2020-11-21
QoL:
- Show turn limit in the End Turn button tooltip
- Notes GUI (hotkey `Ctrl+N`)
- TTV produced by section
- TTV back button (hotkey `Backspace`)
Modding:
- EXPERIMENTAL: reinforcements script: https://openxcom.org/forum/index.php/topic,5151.msg133650.html#msg133650
- Ability to override rank-based race member (see link above)
- Escort the VIPs mission type: https://openxcom.org/forum/index.php/topic,8792.0.html
- Protect the VIPs mission type (see link above)
- Custom debrief mission accomplished/failed title (`missionCompleteText`, `missionFailedText`)
- Custom name/attributes for civilians recovered as soldiers: https://openxcom.org/forum/index.php/topic,5185.msg134201.html#msg134201
- (Partial) Support for non-point mission site areas (e.g. terror sites don't have to be only in cities, but can be in rectangular areas)
(full support since OXCE v7.3)
- Support for craft skins: https://openxcom.org/forum/index.php/topic,8244.msg133524.html#msg133524
- Ability to disable facility connectors: https://openxcom.org/forum/index.php/topic,8006.msg133709.html#msg133709
- Support for multiple air lock types: https://openxcom.org/forum/index.php/topic,8006.0.html
- Base defense facility ammunition: https://openxcom.org/forum/index.php/topic,7651.msg133495.html#msg133495
- Alternative pedia article for armors (MMB): https://openxcom.org/forum/index.php/topic,8707.msg133338.html#msg133338
- Custom sprite for UFO-style armor articles: https://openxcom.org/forum/index.php/topic,8707.msg133330.html#msg133330
- Custom palette support for TFTD-style pedia articles: https://openxcom.org/forum/index.php/topic,4957.0.html
- Option to disable tech tree viewer: https://openxcom.org/forum/index.php/topic,8791.0.html
- Option to disable stats for nerds (see link above)
- Option to disable production dependency tree (see link above)
- Option to disable "alien inventory" (see link above)
- Option to disable hit log/turn diary (see link above)
- GetOneFree now works also for mission bonus and event bonus
- Craft immune to detection by HKs and alien bases flag (`undetectable`)
Bugfixes:
- Fixed 2x2 units autoshots bug on slopes
- Fixed in-use check for prisons
- Fixed 40k turret endless loop
- Fixed verticalLevels in a facilities ruleset having a wrongly sized map script command
- Fixed fake civilian scoring issue
- Fixed 25yo bug (throwing through walls and ceilings)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
VSCode ruleset validator plugin and ufopedia.org wiki ruleset reference were updated.
-
I'm going to be burned with this question... but since I can't find explanations and I don't understand the English language... I dare!
With OXCE 6.7 new keyboard/mouse commands appear. Example "M-click" in the research screen.
There was also "M-click" during the tactical to see the enemy and his weapons...
All these commands work very well with "OXCE 6.7 + XFiles" ! Thank you very much!
But why in an OXCE 6.7 game without any other pack these commands don't work ?
There must be something I didn't understand... sorry !
I have finally found the cause of the error!
I had about twenty small mods!
I had to put them together in a pack and now everything works!
-
Good job. Thanks for the update.
-
Thanks for this brand new update full of amazing new features, Meridian! You are the best))
-
Hey on the Android version how do you turn the personal lights back on?
I have no idea how they got turned off in the first place, but now I cant find the option in either the .cfg file or the .sav file.
-
click on the blue rectangle
-
No thats not what im talking about. Night vision comes on automatically. However even with it off the Triton and all personnel and HWPs are supposed to have a personal light, always been that way.
Now somehow all of that has disappeared.
The only lights visible on the map at all are because of Fires (didnt bring flares).
-
I'll release an update tomorrow with an extra button to toggle personal lights separately.
-
Here's a clearer example. I also did a fresh reinstall too. Simple quick battle no saves. Max darkness shade. I tossed the flare on the upper deck.
Notice that none of the units have light on them at all.
This could be a bug, dunno. I upgraded the other day to 6.8 from 6.6 and started noticing it after that.
Oddly when the darkness shade isnt strong enough to enable nightvision the personal lights are present. But when nightvision becomes available, the lights go off. That makes this sound like a light system bug.
-
New OXCE v6.8.3 is up.
2020-11-30
QoL:
- Ctrl+EndTurn to skip AI in debug mode
Modding:
- Melee terrain damage for 2x2 units: https://openxcom.org/forum/index.php/topic,8634.0.html
- No CQC when surprised (see `closeQuartersSneakUpGlobal` in the ruleset reference)
- Option to disable inventory TU cost indicator: https://openxcom.org/forum/index.php/topic,8791.0.html
Bugfixes:
- Fixed double mod loading on mobile platforms
- Fixed personal lights issue on Android
- Fixed rare crash when reporting a crash :)
- Fixed rare crash on mising footstep sound
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
- Melee terrain damage for 2x2 units: https://openxcom.org/forum/index.php/topic,8634.0.html
If the AI uses it, Reapers will finaly be able to navigate cities. :)
-
I was using the OXCE Version from 2019 (with X-Files mod). Today I downloaded the Nov. 2020 version and simply overwrite all 2019 files with the new ones from the downloaded archiv.
Now I have a strange error.
[21-12-2020_20-34-25] [ERROR] Error processing 'STR_DAVID_VINCENT' in units: Item STR_STR_DESERT_EAGLE not found
Error processing 'STR_FEMALE_CIVILIAN_CITY_GIRL' in units: Item STR_PAINKILLERS not found
Error processing 'STR_MALE_CIVILIAN_CITY_BOY' in units: Item STR_PAINKILLERS not found
Sounds like a problem with the Mod. But I do not understand why the Mod matters.
I did not updated the Mod! An old Mod version should work with a new/fresh OXCE version - in my understanding.
So what do I missunderstand here?
-
Sounds like a problem with the Mod. But I do not understand why the Mod matters.
I did not updated the Mod! An old Mod version should work with a new/fresh OXCE version - in my understanding.
So what do I missunderstand here?
We improve OXCE constantly and add ruleset validations almost every release to improve the quality of mods.
That causes mods, which had an (undetected) error to stop working after the upgrade. The modders then update/fix their mods and release a new version that's better. Win win.
-
I see. That sounds like a good solution.
I have the lates X-Com Files 1.7b and lates OXCE. It starts now.
But my savegames are not displayed in the game menu. The save game list is empty.
But the sav-files are still in ~/.local/share/openxcom/x-com-files. What can do to bring them back in the game?
-
The mod was deactived. I can't understand why.
XCOM2 was load by default.
After activating I get an error again.
[22-12-2020_21-42-07] [WARN] disabling mod with invalid ruleset: x-com-files
[22-12-2020_21-42-07] [ERROR] failed to load 'X-Com Files'; mod disabled
Error for 'STR_LASER_CARBINE': offset '2016' exceeds mod size limit 2000 in set 'HANDOB.PCK' at line 11567
-
Mod size limit in XcomFiles 1.7b is 3000, not 2000.
Just install the mod properly and don't mix it with old versions or anything.
It's really easy.
-
New OXCE v6.9.1 is up.
2021-01-09
QoL:
- User option for default filter in New Manufacture UI (`oxceManufactureFilterSuppliesOK` in options.cfg)
- Prioritize drawing units on the ground (regardless of weight)
Modding:
- Unhardcoded hit/explode/bulletimpact animation frame counts: https://openxcom.org/forum/index.php/topic,8944.msg135061.html#msg135061
- Ability to re-enable disabled research topics: https://openxcom.org/forum/index.php/topic,5482.msg135345.html#msg135345
- Option to trigger events on country leave/rejoin: https://openxcom.org/forum/index.php/topic,8878.msg135112.html#msg135112
- Alternative battlescape theme window background: https://openxcom.org/forum/index.php/topic,9020.0.html
- Allow Leeroy to perform multi-turn charge: https://openxcom.org/forum/index.php/topic,5628.msg135343.html#msg135343
Scripting:
- More scripting support for Ufos and Crafts
- Add script handlers for stats for nerds: https://openxcom.org/forum/index.php/topic,8985.0.html
Bugfixes:
- Fixed support for non-point mission site areas
- Fixed crash when reloading the game with a primed spawning item in an inventory
- Fixed reload of multi-slot weapons
- Fixed sorting of compatible ammo lists (affected Ufopedia display)
- Fixed drag scrolling and middle-click (when using black borders/letterboxing)
- Don't play firing sound with no ammo (during base defense)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
Hello! Are universal patches for UFO and TFTD included?
-
Hello! Are universal patches for UFO and TFTD included?
In Android version, UFO patch is included, TFTD not.
In all other versions, they are both not included.
PS: so exactly the same as in OpenXcom zip distributions
-
New functionality in scripts:
begin; #stat new scope with new variables
var int i 15; #new variable in the middle of script
loop var zz i; #repeat this code block `i` times, `zz` will have values from `0` to `i-1`
if eq zz 6;
break; #break out of loop block
end;
if eq zz 3;
continue; #skip rest of body of loop and repeat it from start with next `zz` value.
end;
end;
end;
I added too new function to multiple function in script for unit stats, idea is that in may cases you want add some value to some stat and you are not interested in current value, now you need use `getX` and `setX` to set some thing, now I added `addX` that add to value of stat.
-
Big request to return the option - difficultyBasedRetaliationDelay. Or tell me a way to completely avoid the Retaliation missions in the first month.
-
Big request to return the option - difficultyBasedRetaliationDelay. Or tell me a way to completely avoid the Retaliation missions in the first month.
ok
-
What is "ambienceRandom" attached to? Why is he inherited by the next mission in two-tier missions?
If this is intended, then it is very bad. Maybe it should be hard-tie to "terrains.rul", and not to the mission?
There is a bug in version 6.9.6. In version 6.9.1 - no.
-
What is "ambienceRandom" attached to?
It's attached to terrain.
There is a bug in version 6.9.6. In version 6.9.1 - no.
I cannot see any difference between 6.9.1 and 6.9.6.
-
And yet in 6.9.6. "ambienceRandom" and "ambience" are carried over from the first mission to the second, which is not in 6.9.1 version. Moreover, if the second has its own "ambience" - then both work. I just put it before the fact.
И тем не менее в 6.9.6. "ambienceRandom" и "ambience" переносятся из первой миссии во вторую, чего в 6.9.1 версии нет. Причём, если во второй есть свой "ambience" - то работают оба. Просто ставлю перед фактом.
-
And yet in 6.9.6. "ambienceRandom" and "ambience" are carried over from the first mission to the second, which is not in 6.9.1 version. Moreover, if the second has its own "ambience" - then both work. I just put it before the fact.
И тем не менее в 6.9.6. "ambienceRandom" и "ambience" переносятся из первой миссии во вторую, чего в 6.9.1 версии нет. Причём, если во второй есть свой "ambience" - то работают оба. Просто ставлю перед фактом.
Doesn't happen for me.
If you have a way to reproduce, share the necessary files, saves and steps.
-
Okay.
But first you need to download and install my modification. https://openxcom.org/forum/index.php/topic,5724.0.html
-
Now for the details. If the first mission has "ambienceRandom" and the second "ambience:", then the "ambience:" of the second mission is added to the "ambienceRandom" list of the first mission. In version 6.9.1 this is definitely not the case. Introduced with installation 6.9.6. Checked it three times on both versions.
Теперь подробности. Если первая миссия имеет "ambienceRandom", а вторая "ambience:", то "ambience:" второй миссии добавляется к списку "ambienceRandom" первой миссии. В версии 6.9.1 такого точно нет. Появилось с установкой 6.9.6. Проверил трижды на обеих версиях.
-
The behavior is the same on v6.9.1 and v6.9.6
The different results are caused by RNG.
Your second stage has two different terrains with two different ambient sounds. The result depends on which terrain is picked.
- type: STR_ALIEN_CAVE_MISSION_P2
...
terrains:
- UBASE
- LEVEL
-
No, that's not the point. Both underground locations have NO bird sounds from the surface. UBASE does not have " ambience:". LEVEL has, and its " ambience: "is added to the "ambienceRandom" list from the previous level's location.
Нет, дело не в этом. На обоих подземных локациях НЕТ звуков птиц с поверхности. UBASE не имеет "ambience:". LEVEL имеет, и его "ambience:" добавляется в лист "ambienceRandom" с локации предыдущего уровня.
In short, there is a superimposition of "ambience:" and "ambienceRandom".
-
"ambience" cannot be added to "ambienceRandom"... that is absolutely impossible. Variables are kept separated at all times.
On stage one, the variables contain:
ambience: -1
ambientVolume: 1.25
ambienceRandom:
- 1563
- 1564
- 1565
- 1566
- 1567
- 1568
- 1530
- 1531
- 1532
- 1534
- 1535
On stage two, for first terrain, the attributes contain:
ambience: -1
ambientVolume: 0.5
ambienceRandom:
[]
On stage two, for second terrain, the attributes contain:
ambience: 1494
ambientVolume: 1
ambienceRandom:
- 1563
- 1564
- 1565
- 1566
- 1567
- 1568
- 1530
- 1531
- 1532
- 1534
- 1535
No superimposition.
ambienceRandom is from previous stage, ambience is from next stage and it was not added into the ambienceRandom list
-
I don't know where it came from.
alienDeployments:
- type: STR_ALIEN_CAVE_MISSION
terrains:
- CULTACAV
nextStage: STR_ALIEN_CAVE_MISSION_P2
- type: STR_ALIEN_CAVE_MISSION_P2
terrains:
- UBASE
- LEVEL
terrains:
- name: CULTACAV
script: FARMPCAV
mapDataSets:
- BLANKS
- CULTIVAT
- BARN
ambienceRandom: [563, 564, 565, 566, 567, 568, 530, 531, 532, 534, 535]
ambienceRandomDelay: [8, 16]
ambientVolume: 1.25
- name: UBASE
mapDataSets:
- BLANKS
- U_BASE
- U_WALL02
- U_PODS
- BRAIN
- U_BASE2
- U_DISEC2
- U_OPER2
script: ALIENBASE
mapBlocks: &Ubase1
- name: UBASE_00
- name: LEVEL
music:
- GMTACWET
ambience: 494
ambientVolume: 1.0
enviroEffects: STR_Underwater_D
mapDataSets:
- BLANKS
- SEAORGANIC1
- SEAORGANIC2
- SEAORGANIC3
- SEANOM
script: TLETH_P2_P3
mapBlocks:
- name: LEVEL01
-
It came from the previous stage.
I still don't get what you want from me:
1/ you said it works differently in 6.9.1 and 6.9.6 ... I have proved to you that it works the same way in both.
2/ I have also proved that the two attributes are not mixed, you can see it in the saved game yourself if you don't believe me
The correct solution is to not mix ambience with ambienceRandom... as it is described on the wiki: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Terrains
It explicitly says for ambienceRandom: "Doesn't work when ambience is defined."
The correct solution is to replace
ambience: 494
with
ambienceRandom: [494]
Stick to using either ambience or ambienceRandom, not both.
I can check if I can make it better, but for now it works as described on the wiki and on the forum.
-
I have it nowhere and does not mix.
Do you mean that can use either "ambience:" or "ambienceRandom" in general in the entire modification?
Why then in version 6.9.1 nothing of the kind was observed?
Changed to "ambienceRandom: [494]" - the sound stopped playing at all.
-
Do you mean that can use either "ambience:" or "ambienceRandom" in general in the entire modification?
During the same mission, you should use only one of them.
Why then in version 6.9.1 nothing of the kind was observed?
I have observed it today many times in 6.9.1, there's a 50% chance for it to happen.
Attaching a video as proof.
-
I wrote about that that it is good to tie "ambience:" and "ambienceRandom" to "terrains.rul", not to the mission.
During the same mission, you should use only one of them.
Understand.
-
Big request to return the option - difficultyBasedRetaliationDelay. Or tell me a way to completely avoid the Retaliation missions in the first month.
Implemented today in v6.9.7.
During the same mission, you should use only one of them.
In v6.9.7, all the ambient sounds will be reset when moving from one mission stage to another.
You don't have to reset them manually anymore.
You can now also use different types of ambient sound (`ambience` or `ambienceRandom`) on each mission stage.
https://lxnt.wtf/oxem/builds//Extended/Extended-6.9.7-7c2b57431-2021-02-27-win64.7z
-
Working. Thank you.
-
I just tried out Extended for the first time. Loaded an OXC save...
1. In Battlescape, what's the little number 2 in the lower-right corner of the psi-amp in my soldier's hand?
2. Why would the game tell me I'm missing mods, even though I carefully checked that I have exactly the same mods as in OXC? The same selection of standard mods, as well as this mod (https://openxcom.mod.io/alloys-and-elerium-on-top) that transferred no problem. Should I worry about savegame compatibility from OXC -> OXCE?
3. is there a comprehensive list of differences between OXC and OXCE to be read anywhere? I don't just mean the ruleset referece, but features in general.
For example I see that the unequal LOS that leads to failure of mutual surprise when smoke is involved is solved. This is good, and important - but I do not see how I could know this if it hadn't been mentioned by some forum member in a conversation I was part of elsewhere.
-
I'm not an authority when it comes to answering this so I'll give what I think is right, until proper answers arrive:
1. In another mod I currently play, the number denotes if item requires 2 hands to use (green - allowed use but with acc penalty; red - other hand must be free to allow use). Not sure why or if Psi-Amp is a unique case here.
2. Don't know. I'm only worried about retaining OXC <-> OXCE vanilla savegames compatibility, nothing else. Additional mods complicate things in unforeseen ways so you may not get satisfactory answer to this.
3. Only this short list (https://openxcom.org/forum/index.php/topic,6459.0.html), afaik. I actually prefer OXCE way. If we were to load saves in OXC the game simply assumes vanilla behavior without loss of information (except additional UI options in OXCE).
LOS and other stuff, if indeed the case, may be unintentional case of undocumented changes. Those creep up over time and get increasingly more difficult to keep track of? Could be on your end though, since you mentioned mods. Residue in configs/rules/etc from pasts mods perhaps? Anyway, like I said, let's wait for proper authority as topic mildly interests me as well.
-
I just tried out Extended for the first time. Loaded an OXC save...
1. In Battlescape, what's the little number 2 in the lower-right corner of the psi-amp in my soldier's hand?
2. Why would the game tell me I'm missing mods, even though I carefully checked that I have exactly the same mods as in OXC? The same selection of standard mods, as well as this mod (https://openxcom.mod.io/alloys-and-elerium-on-top) that transferred no problem. Should I worry about savegame compatibility from OXC -> OXCE?
3. is there a comprehensive list of differences between OXC and OXCE to be read anywhere? I don't just mean the ruleset referece, but features in general.
For example I see that the unequal LOS that leads to failure of mutual surprise when smoke is involved is solved. This is good, and important - but I do not see how I could know this if it hadn't been mentioned by some forum member in a conversation I was part of elsewhere.
1/ it's the indicator that it is a 2-handed weapon
2/ if you're missing mods, check if they have metadata.yml (this file is mandatory in OXCE)
if you're not missing any mods, upload the save here so that I can have a look
you don't need to worry about savegame compatibility OXC -> OXCE, it is 100% compatible
3/ there are thousands of fixes and new features in OXCE, the only truly "comprehensive" list of differences is a git log
more humanly-readable changelog is here: https://openxcom.org/forum/index.php/topic,4187.0.html
but even this shortened changelog is a reading for days and days... there's 7 years of active development in OXCE
The LOS example (once confirmed) is likely a very early change (from before 2015), when I wasn't involved in OXCE yet, and thus not documented by me.
I'll check what the difference is and document it... but I don't think OXCE has equal LOS, as far as I know smoke does make it unequal also in OXCE, maybe in a slightly different way if you say it works differently than OXC.
-
Thanks for the replies.
The LOS example (once confirmed) is likely a very early change (from before 2015), when I wasn't involved in OXCE yet, and thus not documented by me.
I'll check what the difference is and document it... but I don't think OXCE has equal LOS, as far as I know smoke does make it unequal also in OXCE, maybe in a slightly different way if you say it works differently than OXC.
I found out about it from this post (https://openxcom.org/forum/index.php/topic,3315.msg38023.html#msg38023). If you download the savegame from the first post of that thread, you'll see that in OXC moving the soldier one tile forward, to 31,20, gets the soldier killed through lack of mutual surprise, while in OXCE any angle of approach results in mutual surprise. This is true without any mods.
if you're missing mods, check if they have metadata.yml
Never mind. I somehow unclicked a mod I thought I had clicked. I shouldn't post while ultra tired.
I do not understand, however, why OXC sees my own mod that I add to the "standard" folder, while in OXCE the game only recognizes it if I put it in user/mods. Is this intended? And yes, I did include metadata.yml.
-
I do not understand, however, why OXC sees my own mod that I add to the "standard" folder, while in OXCE the game only recognizes it if I put it in user/mods. Is this intended? And yes, I did include metadata.yml.
Yes, it was intentional. There was too much confusion in the discussions, when some wrote that mods should be placed in the "mods" folder, and others that in the "standard" folder.
-
I do not understand, however, why OXC sees my own mod that I add to the "standard" folder, while in OXCE the game only recognizes it if I put it in user/mods. Is this intended? And yes, I did include metadata.yml.
Yes, it is intended.
It's needed for example for the auto-update functionality.
But even without it, supporting and troubleshooting manual upgrade issues and platform change issues has become much easier since this was introduced. It has saved countless hours that I can invest more productively into development.
-
I see, then nothing's wrong. Good to know.
-
So, if my "mod" consists of just a single rul file with a few changes, do I still need the metadata.yml file? What does that file need to have in it (or can I take an existing one from another mod and make whatever changes are needed)?
-
So, if my "mod" consists of just a single rul file with a few changes, do I still need the metadata.yml file? What does that file need to have in it (or can I take an existing one from another mod and make whatever changes are needed)?
Yes, every OXCE mod no matter how small needs it.
"id" and "name" should be provided as a minimum, other attributes are optional.
You can copy it from another mod if you want, just don't forget to change those two attributes, especially the "id" (it needs to be something unique).
-
1, 2, 3, 4.....
Most of it is already implemented and working. There is no point in discussing anymore. Sooner or later, the rest will be implemented. As I said, it only takes time.
-
1, 2, 3, 4.....
Most of it is already implemented and working. There is no point in discussing anymore. Sooner or later, the rest will be implemented. As I said, it only takes time.
I don't know what you're talking about.
-
even this shortened changelog is a reading for days and days
Hey, it's more useful than you made it sound. I've already been able to look up various stuff that bothered me thanks to that link (like why I suddenly have 65 storage instead of 50, that freaked me out). So thanks again!
-
Meridian, can you tell us what was done in version 6.9.7-e? I don't even know where to look and what to test, other than what was discussed. What's in development? When the release of a new version that is already underway.
-
Meridian, can you tell us what was done in version 6.9.7-e? I don't even know where to look and what to test, other than what was discussed. What's in development? When the release of a new version that is already underway.
I will provide a changelog with the official release.
The next official release is v7.0 and will be released probably on March 13th.
-
What exactly is the minimum condition to train throwing with grenades?
I just did this:
- One soldier threw 3 armed alien grenades
- One soldier threw 3 armed smoke grenades
- One soldier threw 3 unarmed smoke grenades
Then I loaded them back onto the Skyranger and left. The post-mission screen showed 0 gains for all.
Repeated the same with save scumming on. Same result.
Me confused.
Do I have to hit an enemy target? Or do I need to beat the mission?
-
Throwing as such doesn't train throwing accuracy in OXCE, more details here: https://openxcom.org/forum/index.php/topic,4230.0.html
Hitting (zero damage also counts) an enemy with a thrown weapon does.
So for example, if you throw a grenade, it explodes and hits 5 enemies... you get +5 throwing experience... which then transforms into +1, +2 or +3 throwing accuracy at the end of the mission.
-
- Craft weapons+ammo and HWPs+ammo now count properly towards storage limits... this was done to fix various situations where player was stuck on SELL screen
* Hangars in xcom1/xcom2 were given +5 storage space to offset new storage counting and to be compatible with original XCOM (not with OpenXcom)
I wonder what sort of situations caused this. Producing craft ammo that took up more space than the materials going into it, while advancing time by "1 day" so it's hard to stop before the forced sale is triggered again and again?
If I guessed this correctly, then I wonder why something similar wasn't done with armors. At the moment armors worn by soldiers don't count towards the storage limit, and it's possible to get a situation with the SELL screen popping up if producing Alloy/Platics armor, since they take up more space than the materials used.
-
I wonder what sort of situations caused this.
In OXC, losing a part of the base due to base defense.
In OXCE, additionally also missile strikes.
Just producing stuff would not cause this, you can sell a lot of other stuff without getting stuck.
To get stuck, you need a sudden and drastic change in storage space.
-
How do "stats for nerds" (I hate that name with a passion) calculate "average DPM" for Craft Weapons?
For UFOs I understand the results. A Battleship has 140 damage, 60% accuracy, 0-100% damage range, average reload of 24 on Superhuman. 140*(60/24)*(60/100)*(1/2)=105. And the game indeed shows a DPM of 105.
A Laser Cannon has 70 damage, 35% accuracy, 24s reload, and presumably a damage range of 50%-100% (https://www.ufopaedia.org/index.php/Craft_Combat_Mechanics#Damage_Mechanics). 70*(35/100)*(60/24)*(3/4) ≈ 46. The screen shows 61, which is 4/3 of what I calculated. Is the 50-100% damage range not observed in OXC, or OXCE?
In OXC, losing a part of the base due to base defense.
In OXCE, additionally also missile strikes.
I see, I made wrong assumptions, then.
But I'm not sure I understand. How did that lead to being stuck, in a way that just selling enough stuff didn't solve? Why was the handling of craft armaments and tanks particularly important?
-
How do "stats for nerds" (I hate that name with a passion) calculate "average DPM" for Craft Weapons?
// (damage / standard reload * 60) * (accuracy / 100)
int avgDPM = craftWeaponRule->getDamage() * craftWeaponRule->getAccuracy() * 60 / craftWeaponRule->getStandardReload() / 100;
Is the 50-100% damage range not observed in OXC, or OXCE?
It is.
But I'm not sure I understand. How did that lead to being stuck, in a way that just selling enough stuff didn't solve? Why was the handling of craft armaments and tanks particularly important?
Start a new game, sell everything, go to sell screen again... you'll see you still have a lot of stuff even after you sold everything.
Now imagine you try to do that with storage space = 0.
You wouldn't be able to perform the first sell (both sell and cancel buttons would be hidden and you would be stuck).
-
It is.
But not in the "stats for nerds"?
If I found the right git source (https://github.com/MeridianOXC/OpenXcom), then I see the UFO part contains the 0-100% spread factor:
// spread 0-100%
double avgDamage = totalPower * 0.5;And indeed the values displayed on the stats page come out as what you'd expect.
But the craft weapon part doesn't seem to include the 50-100% damage spread. This affects both average and total damage displayed. And indeed the values come out wrong.
What I'm trying to ask is if this an oversight that needs to be fixed? Or am I missing something.
-
What I'm trying to ask is if this an oversight that needs to be fixed? Or am I missing something.
I chose the value without 50-100% for Craft weapons to be consistent with the main Ufopedia display.... Ufopedia says Damage=70 (instead of Power=70).
Whereas in UFO articles, Ufopedia refers to Power (not Damage), so I added the damage spread to calculate damage from power.
I don't mind changing it, but it will be inconsistent one way or another.
What's more important than the absolute numbers is the relative comparison of two weapons.
Regardless if the numbers say 50 and 100; or 70 and 140... the second weapon does twice as much damage as the first one.
PS: btw. even with damage spread considered, the numbers can still be very far from reality... pilot skills, craft bonuses, ufo bonuses and alien race bonuses all affect the final numbers and can make the same weapon very effective in one situation and completely useless in another situation
-
I see.
I chose the value without 50-100% for Craft weapons to be consistent with the main Ufopedia display.... Ufopedia says Damage=70 (instead of Power=70).
Whereas in UFO articles, Ufopedia refers to Power (not Damage), so I added the damage spread to calculate damage from power.
I don't mind changing it, but it will be inconsistent one way or another.
What's more important than the absolute numbers is the relative comparison of two weapons.
Regardless if the numbers say 50 and 100; or 70 and 140... the second weapon does twice as much damage as the first one.
There's also UFO DPS vs craft DPS. And there's total expected weapon damage vs UFO hitpoints.
In those contexts the omission makes the craft weapons look more powerful than they are. I discovered this because I'm working on a little craft/ufo balance mod right now. For me it's not a problem anymore, since thanks to your explanation I know what's going on, and I'm doing the same thing in a spreadsheet, but still, until I asked I was confused. I cannot be the only person who will ever think of using that screen as a quick way to check "can this craft weapon shoot down this UFO before it runs out of ammo".
A stats/calculations display is an opportunity to present real values to the player, precisely because Ufopedia is wrong/misleading (when it says "Damage", it doesn't actually mean damage, it means a stored value that happens to be labelled "Damage"). Being consistent with in-game Ufopaedia has less value than giving the player accurate info.
This could be fixed by showing the damage range in the Ufopaedia - which actually might not be a bad idea. But perhaps not worth the effort, the added visual complication, and departure from past practice. X-com veterans are used to pedia values being worthless anyway.
PS: btw. even with damage spread considered, the numbers can still be very far from reality... pilot skills, craft bonuses, ufo bonuses and alien race bonuses all affect the final numbers and can make the same weapon very effective in one situation and completely useless in another situation
Right, Extended features. Atm I'm working with vanilla mechanics, and use Extended solely because it lets me use a keyboard shortcut to Mind Control things. Joking. I mean I use it for that and the MANY other conveniences like that. And for the equal mutual surprise fix, which I still don't think is documented but which I absolutely love. EDIT: hm, how do I do an inline spoiler...
Anyhoo. Thanks for the replies. Me, I'll be fine either way now that I understand, but for whatever it's worth, I think UFO and Craft values should be consistent.
-
I cannot be the only person who will ever think of using that screen as a quick way to check "can this craft weapon shoot down this UFO before it runs out of ammo".
OK, I'll change it today.
And for the equal mutual surprise fix, which I still don't think is documented but which I absolutely love.
This will take some time.
It's a non-trivial part of the source code and I will need to read it, understand it, test it and dig years into the past to compare all the changes.
But I'll do it eventually (it's todolisted), just need to get in the mood for it.
-
Let's also introduce automatic combat on missions. (Sarcasm)
I don't think this is necessary. The player must think with his own head. And if everything is reduced to automation - why is a player needed then?
-
OK, I'll change it today.
Cool!
This will take some time.
I figured. Pardon me, didn't mean to nag.
-
I cannot be the only person who will ever think of using that screen as a quick way to check "can this craft weapon shoot down this UFO before it runs out of ammo".
OK, I'll change it today.
I say right away - I am categorically against if such a function cannot be turned off.
Let me explain why. It will take you several updates to refine this function, since you need to take into account all the factors (avoidBonus, armor, powerBonus, raceBonus, shieldDamageModifier), otherwise it will all work through ass, as the base defense systems work now. I did not write, because even from the original UFO I was used to defending my bases exclusively by aviation and protective buildings for me are nothing more than decor, but nevertheless.
-
What?
We're talking about the "stats for nerds" screen, which already exists, already provides a "total damage" estimate, and which yes, can be turned off.
-
Apparently the translator failed again.
In "stats for nerds" all of these statistics mean nothing for modifications using the options above. In my modification, a fighter with two AVALANCHEs can shoot down a medium UFO, but will by miss with all missiles at very small UFO, due to the high "avoidBonus". How to take this into account?
And then there's "raceBonus".
raceBonus:
STR_SECTOID:
hitBonus: 100
avoidBonus: 40
radarChance: 10
STR_SNAKEMAN:
damageMax: 3500 #additive bonus to craft stats.
sightRange: 75
hitBonus: 30
STR_FLOATER:
speedMax: 1500 #additive bonus to craft stats.
accel: 5
avoidBonus: 30
STR_GILLMAN:
speedMax: 400 #additive bonus to craft stats.
avoidBonus: 70
powerBonus: 25
radarRange: 150
STR_AQUATOID:
powerBonus: 60
hitBonus: 60
avoidBonus: 30
STR_TASOTH:
speedMax: 250
accel: 1
powerBonus: 100
hitBonus: 50
avoidBonus: 35
armor: 10
radarRange: 150
radarChance: 25
sightRange: 75
STR_LOBSTERMAN:
damageMax: 1750
armor: 40
speedMax: 250
accel: 1
powerBonus: 20
hitBonus: 25
avoidBonus: 50
shieldCapacity: 1000
shieldRecharge: 15
STR_MUTON:
armor: 70 #amount of blocked damage per hit.
speedMax: 250
powerBonus: 50
hitBonus: 55
avoidBonus: 55
STR_ETHEREAL:
shieldCapacity: 2000
shieldRecharge: 30
speedMax: 500
accel: 1
powerBonus: 30
hitBonus: 100
avoidBonus: 50
radarChance: 25
STR_MIXED:
speedMax: 1500 #additive bonus to craft stats.
accel: 5
shieldCapacity: 2000
shieldRecharge: 30
damageMax: 3500 #additive bonus to craft stats.
avoidBonus: 70
hitBonus: 70
powerBonus: 50
radarRange: 150
radarChance: 25
sightRange: 75
STR_MIXED2:
speedMax: 500
accel: 2
avoidBonus: 120
hitBonus: 120
powerBonus: 100
armor: 70
radarRange: 150
radarChance: 25
sightRange: 75
STR_CULT:
hitBonus: 70
avoidBonus: 70
armor: 30
How to take this into account?
-
I say right away - I am categorically against if such a function cannot be turned off.
Yes, "stats for nerds" can be turned off: https://openxcom.org/forum/index.php/topic,8791.0.html
How to take this into account?
These cannot be taken into account.
Same as many other things in the original Ufopedia and in the new Stats for nerds.
-
There is a lot of useful information in "stats for nerds" besides the "assumed" parameters. If only "calculated values" could be turned off, that would be great.
-
For 7.0 yaml tags like `!add` are available for
fixedUserOptions:
recommendedUserOptions:
hiddenMovementBackgrounds:
baseNamesFirst:
baseNamesMiddle:
baseNamesLast:
operationNamesFirst:
operationNamesLast:
-
New OXCE v7.0 is up.
2021-03-13
QoL:
- Extended geoscape/battlescape/inventory links: https://openxcom.org/forum/index.php/topic,9506.0.html
- Touch buttons -- BIG THANKS to robin for the artwork: https://openxcom.org/forum/index.php/topic,9507.0.html
- Renamed and reordered scale modes: https://openxcom.org/forum/index.php/topic,9508.0.html
- New Battle QoL (bigger selectors and quick search): https://openxcom.org/forum/index.php/topic,9510.0.html
- Simplified reordering of the base list (R-click): https://openxcom.org/forum/index.php/topic,4187.msg137203.html#msg137203
- Ability to reorder craft at base (R-click)
- User option for multi-slot battlescape autosaves: https://openxcom.org/forum/index.php/topic,9512.0.html
- User option for (mouse) thumb buttons support (`thumbButtons: true/false` in options.cfg)
- "Not equipped" item category in Craft Equipment UI
Features:
- Save info about special weapons: https://openxcom.org/forum/index.php/topic,9513.0.html
- Save info about loaded fixed weapons in equipment templates: https://openxcom.org/forum/index.php/topic,9514.0.html
- Fixed `maxRange: 1` weapons for 2x2 player units: https://openxcom.org/forum/index.php/topic,9515.0.html
- Check weapon maxRange in 3D: https://openxcom.org/forum/index.php/topic,6459.msg137222.html#msg137222
Modding:
- Extended psi attack experience gains: https://openxcom.org/forum/index.php/topic,4230.msg137247.html#msg137247
- Ability to prevent panic/MC per unit type, also unhardcoded berserk odds per unit type: https://openxcom.org/forum/index.php/topic,8704.msg136773.html#msg136773
- Support for battery-powered weapons: https://openxcom.org/forum/index.php/topic,9293.0.html
- Support for fixed craft weapons: https://openxcom.org/forum/index.php/topic,9047.0.html
- Pilot armors: https://openxcom.org/forum/index.php/topic,9313.0.html
- Adjusted sell prices based on difficulty: https://openxcom.org/forum/index.php/topic,6785.msg135883.html#msg135883
- Research gate to hire scientists/engineers (`hireScientistsUnlockResearch` and `hireEngineersUnlockResearch`)
- More retaliation mission options: https://openxcom.org/forum/index.php/topic,9496.msg137252.html#msg137252
- Ability to override autoNV setting per environment (attribute `ignoreAutoNightVisionUserSetting`)
- Ability to override scanner and probe action names (using existing `psiAttackName` attribute)
- Added `difficultyBasedRetaliationDelay` option again: https://openxcom.org/forum/index.php/topic,6586.msg136997.html#msg136997
- Reset ambient sounds on stage transition in multi-stage missions
Scripting:
- Added access to unit inventory: https://openxcom.org/forum/index.php/topic,5245.msg136806.html#msg136806
- Added syntax for loops
Bugfixes:
- Fixed compliant map block detection in the Reinforcements feature (when using `spawnBlockGroups`)
- Fixed/improved friendly kill tracking: https://openxcom.org/forum/index.php/topic,4595.msg135527.html#msg135527
- Fixed broken Korean fonts: https://openxcom.org/forum/index.php/topic,9486.0.html
- Ignore `LOSRequired` weapon flag when targeting allies and civilians (it's a workaround, LOS check doesn't work in these cases)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator and wiki ruleset reference were updated.
-
Thank you for your work.
-
Great update from what my puny brain understands. I especially like base/craft reordering. Craft thingy actually wrote off an item from my own personal QoL wishlist. Base would probably end on it too had I played enough times to repeat base placing/purpose mistake so props for making those.
Couple of quick questions:
Is Craft reordering only a visual change (when looking at base layout) or does it also include functional reordering when intercept popup is pulled from Geoscape? For example when player wants to have Interceptors followed by Transports within same base listing. Cannot begin to explain how much extra time I spent building an extra hangar in another base just so I could transfer craft away & back again to fully reorder them.
From something I read (probably miss-read) on Discord a ~month ago: is NV a persistent on/off setting now, kept inside the save? Rather than depending on map lighting amount and being turned on/off (depending on threshold value in options) automatically when battle is started/reloaded.
Someone asked where NV setting was and you responded it will be replaced by something better, or something along those lines. Hoping it's an option I missed coz it would be of great use to me. Happens rarer now (since sweet spot treshold=9) but I still occasionally fight with auto-NV setting, turning it on or off manually because threshold value isn't universally viable in all situations. If on/off toggle is part of save then it'd sufficient to toggle it at start of battle and only if I don't already agree with what threshold decided.
I'm pushing my luck but maybe CTRL+END setting could override NV and vice-versa depending which was set last. It does look more beautiful than NV in some cases. Setting would also be persistent in battle saves until a new battle was started (not reloaded) where threshold would take priority. Well so much for being quick about it, sorry!
-
To add to the topic of mutual surprise changes in OXCE: for some extra fun, the situation from the savegame attached results in mutual surprise in OXC, but not in OXCE, the reverse of what I usually experience.
I confess myself confused.
(Not trying to rush you, Meridian, just figured if/when you get to examining the smoke vs sight range issue you might possibly find another datapoint useful. If not, ignore.)
-
All Hi Hi
Suggestion for improving the interface
Is it possible to render in the user's fashion
(on the battlefield screen) own buttons with the specified coordinates, Without using the built-in interface (Battlescape)
or by some other method? Improved button graphics I would do myself (Mode 640 x 400 basic frame)
-
You can change how the buttons look.
You cannot change what the buttons do, nor their position.
-
No need to change button functions
I wanted to change the coordinates and increase the size of the buttons, since the size of the displayed map is too large compared to the size of the panel (320x200 buttons interface). Is it really that hard to just fix 30 ...... 60 numbers
-
ICONS.PCK Battlescape icons
xracer
Control panel is basically done, i have added those last 2 little items for grenades quick access and reload of course functionality for those would need to be added, although i have re-size the icons to give a little more space to the status bar, and to make it fir vanilla size.
if you think there is something else that need to be changed let me know, maybe we can gather every thing and make a "large" mod, I am tinkering with the rest of the GUI to make it fit a 640x400 but not simply 2x everything.
Althought right now i am focused on teh battlescape i think there isn't much that needs to be done there if the loadout screen is used then that covers basically everything, the rest of the GUIS such as the minimap, scanner, medikit will just be centered with the battlescape as background so that it looks like an actual window. Anything else i am missing? maybe i shoudl play the game and go over every GUI again
Rul file syntax: one button
- type: ICONS.PCK
singleImage: true
width: 320
height: 200
files:
0: Resources/DECALS/ICONS.png
- type: KneelButton
width: 32
height: 32
subX: 32
subY: 16
files:
0: Resources/UnitUI/kneelButton.png
-------------------------------------------------------------------------
BattlescapeState.cpp (Names All buttons)
rank icons
rankTiny icons
btnUnitUp icons
btnUnitDown icons
btnMapUp icons
btnMapDown icons
btnShowMap icons
btnKneel icons
btnInventory icons
btnCenter icons
btnNextSoldier icons
btnNextStop icons
btnShowLayers icons
numLayers icons
btnHelp icons
btnEndTurn icons
btnAbort icons
btnStats icons
txtName icons
AvatarBackground
numTimeUnits icons
numEnergy icons
numHealth icons
numMorale icons
barTimeUnits icons
barEnergy icons
barHealth icons
barMorale icons
imanaBarVisible
barMana icons
btnReserveNone icons
btnReserveSnap icons
btnReserveAimed icons
btnReserveAuto icons
btnReserveKneel icons
btnZeroTUs icons
btnLeftHandItem icons slot weapon
btnRightHandItem icons
btnVisibleUnit indicator unit (enemy)
numVisibleUnit number enemy
// there is some cropping going on here, because the icons image is 320x200 while we only need the bottom of it.
auto crop = icons->getCrop();
crop.getCrop()->x = 0;
crop.getCrop()->y = 200 - iconsHeight;
crop.getCrop()->w = iconsWidth;
crop.getCrop()->h = iconsHeight;
It might look like this
tweaked in a graphical editor
original aspect ratio for a resolution of 1024x640
-
How do you define and set the extra damage types?
I see multiple mentions of them in the ruleset reference but no actual way to use them, and my searching was only able to find a mention that yes, they exist, but again nothing about how to use them.
-
I see multiple mentions of them in the ruleset reference but no actual way to use them, and my searching was only able to find a mention that yes, they exist, but again nothing about how to use them.
https://openxcom.org/forum/index.php/topic,6577.msg103384.html#msg103384
-
I recreantly add option to script to allow setting custom spawn units to any unit, it still have some corner cases but overall should work as expected.
This feature have to additional functionalities, you can set what faction of spawned unit will be, and if transformation will be instant or only when unit is stunned/killed
-
Dear Meridian, could you expand the numeric value for the oxceAutoNightVisionThreshold option to 16?
What for? To enable and disable the Night Vision mode in battle. At least in the settings. And it would be better if there was another hotkey, but this is not necessary.
Backlighting with a "space" is enough for me, and with forced automation, the entire atmosphere of the original disappears in night battles.
-
Dear Meridian, could you expand the numeric value for the oxceAutoNightVisionThreshold option to 16?
What for? To enable and disable the Night Vision mode in battle. At least in the settings. And it would be better if there was another hotkey, but this is not necessary.
Backlighting with a "space" is enough for me, and with forced automation, the entire atmosphere of the original disappears in night battles.
You can use value 15 to disable the night vision.
Values 16, 17, 18, and so on would only do the same as 15.
-
Unfortunately, there are maps with 15 shading. And these are the settings of the original. Try it yourself.
UFO - UBASE, MARS.
TRTD - GRUNGE, ENTRY, ALSHIP, LEVEL, CRYPT.
-
Unfortunately, there are maps with 15 shading. And these are the settings of the original. Try it yourself.
UFO - UBASE, MARS.
TRTD - GRUNGE, ENTRY, ALSHIP, LEVEL, CRYPT.
I know.
Setting 15 means "darker than 15", "relevant for shade higher than 15", "relevant for shade > 15", "relevant for shade higher or equal than 16" or "relevant for shade >= 16".
Hope that clarifies it.
With setting 15, OXCE will *not* automatically turn on night vision under any circumstance.
Just try it yourself.
-
Understood thanks. Found a mistake in myself, there were maps with shading 16. I will fix it.
-
Not sure if this is the right place, but I have recently run into trouble with prison types in XCF.
Cyberweb robotic units - robosphere/turret (or rather their respective items upon recovery) - don't have an assigned prison type. They die upon recovery if no alien containment unit exists. They however do not take up any prisoner slot in the containment unit and are not trasferred to a base having a containment unit either.
I am not sure this intended or a fall back for "vanilla" units (i.e. those without a separate prison type). What would be the correct way to define a recoverable alien unit that takes up no prison slot/type?
-
There is always a prison type, default is 0.
Check if you have correctly set the `liveAlien` flag.
-
There is always a prison type, default is 0.
Check if you have correctly set the `liveAlien` flag.
No, those units don't have that flag set (on purpose I guess, since they are robotic). Do all recoverd units check for a matching/existing prison type, regardless of the flag? Is it possible to skip that check?
-
It's simple.
Stuff with `liveAlien: false` goes into stores.
Stuff with `liveAlien: true` goes into alien containment.
Nothing else depends on this flag.
This is its only purpose, by design.
Once it has been determined that an item belongs to an alien containment... then the `prisonType` attribute kicks in and says to which particular alien containment facility should it go.
-
Sorry, it's my fault. I'll fix the problem soon.
-
It's simple.
Stuff with `liveAlien: false` goes into stores.
Stuff with `liveAlien: true` goes into alien containment.
Nothing else depends on this flag.
This is its only purpose, by design.
Once it has been determined that an item belongs to an alien containment... then the `prisonType` attribute kicks in and says to which particular alien containment facility should it go.
But that is not how it works, apparently. Regardless of the flag setting the units die if no facility with 'prisonType: 0' exists:
- type: STR_CYBERWEB_ROBOSPHERE_TERRORIST
categories: [STR_HUMAN_TECH, STR_ROBOTS]
size: 0.0
recover: true
costSell: 50000
listOrder: 144710
dies during recovery when no alien containment exists.
- type: STR_CYBERWEB_ROBOSPHERE_TERRORIST
categories: [STR_HUMAN_TECH, STR_ROBOTS]
size: 0.0
recover: true
costSell: 50000
listOrder: 144710
liveAlien: false
also dies.
Hence my question regarding the proper way to define a recoverable alien unit/item that does not require a prison type.
Addendum to this:
The only way to recover them is to also set an existing (i.e. already built) prison type:
- type: STR_CYBERWEB_ROBOTURRET_TERRORIST
categories: [STR_HUMAN_TECH, STR_ROBOTS]
size: 0.0
recover: true
costSell: 20000
listOrder: 144720
liveAlien: false
prisonType: 1
Recovers correctly if a 'prisonType: 1' facility exists at any base.
-
Actually I want to add prison type 4 (robots), but put it on general stores, so you don't need yet another building.
-
Actually I want to add prison type 4 (robots), but put it on general stores, so you don't need yet another building.
Isn't the issue that the flag does not work correctly? Setting 'liveAlien: false' should enable players to recover them as items.
-
Isn't the issue that the flag does not work correctly? Setting 'liveAlien: false' should enable players to recover them as items.
Even if, I'd rather do this the "proper" way. :)
-
But that is not how it works, apparently. Regardless of the flag setting the units die if no facility with 'prisonType: 0' exists:
If everything is right, you get a live alien item.
If anything is wrong, you get a corpse item.
Hence my question regarding the proper way to define a recoverable alien unit/item that does not require a prison type.
All recoverable units need a liveAlien flag and optionally a prisonType (defaults to 0 if not defined).
Same as in OXC.
There is no such thing as "without a prison type"... that's simply not a thing.
Ask differently if you think I didn't understand the question... but the only answer to "can I have an item without a prison type" is "does not compute".
If you want to recover something completely else than a unit, there are (several) other ways how to do it.
-
I think my confusion stems from this:
Stuff with `liveAlien: false` goes into stores.
Stuff with `liveAlien: true` goes into alien containment.
Nothing else depends on this flag.
This is its only purpose, by design.
Once it has been determined that an item belongs to an alien containment... then the `prisonType` attribute kicks in and says to which particular alien containment facility should it go.
From what I can tell the first thing that is checked is the prison type and whether a facility with that type exist - if it does not then a corpseItem is recovered, regardless of the 'liveAlien' flag. The flag only comes into play if a corresponding prison type exists - then it is used to dertermine if the recovered item counts towards alien containment.
-
On some places the flag is checked first, the prison type second. For example here, if you need a proof: https://github.com/MeridianOXC/OpenXcom/blob/oxce-plus/src/Battlescape/DebriefingState.cpp#L2519
On other places the prison type is checked first, the flag second.
In both cases the outcome is the same.
See diagrams for both cases as visual explanation.
If both conditions are satisfied (regardless of the order in which they are checked), you get a prisoner... otherwise (if any condition is not satisfied), you don't get a prisoner.
-
Thanks for the explanation :D
-
In today nightly I push change with more aggressive checking of mod data, this mean some mods could not load any more.
As most of this checks was to prevent bugs in mod that crash in game I added option to ignore them in user config:
oxceModValidationLevel: 1
Available levels:
0 - expected game behavior is random crash at run time, any problems encounter at this level will not be fixed in any way, only guarantee is loading main menu.
1 - game should not crash, but behavior could not that you could expect, only crash at this level will be fixed.
2 - default level game should run correctly, any problem at this level could mean bugs in engine and all should be fixed.
3 - (not used yet) pedantic checks that do should not affect in any way behavior of game
-
Question:
Is it currently possible to restrict inventory slots to certain items (instead of restricting items to certain inventory slots)?
-
Is it currently possible to restrict inventory slots to certain items (instead of restricting items to certain inventory slots)?
no
-
In today nightly I push change with more aggressive checking of mod data, this mean some mods could not load any more.
As most of this checks was to prevent bugs in mod that crash in game I added option to ignore them in user config:
oxceModValidationLevel: 1
Available levels:
0 - expected game behavior is random crash at run time, any problems encounter at this level will not be fixed in any way, only guarantee is loading main menu.
1 - game should not crash, but behavior could not that you could expect, only crash at this level will be fixed.
2 - default level game should run correctly, any problem at this level could mean bugs in engine and all should be fixed.
3 - (not used yet) pedantic checks that do should not affect in any way behavior of game
Here is the new build, OXCE v7.0.5 (2021-05-02):
win64: https://lxnt.wtf/oxem/builds//Extended/Extended-7.0.5-7408661e9-2021-05-02-win64.7z
win32: https://lxnt.wtf/oxem/builds//Extended/Extended-7.0.5-7408661e9-2021-05-02-win32.7z
linux/ubuntu: https://lxnt.wtf/oxem/builds//Extended/Extended-7.0.5-7408661e9-2021-05-02-bionic-x86_64.7z
This build is meant for modders only, not for players.
Modders, please update your mods to comply with the validation rules.
Yankes and I are available to answer your questions:
1. here on the forum
2. or on the OpenXcom discord
3. or on the X-Piratez discord
If you think some validations are not correct, please contact Yankes.
PS: the official OXCE v7.1 release is planned for late summer (probably August 2021)... I hope that's enough time to update all actively developed mods.
-
- on OpenXcom discord
- on X-Piratez discord
Very funny. And what should I, Russian-speaking, do? Not only was the most important discussion moved to some kind of ass of world, so also ustonavlivat additional (unnecessary for me) software.
Stop this practice and return the discussion to this site.
-
The first option on the list was "here".
Discords were only the second and third option.
-
Announce the list of changes in OXCE v7.0.5, please.
-
Changes in OXCE 7.0.5
QoL:
- none
Features:
- added more ruleset validations
Modding:
- none
Scripting:
- none
Bugfixes:
- Craft returning after mission don't join dogfights
- Fixed instant mission despawn
-
Some bugs (I think?) I have recently encountered:
Under certain circumstances unit positions are not updated correctly after terrain is destroyed. Case in point, the sectoid failed its melee check (aliens turn) and fired into the ground, destroying the tile underneath itself without actually falling down. Unit position was only updated correctly after he died/was stunned:
(https://abload.de/thumb/screen001elkrv.png) (https://abload.de/image.php?img=screen001elkrv.png)
(https://abload.de/thumb/screen002nwj33.png) (https://abload.de/image.php?img=screen002nwj33.png)
(https://abload.de/thumb/screen0033qje1.png) (https://abload.de/image.php?img=screen0033qje1.png)
Randomly generated base names can lead to overflow of chraracter space, resulting in a change in change of font size and enabling the player to use names >13 characters in length:
(https://abload.de/thumb/screen005mhjuw.png) (https://abload.de/image.php?img=screen005mhjuw.png)
(https://abload.de/thumb/screen006l1kqu.png) (https://abload.de/image.php?img=screen006l1kqu.png)
Not sure if this intended or of this can be enabled seperately - I'd actually like to have this option in the game so I don't have to shorten names too much.
-
Under certain circumstances unit positions are not updated correctly after terrain is destroyed. Case in point, the sectoid failed its melee check (aliens turn) and fired into the ground, destroying the tile underneath itself without actually falling down. Unit position was only updated correctly after he died/was stunned:
I'd need some way to reproduce, best a save just before.
Randomly generated base names can lead to overflow of chraracter space, resulting in a change in change of font size and enabling the player to use names >13 characters in length:
Modders have been warned to make the names short.
Not sure if this intended or of this can be enabled seperately - I'd actually like to have this option in the game so I don't have to shorten names too much.
No, it's automatic.
You can change the name in the save if you want... but small base names look awful (and don't fit into tables).
-
I'd need some way to reproduce, best a save just before.
:P
Modders have been warned to make the names short.
Off to the modding subforum I go.
[...]but small base names look awful (and don't fit into tables).
Shortened base names also look awful, but I get why this would be even more impractical.
-
Question:
Facilities can be built over existing facilties (buildOverFacilities). Is it possible to reduce cost of the new facility (or refund cost of the old facility) to simulate "upgrading" facilities (i.e. upgrading from level 1 to level 2 costs less than building a new level 2 facility)? It is possible to refund money using refundValue, but this applies for dismantling in general, not only for building over an existing facility.
Additonal question (though I am not sure if this belongs here or under help):
How exactely is weapon position on units defined in regards to shot trajectory? Are terrain slopes acurately represented on the battlescape?
Case in point, I just got shot at by an alien unit (gazer) which I presume should have been occluded by terrain (the weapon, at least):
(https://abload.de/thumb/screen016ezksb.png) (https://abload.de/image.php?img=screen016ezksb.png)(https://abload.de/thumb/fpslook00398kof.png) (https://abload.de/image.php?img=fpslook00398kof.png)(https://abload.de/thumb/fpslook004dtjtv.png) (https://abload.de/image.php?img=fpslook004dtjtv.png)(https://abload.de/thumb/fpslook0058kjtg.png) (https://abload.de/image.php?img=fpslook0058kjtg.png)
(last image is the position I got shot at)
Where exacately are weapons located on units?
-
Facilities can be built over existing facilities (buildOverFacilities). Is it possible to reduce cost of the new facility (or refund cost of the old facility) to simulate "upgrading" facilities (i.e. upgrading from level 1 to level 2 costs less than building a new level 2 facility)? It is possible to refund money using refundValue, but this applies for dismantling in general, not only for building over an existing facility.
It's only possible via refundValue.
How exactly is weapon position on units defined in regards to shot trajectory?
It's usually 3 or 4 voxels below the unit's current height.
For humanoids this corresponds to "shoulder level".
Exact formula: https://github.com/MeridianOXC/OpenXcom/blob/oxce-plus/src/Battlescape/TileEngine.cpp#L5006
Are terrain slopes accurately represented on the battlescape?
Depends on the modder.
-
It's only possible via refundValue.
:'(
It's usually 3 or 4 voxels below the unit's current height.
For humanoids this corresponds to "shoulder level".
Exact formula: https://github.com/MeridianOXC/OpenXcom/blob/oxce-plus/src/Battlescape/TileEngine.cpp#L500
Thanks, that's higher than I would have expected. Are individual/custom unit heights represented in 3D-view or is the same cylinder usaed for all (small) units?
Depends on the modder.
Let me rephrase that: Are terrain slopes of vanilla terrain tiles accurately represented by their LOFTs?
Addendum:
Is there a known issue with (limited) alien storage and the recovery-phase transfer screen? I have just now run into a situation where I am forced to discard units, but they have gotten mixed up with aliens being studied at another base (originating base has no containment, other base does). I am unable to exit the screen as I have ended up with negative alien storage, studied specimens can not be discarded and I have no other free storage I can transfer that alien to:
(https://abload.de/thumb/screen0183nk5x.png) (https://abload.de/image.php?img=screen0183nk5x.png)
-
Thanks, that's higher than I would have expected. Are individual/custom unit heights represented in 3D-view or is the same cylinder used for all (small) units?
unit height is considered
Let me rephrase that: Are terrain slopes of vanilla terrain tiles accurately represented by their LOFTs?
No other way to find out than to check them all manually.
Addendum:
Is there a known issue with (limited) alien storage and the recovery-phase transfer screen?
no
-
no
I have just had a look at my recent saves, and I somehow managed to recover live aliens to a base that does not actually have that specific prison type. Are there any known issue concerning live recovery where such recovery should not be possible?
-
I have just had a look at my recent saves, and I somehow managed to recover live aliens to a base that does not actually have that specific prison type. Are there any known issue concerning live recovery where such recovery should not be possible?
no
-
no
I'll see if I can manage to reproduce it and/or if it turns up again.
-
Hi.
Small question:
damage "toMana:" applies when damage >0 and deals % of it.
But how can i do flat (let's say 5) mana damage?
-
Not available via ruleset.
But likely doable via scripts.
-
Ok, got it. Thanks.
-
Question:
Is it possible to tie mission site spawns to an active infiltration state (i.e. spawn a mission site provided a country has been infiltrated&an associated alien base exist)? Sorry if this is badly worded.
-
Likely not the way you're thinking, but you can make infiltrations use an alien base deployment that generates the missions you want separate from any other type of alien base.
-
Likely not the way you're thinking, but you can make infiltrations use an alien base deployment that generates the missions you want separate from any other type of alien base.
Unless I am misunderstanding the ruleset reference genMission can not generate mission sites, only UFOs:
Which alien mission should this base generate?
Usually supply mission - can be used to generate any mission type except Mission Sites (UFO will be generated, but the site will never appear)
-
We generate terror missions all the time from bases in 40k. That is an old restriction, since lifted.
You could also use the operationType attributes on the alienMission to make it scripted but still require a certain type of base.
-
We generate terror missions all the time from bases in 40k. That is an old restriction, since lifted.
You could also use the operationType attributes on the alienMission to make it scripted but still require a certain type of base.
Thanks for the heads up. Are (or rather can) missions generated from an alien base be limited to the region of the base?
How would I reference "a certain type of alien base" in operation Type (apart from a new or existing alien base, unless that is what you are referring to)? Would it be possible to tie this only to alien bases causing an infiltration?
-
Don't want to start a new thread for this, but I have a quick question.
It looks like the Android port of OXCE uses SDL_Mixer2 - any chance of that change being back-ported to the pc version (And ideally backported all the way to vanilla OpenXCom)? SDL_Mixer2 should support the LOOPSTART and LOOPEND .ogg metadata tags, which will allow me to make better MT-32 music packs.
-
It looks like the Android port of OXCE uses SDL_Mixer2 - any chance of that change being back-ported to the pc version (And ideally backported all the way to vanilla OpenXCom)?
Yes, and there is a branch in the OpenXcom repository too if you want to test it: https://github.com/OpenXcom/OpenXcom/tree/sdl2
It compiles and runs in the basic mode.
But OpenGL rendering doesn't work.
Anyway, the plan is to migrate to SDL2 after OpenXcom 2.0 is released... which may be next month, next year, or also never. Only time will tell.
-
Stupid question: where I can get old source code to build myself? Getting crashes in Arch Linux and Windows too now. It might be mod related (TWoTS) but I'm not sure, so I need old source codes for it to rebuild and test before posting unverified info here. As far as I know (correct my stupidity again) git has latest version now, but how to get old (interested in 6.9)?
-
Stupid question: where I can get old source code to build myself? Getting crashes in Arch Linux and Windows too now. It might be mod related (TWoTS) but I'm not sure, so I need old source codes for it to rebuild and test before posting unverified info here. As far as I know (correct my stupidity again) git has latest version now, but how to get old (interested in 6.9)?
Git contains the entire version history since the very first commit.
-
OK, I think I got it. Only problem what I cant' find latest commit number (or should I said hash instead) for last 6.9.1 version. Compiled 6.8.4 instead.
-
OK, I think I got it. Only problem what I cant' find latest commit number (or should I said hash instead) for last 6.9.1 version. Compiled 6.8.4 instead.
you can see commit numbers here: https://openxcom.org/oxce/release/
6.9.1 is https://github.com/MeridianOXC/OpenXcom/commit/85681b6a4
-
Thank you very much for you time and info. The problem what I'm still not very good with git command and it's sub commandants (git checkout and etc), so I stuck a bit there. But now cloned, changed to 6.9.1 commit number, builded, packed to local package and installed. Everything working fine. The crashes what I've encountered early based on mod files and changes in new OXCE 7.0 version. Let's wait while author of the mod will check it and made necessary changes to make it compatible with 7.0.
-
I am having trouble understanding/debugging marker names / IDs, case in point being XCF and alien bases:
The marker name assigned to alien bases is called STR_ALIEN_BIG_BASE:
- type: STR_ALIEN_BIG_BASE_ASSAULT
enviroEffects: STR_INSANITY_4
genMission:
STR_BASE_PATROLING_MEDIUM_SCOUT: 30
STR_BASE_PATROLING_LARGE_SCOUT: 22
STR_BASE_PATROLING_ABDUCTOR: 18
STR_ALIEN_SUPPLY: 12
STR_MIB_BASE: 3
genMissionFreq: 5
markerName: STR_ALIEN_BIG_BASE
STR_ALIEN_BIG_BASE is also defined as StringID in the language file
STR_ALIEN_BIG_BASE: "Alien Colony"
However, in-game the marker name has an attached underscore and is accordingly displayed as
STR_ALIEN_BIG_BASE_
as the string is (obviously) not defined in the language file.
I am trying to understand why this is the case. The ruleset reference does not list anything in regards to that and other strings are converted as is. Is the underscore necessary to pass IDs (e.g. alien base 1, 2, 3 etc.)?
-
save?
can this be reproduced or is it some mod version upgrade artifact?
-
save?
can this be reproduced or is it some mod version upgrade artifact?
Happened in a new game without mods and has also been reported by other users. Attached is a modified save file which should spawn a new alien base at the end of the month (either in UK/Europe or in the Falklands). The alien base name is displayed as "STR_ALIEN_BIG_BASE_".
To clarify, this is a base spawned due to infiltration. I don't know if the naming mechanics are different for bases that are spawned normally. The marker name is correctly parsed as a string if the underscore is added in the language file (i.e. STR_ALIEN_BIG_BASE_: "Alien Colony").
OXCE version is 7.0 (2021-03-13).
-
save?
can this be reproduced or is it some mod version upgrade artifact?
Happened today, on XCOM Files.
Active mods are XCOM Files 1.8b and Dark Geoscape.
Edit: Game version is 7.0, and since either game or mods were updated pased several months, both real and in-game.
-
I've had this issue since forever and never could understand what was causing it...
-
save?
can this be reproduced or is it some mod version upgrade artifact?
Meridian, any update on this (provided you are not on holidays, busy, sick or otherwise engaged)? Where you able to reproduce the issue?
-
Unfortunately I am not feeling well.
I am also taking vacation to recover, starting on Friday (tomorrow).
I will be completely offline for the next 3+ weeks.
-
I hope you are feeling better soon.
Take it easy.
-
Unfortunately I am not feeling well.
I am also taking vacation to recover, starting on Friday (tomorrow).
I will be completely offline for the next 3+ weeks.
Get well soon. More tea with lemon and everything will pass.
-
Unfortunately I am not feeling well.
I am also taking vacation to recover, starting on Friday (tomorrow).
I will be completely offline for the next 3+ weeks.
:-[
Get well soon Meridian, take it easy.
-
Unfortunately I am not feeling well.
I am also taking vacation to recover, starting on Friday (tomorrow).
I will be completely offline for the next 3+ weeks.
Take as much time as you need to recover, personal health is crucial.
I hope you'll get better soon.
-
Mod size limit in XcomFiles 1.7b is 3000, not 2000.
Just install the mod properly and don't mix it with old versions or anything.
It's really easy.
Hi Meridian,
because I need to update OXCE and the Mod I ask here again.
How do I do this "properly"? It confuses me all the time when I try to update.
-
Hi Meridian,
because I need to update OXCE and the Mod I ask here again.
How do I do this "properly"? It confuses me all the time when I try to update.
I am not Meridian, but I will answer anyway.
1. Delete the original mod in {your path}/user/mods/
2. Copy new mod directory into {your path}/user/mods/
That is how I update mods. It is slower than just copying (replace older) the new files in, but makes sure that any files that should no longer exist are removed.
-
1. Delete the original mod in {your path}/user/mods/
2. Copy new mod directory into {your path}/user/mods/
I second this. This is the only surefire way to avoid unintended behaviour/bugs/other mod-related weirdness in case ruleset-definitions, filenames, etc. change between versions.
-
I pushed two experimental UI features by Buscher:
One is sending multiple crafts as "wing" using shift (one is leading, rest is following it)
Second is option for continuing given mission after HK attack
There will be some tweaks and updates to it.
-
How do I change the mana skill in soldierTransformation? Is there some trick?
soldierTransformation:
- name: STR_ELITE_TRAINING_A
flatOverallStatChange:
psiStrength: 5 # works fine in OXCE 7.0
- name: STR_ELITE_TRAINING_B
flatOverallStatChange:
mana: 1 # does not work in OXCE 7.0
- name: STR_ELITE_TRAINING_C
flatOverallStatChange:
manaPool: 1 # does not work in OXCE 7.0
-
soldierTransformation:
- name: STR_ELITE_TRAINING_B
flatOverallStatChange:
mana: 1 # does not work in OXCE 7.0
this one works just fine for me...
-
Thanks for help.
After searching I found my mistake: There was an
"upperBoundAtMaxStats: true"
and mana limits not in my mind. Now all is fine. :)
-
Having a play through of Vanilla XCOM: UFO Defense with my kid and he mentioned something - In X Piratez we could see status indicators for units that were stunned, bleeding etc. However we couldnt see such when using OpenXcom Extended - did I miss the option for it or is there a mod that adds it? I didnt want to open a new thread for this.
-
Having a play through of Vanilla XCOM: UFO Defense with my kid and he mentioned something - In X Piratez we could see status indicators for units that were stunned, bleeding etc. However we couldnt see such when using OpenXcom Extended - did I miss the option for it or is there a mod that adds it? I didnt want to open a new thread for this.
It requires a mod.
I haven't seen a standalone mod just for this around, but it is easy to create once you have the images.
-
Thanks Meridian.
-
- Craft returning after mission don't join dogfights
Meridian, please make it an option that can be enabled or disabled as desired.
Although recently an aggressive UFO destroyed my ship returning from a mission, the player himself must take measures to prevent such a development of events and send interceptors to escort the transports. I made a mistake and was punished, but I am against the elimination of this threat.
-
- User option for (mouse) thumb buttons support (`thumbButtons: true/false` in options.cfg)
Is there something setup-specific about this, or does it always default to 'false'? Because if I hadn't remembered this from earlier versions and gone looking for how to re-enable it, I would never have suspected it was a thing.
-
Is there something setup-specific about this, or does it always default to 'false'? Because if I hadn't remembered this from earlier versions and gone looking for how to re-enable it, I would never have suspected it was a thing.
Always defaults to false.
-
There is one more option for the players.
Ctrl+X (during idle BattleScape) toggles unit response sounds on/off.
Yes, it is much more convenient. Can add such a function to the "Links" menu?
-
How to remove the measurement system in miles? In the original there was a metric system, and now go to "stats for nerds" and see some horror, in the form of speed in knots and distance in miles. How to get rid of this?
-
How to remove the measurement system in miles? In the original there was a metric system, and now go to "stats for nerds" and see some horror, in the form of speed in knots and distance in miles. How to get rid of this?
Can you post an example/screenshot. I don't know what you mean.
-
Can you post an example/screenshot. I don't know what you mean.
Screenshots. I wanted to say that all these recalculations between miles and kilometers are unnecessary. I would really like to see in" stats for nerds " only what is written in the ".rul "file, and how to name these conditional units, everyone should decide for himself, through "extraStrings".
I don't know how to say it better... In general, need a toggle of basic calculus systems. We have adopted the metric system in Russia and no one measures anything in knots and miles. I set the characteristics of objects and write descriptions guided by the metric system (I don't know any others), and as a result, some kind of mess turns out.
-
In the original there was a metric system
You said that in the original there was a metric system.
If there is a difference between the original and OpenXcom somewhere, I'm willing to fix it (unless it was a clear bug in the original)... but you didn't show any difference to the original.
As for "stats for nerds", it shows true units as used for real calculations.
I also have no idea how much a mile or a knot is... I'm from Europe... that's why I added conversion to kilometers and to km/h.
But the originals will stay because that's how they are written in rul files and both modders and players deserve to see the true ruleset values, which is the primary purpose of "stats for nerds".
-
So I ran UFO: Enemy unknown in DOSBox to check it.
Turns out, it was inconsistent.
Radar ranges in miles, Aircraft armament ranges in KM, Aircraft speeds without units.
-
So I ran UFO: Enemy unknown in DOSBox to check it.
Turns out, it was inconsistent.
Radar ranges in miles, Aircraft armament ranges in KM, Aircraft speeds without units.
This, of course, makes some mess in a clear picture. I was also surprised by this. I were even more surprised by the three Russifications for the dos version. In one, everything is translated into kilometers, in another into miles, in the third... It is better to delete the third Russification and forget it as a terrible dream.
-
I don't worry whether it's in kilometers or miles as long as it's listed which one it is and the values are correct. I just think of it as Magic Numbers A and Magic Numbers B, because they're really just good for comparison to each other.
For those who don't know, 1 knot is 1 nautical mile per hour. The base game uses knots for speed and nautical miles for distance on the geoscape, and it uses km for distance in the interception window. With knots vs nautical miles, you're really just comparing aircraft speed to flight distance, or flight time, so you don't need to know how far a nautical mile is. Similarly, in the interception window, you're simply comparing one weapon's range with another weapon's range, so you don't need to know how long a kilometer is.
-
Hey Yankes,
Just wondering if your YAML syntax for mod extensions supports starting base?
Like the following
startingBase:
facilities: !add
- type: STR_GENERAL_BUILDING
x: 3
y: 2
or
startingBase:
items: !add
STR_MARK_I_ARMOR: 1
also, is it possible to update properties of items without rewriting the entire items properties like such
ufopaedia:
- id: STR_LMG
requires: !add
- STR_ADVANCED_FIREARMS
- id: STR_LMG_CLIP
requires: !add
- STR_ADVANCED_FIREARMS
- id: STR_LMG_AA_CLIP
requires: !add
- STR_ADVANCED_FIREARMS
or not sure on this one either?
- type: STR_AUTO_CANNON
tuAuto: 40
tuSnap: 28
tuAimed: 60
autoShots: 6
I'm currently testing, but the starting base isn't working.
Thanks!
-
Answer is simple `!info` will give you hit if given node support this.
For given question, `startingBase` do not support this, overall this nodes have specific handling that prevent use of this functionality.
For `ufopaedia` is not implemented but could be supported.
-
Can the turret be turned for tanks 85mm and 60mm cannons?
I searched through the forum, but only found CTRL + RMB and touch buttons. They don't work: my whole tanks are turning, just like the RMB function on all units.
-
Can the turret be turned for tanks 85mm and 60mm cannons?
I searched through the forum, but only found CTRL + RMB and touch buttons. They don't work: my whole tanks are turning, just like the RMB function on all units.
You need the "alternate movement methods" user setting turned on (the one that enables running and strafing).
-
I'm guessing this is a problem with X-Com files, but maybe an underlining issue with OXCE. I'm running v7.0 13 Mar 2021 and XCF v2.0.1 as of 6d ago. I figure I'd post here instead of on github ticket since it doesn't look like that option is enabled. Posting on openxcom.org/forum OXCE & on mod.io --> X-Com Files, not sure who would ultimately track this issue.
-Issue
Caused By:
-- UFO detected --> Intercept with 'public car' --> UFO detection lost --> choose 'patrol'
Effect:
-- public car immediately disappears from globe geoscape --> open up base menu, equip craft --> shows the craft is at the base currently --> next time an event comes up and choose intercept with same 'public car' --> it immediately appears at the location that it dispersal.
sorry I didn't have a save file for reproducing this.
-JC
-
Sorry, I don't understand the description, too much stuff going on.
Can you create just a single list of numbered steps to follow? And clearly highlight the step which contains the unexpected behaviour.
(And most likely the save will be needed too)
-
Yeah, sorry for the confusion.
This is early in the game progression of X-Com Files modpack, before blackops unlocked
Geoscape view
1.) UFO Detection
2.) Choose "Intercept"
3.) Choose "Public/Car"
4.) Public/Car is flying towards UFO
5.) UFO tracking lost
6.) At Menu "what to do with craft" - choose 'patrol'
Effect[1] 'public/car' yellow dot on geoscape immediately disappears.
7.) Immediately goto Base Menu
8.) Goto Equip Craft Menu
9.) 'public/car' shows 'ready' and is at the base
Expected[1] 'public/car' should be 'returning' and showing up as moving yellow dot on geoscape globe
10.) Later... another mission pops up on the geoscape view
11.) Choose intercept
12.) Choose public/car (the same one that disappeared earlier) (this will also be the very next time to choose this craft)
Effect[2] 'public/car' yellow dot immediate appears at the location on the globe where it disappeared, (not originating from the base location)
After that I didn't see this glitch again. and didn't think to post/comment on it until any save games around the time of the glitch were all overwritten with later in the game progression.
-JC
-
You need the "alternate movement methods" user setting turned on (the one that enables running and strafing).
It was the tank type. Tanks with 85mm or 60 cannons have fixed turrets, they cannot turn it. You can also see on the sprite as the turret and tank body is shaded and rendered to flow together way too photo-perfectly.
While the Cars with automatic grenade launchers have a tiny turret, which is easily separated into its own sprite. Because of the separation the shading and rendering is not continous, but a clear edge made of black pixels.
Rotatable turrets for the tanks would have been a lot of extra work.
-
It was the tank type. Tanks with 85mm or 60 cannons have fixed turrets, they cannot turn it. You can also see on the sprite as the turret and tank body is shaded and rendered to flow together way too photo-perfectly.
While the Cars with automatic grenade launchers have a tiny turret, which is easily separated into its own sprite. Because of the separation the shading and rendering is not continous, but a clear edge made of black pixels.
Rotatable turrets for the tanks would have been a lot of extra work.
OK, no problem.
I don't even know which tanks or even which mod you're talking about.
Mod questions normally belong to mod threads, try to keep this thread for engine questions :)
-
Engine's bug, maybe.
No TU cost is shown for travelling in flying suit from a craft with a ramp to a place somewhere near the right side of the craft, on the same 2nd level. It happens only when the flying unit needs to move diagonally on the ramp in order to get around another unit standing on the ramp. See the picture and the saved game (X-COM Files mod).
-
Another bugreport from the same battlescape, about floating weapon.
Steps to reproduce:
1. Kill a floater flying in the 3rd level with powerful plasma to get the body disintegrated.
2. Watch floater's weapon floating in the air on the same 3rd level.
The lucky shot was made with Fire glove, it is X-COM Files mod.
There is a save in the attached ZIP, it was made right after the shot.
-
Engine's bug, maybe.
No TU cost is shown for travelling in flying suit from a craft with a ramp to a place somewhere near the right side of the craft, on the same 2nd level. It happens only when the flying unit needs to move diagonally on the ramp in order to get around another unit standing on the ramp. See the picture and the saved game (X-COM Files mod).
And what's the problem?
The unit is not flying through that tile, it flies diagonally.
-
Another bugreport from the same battlescape, about floating weapon.
Steps to reproduce:
1. Kill a floater flying in the 3rd level with powerful plasma to get the body disintegrated.
2. Watch floater's weapon floating in the air on the same 3rd level.
The lucky shot was made with Fire glove, it is X-COM Files mod.
There is a save in the attached ZIP, it was made right after the shot.
We'll have a look at this.
If not difficult, it will be fixed.
-
Thanks!
As for the previous post (https://openxcom.org/forum/index.php/topic,6586.msg141184.html#msg141184):
There are no tiles with TU cost shown between the "24" one and the cursor. Marked this area with orange colour.
-
Although not familiar with the geometry of that craft. It could be that the shortest path (according to the algorithm) is by going up one (or multiple?) level(s), which will not be visible in that screenshot.
Just to be sure: did you check if those numbers are not visible when using the viewpoint with an additional layer (mouse-wheel up on my system)?
-- edit --
Some grammar errors
-
There are no tiles with TU cost shown between the "24" one and the cursor. Marked this area with orange colour.
Upload a save to reproduce please.
-
Not sure if this this is intended or an issues, but the sell/sack screen has inconsistencies , middle or right clicking on items some times shows the ufopedia, sometimes shows the research tree and sometimes nothing even when the research is completed and has the ufopedia page accessible.
I would expected it would function the same as in the craft equip armament screen where middle right clicking would bring up the ufopedia.
-
Right-click doesn't do any of that.
Right-click always shows the manufacturing dependencies.
Middle-click used to always do just the research tree in the past (nice and consistent), but people wanted to have also Ufopedia, so now both are supported (in a complicated way) as follows:
for items:
1. Just Middle-click opens research tree if possible... if not possible, open Ufopedia... if not possible, nothing
2. CTRL+Middle-click opens Ufopedia if possible
for craft:
Middle-click opens Ufopedia
-
Thanks Meridian!
Something else I noticed, when changing the game release under mods, from ufo, tftd, or x-com files. each version doesn't retain it's own copy of setting under the advanced options.
I know some mods, like twots and x-com files specifically sets, changes and locks out options like, x-com files sets explosion radius to 2, but when I go back to tftd or ufo, those setting stay changed. It would be nice to have the advanced setting stored and remembered for each game type.
-
Something else I noticed, when changing the game release under mods, from ufo, tftd, or x-com files. each version doesn't retain it's own copy of setting under the advanced options.
As designed.
You can either use multiple installations of OpenXcom...
...or just have multiple shortcuts for each mod and specify the user and/or config folder as a command-line parameter.
-
Upload a save to reproduce please.
Here is the save.
-
Although not familiar with the geometry of that craft...
Just to be sure: did you check if those numbers are not visible when using the viewpoint with an additional layer (mouse-wheel up on my system)?
I did not check it in the multilayer mode, because I checked it in other way. Just move the agent standing on the ramp and the numbers will appear. The save is in the previous post. The mod is X-COM Files, if you want to check yourself.
-
Here is the save.
The tiles through which the pathfinding goes are still undiscovered, so the pathfinding doesn't render anything on them.
And before you ask, no I don't know why the ground tiles are discovered and one level above they are not.
-
The tiles through which the pathfinding goes are still undiscovered, so the pathfinding doesn't render anything on them.
Thank you for the investigation!
-
Touch buttons keep disappearing = Unselected
Clicking on the ≡ I can turn on Touch buttons display. It works for ~two of my soldiers, then when I switch to the next one, the touch buttons turn OFF.
Is there a way to force these touch buttons to be displayed for the remainder of the battle? OXCE 7.0 for XPiratez. Is this a bug?
I tried to upgrade to one of the latest OXCE nightlies, but unfortunately the latest versions give a nasty ARMOR definition bug when XPiratez is trying to load, so it doesn't load at all.. :(
-
Doesn't happen to me. Can someone confirm?
-
Doesn't happen to me. Can someone confirm?
Found it!
F9 - on quicksave reload touch buttons disappear.
-
Yes, on reload everything resets.
-
New OXCE v7.1 is up.
2021-09-27
QoL:
- Keep original target if attacked by a HK (and didn't disengage manually)
- Interceptor/Escort Wing Feature (by Buscher)
Features:
- Enable mouse wheel scrolling for Ufopaedia novels (by SupSuper)
- Add basic support for AI kneeling and running
- Improved performance on vapor creation
- Breaking change: Improved modding support for vapor colors (to be able to create submods)
- Improved handling of high opacity of vapor - now you can have darker versions too
- `oxceModValidationLevel` user setting (can turn off some ruleset checks for old mods)
Modding:
- Breaking change: handling of default damage range (+added 2 new `RandomType` values; changed the default value from 0 to 8 )
- `alwaysVisible` in armor ruleset + basic script support (`isVisible`, `makeVisible`)
- Live alien (for Geoscape) can now be different than the Battlescape unit type (`liveAlien` in unit ruleset)
- Support for `reloadSound` from ammo item
Scripting:
- Exposed breath animation frames to scripts
- Exposed unit getFire/setFire to scripts
- Exposed unit conversion to scripts
Bugfixes OXCE:
- Fixed bug when destroying workshop-like facilities
- Fixed pathfinding of 2x2 units in fire (to be backpatched into OXC)
- Fixed bug that allowed avoiding AI reaction shots
- Craft returning after mission don't join dogfights
- Fixed instant mission despawn
- Fixed TFTD touch buttons graphics
Bugfixes OXC:
- Don't allow negative time units/energy
- Fixed patrol nodes not being freed when units die
- Fixed Korean wordwrapping
- Fix language settings getting mixed up between files
- Fix intro crashing when no audio device is available
- Don't reset mods when pressing Restore Defaults
- Fix starting day for TFTD
- Fix statistics calculation for commendations
- Don't corrupt saves on debriefing ragequit
- Fixed Snakeman and Silacoid movement type
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator was updated.
Wiki ruleset reference will be updated soon-ish.
Auto-update (Windows only) will be turned on after 2-3 weeks if no critical bugs are found.
-
Breaking change (as requested): Overriding 'ResistType' should NOT override 'RandomType' automatically anymore.
Example in OXCE 7.0:
- type: STR_HADRIEX_GUN_CHARGE
damageType: 9
damageAlter:
ResistType: 12
The unspecified `RandomType` was determined from `ResistType` (in this case from 12, which would translate into `standard damage`)
Same example in OXCE 7.1:
- type: STR_HADRIEX_GUN_CHARGE
damageType: 9
damageAlter:
ResistType: 12
--
The unspecified `RandomType` is NOT determined from `ResistType` anymore, it is determined from `damageType` as in vanilla (in this case from 9, which would translate into `no damage`)
Recommended solution is to specify the `RandomType` explicitly where required, e.g. in this case it would be:
- type: STR_HADRIEX_GUN_CHARGE
damageType: 9
damageAlter:
ResistType: 12
RandomType: 8
-
Hello.
Was fixed an error with "STR_ALIEN_COLONY_" instead of colony name?
Thanks.
-
Hello.
Was fixed an error with "STR_ALIEN_COLONY_" instead of colony name?
Thanks.
It's not a bug.
Some objects get that extra "_" in the translation string intentionally.
Not nice, but that's what has been done in OpenXcom many years ago and we're stuck with it now.
https://github.com/OpenXcom/OpenXcom/blob/master/src/Savegame/Target.cpp#L201
-
Oh. That's odd. But now i find these strings in vanilla language files, so I apologize. My mistake.
-
Not sure if this is a bug but it didn't happen before.
When moving units or firing weapons, the bottom UI blanks out.
Using 7.1, Happens in both X-COM Files, and Vanilla game.
-
Not sure if this is a bug but it didn't happen before.
When moving units or firing weapons, the bottom UI blanks out.
Using 7.1, Happens in both X-COM Files, and Vanilla game.
It happened before for firing weapons (e.g. during autoshots).
It didn't happen when moving units, that's a bug.
Fixed here: https://github.com/MeridianOXC/OpenXcom/commit/18a9c23b55310f8f6445954ef308ddffac12aa89
You can wait for next version or download a snapshot here: https://lxnt.wtf/oxem/builds//Extended/Extended-7.1.1-8be08dd42-2021-09-29-win64.7z
-
Another thing fixed in 7.1.1 is crash when unit with reaction 0 react to attack.
As consequence of this fix y-script hooks for reactions have new argument `reaction_count` where is stored sequence number of current reaction to same event.
-
TRANSFER screen shortcut request:
Right after finishing a mission I can ship the looted equipment to my research base. Can we please have a shortcut key "X" on that screen that transfers all equipment from the left side to the right side, so everything can be shipped to an other base (not where my ship is from) at a flip of a switch?
Thank You!
-
Another thing fixed in 7.1.1 is crash when unit with reaction 0 react to attack.
As consequence of this fix y-script hooks for reactions have new argument `reaction_count` where is stored sequence number of current reaction to same event.
How is it possible?
-
when "action unit" have too zero reaction because of stats of depletion of TU
-
In recent version of OXCE 7.1.2 changed logic that now unit can access psi, skill and special item buttons at once, previously only one buttons was visible.
-
I'm sorry, but I'm staying on version 7.0. I'm tired of error messages that were not considered errors before. In addition, this update does not carry any useful functions for my modification. Bug fixes that I've never encountered are also of dubious utility.
I wish you a successful removal of restrictions in the future and not to ruin what works.
-
I'm sorry, but I'm staying on version 7.0. I'm tired of error messages that were not considered errors before. In addition, this update does not carry any useful functions for my modification. Bug fixes that I've never encountered are also of dubious utility.
I wish you a successful removal of restrictions in the future and not to ruin what works.
Just for the record, all those things were considered errors before, and were causing issues and crashes.
We will definitely not remove any validations (unless proven we made a mistake somewhere -- we're only humans too); the number of validations will only grow and grow to ensure we provide the best quality possible.
-
Encountered possible bug.
When attacking by psi-amp "use", script hook "damageUnit" must know damage type from psi-amp. But both "damaging_type" parameter and "RuleDamageType.getResistType" from "weapon_item" always returns 0.
Or is it work some other way?
-
Do you correctly set it in psi-amp? Stats for nerd should show what damage type is set for this item.
Rest of code should handle damage types same as any other item in game.
-
- type: STR_MENTAL_WEAPON_2 #Mentat master panic
categories: [STR_SPELLS_WEAPONS, STR_PSI, STR_MENTAL_DAMAGE]
maxRange: 25
hitSound: 36
psiAnimation: 40
hitAnimation: 176
battleType: 9
LOSRequired: false
power: 1
manaRequired: true
manaExperience: 150
experienceTrainingMode: 26
accuracyPanic: 30 #bonus equal to Vanilla x2
accuracyUse: 20
accuracyMultiplier:
firing: 0.0
psiSkill: 1.0
damagetype: 13
damageBonus:
psiStrength: 0.5
damageAlter:
RandomType: 3
ArmorEffectiveness: 0
ToWound: 0
ToArmor: 0
costUse:
time: 0
mana: 0
tuPanic: 0
tuMindControl: 0
tuUse: 0
flatRate: true
clipSize: -1
fixedWeapon: true
specialUseEmptyHand: false
recover: false
# specialIconSprite: 6
targetMatrix: 7
Maybe a thing is that attack can be done via skill?
- type: STR_MIND_BLAST_SKILL #mentat master, deal damage.
tags:
SKILL_ID: 12
costUse:
time: 25
mana: 25
flatUse:
mana: true
targetMode: 11
compatibleWeapons: [STR_MENTAL_WEAPON_2]
checkHandsOnly: false
It does nothing scripted though.
-
damagetype: 13
this is incorrect, `T` should be upper case.
-
damagetype: 13
this is incorrect, `T` should be upper case.
Oh. Shame on me.
-
This is why I ask you to check SfN as it can detect errors like this
-
I would like to request a shortcut to transfer everything from the left to the right (at once on keypress "X") on the Transfer screen, please:
(https://i.ibb.co/Mg1Y0zt/screen029.png)
(http://)
-
New OXCE v7.1.3 is up.
2021-10-17
Modding:
- It is now possible to show multiple special buttons at once (psi, special, soldier skill)
Scripting:
- Added reaction count limit (+exposed the counter to scripts)
Bugfixes:
- Fixed missing death and bleedout notifications for unconscious units (to be backpatched into OXC)
- Fixed loot window not displaying any items after a base defense
- Cannot disengage when you and the HK have the same speed anymore
- Fixed issue when unit has Reaction score=0
- Fixed display of unit stats during walking/firing (to be backpatched into OXC)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
New OXCE v7.1.3 is up.
Thank you very much !! :)
-
Small question:
When we use "FixRadius: 1" for super-powerful weapon, the explosion animation still showed over whole screen, not just normal blast. Is it intended?
-
Hard to say its is intended but game behave this way, animation is independent in most case from real explosion calculation.
Even more if range is bigger it still show animation on places where explosion even do not touch.
-
Modding:
- It is now possible to show multiple special buttons at once (psi, special, soldier skill)
And how to make them NOT showing? I got unnecessary "psi" button showed for all my units with psi-abilities.
Thanks.
-
And how to make them NOT showing? I got unnecessary "psi" button showed for all my units with psi-abilities.
Thanks.
That's a bug, being fixed right now...
-
I plan release bug fix for this today
-
New OXCE v7.1.4 is up.
2021-10-24
Modding:
- Ability to change armor values via Soldier Bonuses: https://openxcom.org/forum/index.php/topic,7405.msg141860.html#msg141860
- Arc/Mission/Event-script triggers by xcom base country: https://openxcom.org/forum/index.php/topic,7215.msg141846.html#msg141846
- Arc/Mission/Event-script triggers by xcom base region
Other:
- Added Ukrainian translation
Bugfixes:
- Fixed duplicated psi weapon button
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
- Ability to change armor values via Soldier Bonuses: https://openxcom.org/forum/index.php/topic,7405.msg141860.html#msg141860
Well, for the sake of such a bonus, I switch to the new version without question. :)
One request:
- Craft returning after mission don't join dogfights
Please do this by disabling/enabling the function.
Thanks for the updates.
-
It’s very interesting who translates into Ukrainian?
-
It’s very interesting who translates into Ukrainian?
Somebody called Andriy Rutar.
You can see all details on Transifex: https://www.transifex.com/openxcom/openxcom-extended/language/uk/
-
Can somebody help me? I am currently running into issues while trying to implement an additional base facility which has a map with a custom tileset (in addition to the vanilla tilesets).
I take it I have to modify the whole base defense terrain (XBASE) to include the custom tileset? Or is it possible to include/add custom tilsets on a map block basis and/or add facilities as stand-alone maps?
Thanks in advance.
-
There is a bug (well, I consider it a bug) with the craft equipment templates. If you save a template while the equipment list is being filtered via Q quicksearch, it only saves the equipment that's filtered (and on the craft). It should save all equipment that's assigned to the craft regardless of the filter.
-
There is a bug (well, I consider it a bug) with the craft equipment templates. If you save a template while the equipment list is being filtered via Q quicksearch, it only saves the equipment that's filtered (and on the craft). It should save all equipment that's assigned to the craft regardless of the filter.
It's a useful feature, this way you can choose whether to save everything or just the filtered stuff.
See also my comment that it is intended: https://github.com/MeridianOXC/OpenXcom/blob/oxce-plus/src/Basescape/CraftEquipmentState.cpp#L879
-
Center on Enemy X red rectangle doesn't remain red after switching to new unit in
Extended-7.1.7-19e41cbc3-2021-11-25-win64.7z
Is it the variable
oxceEnableSlackingIndicator: true
or probably caused by this:
oxceRecommendedOptionsWereSet: true
Is there an INI variable that can switch this function back as it was originally?
-
Center on Enemy X red rectangle doesn't remain red after switching to new unit in
because the new unit doesn't see enemy X... so no red rectangle
Is there an INI variable that can switch this function back as it was originally?
it works as it worked originally, since 2015, in OXCE
(in OG and OXC, the red rectangle just disappears... as they don't have any green rectangles)
-
It's a useful feature, this way you can choose whether to save everything or just the filtered stuff.
Ah, okay, got it. I never want to do this, but that's okay. I just need to be careful to always turn the filter off first.
-
I would like to request a shortcut to transfer everything from the left to the right (at once on keypress "X") on the Transfer screen, please:
(https://i.ibb.co/Mg1Y0zt/screen029.png)
(http://)
done
-
New OXCE v7.2 is up.
2021-12-24
QoL:
- CTRL-click to assign soldiers in Craft Armor GUI: https://openxcom.org/forum/index.php/topic,10237.0.html
- Sorting in Sell and Transfer GUIs (by size and value): https://openxcom.org/forum/index.php/topic,5821.msg142113.html#msg142113
- Preserve armor of soldiers undergoing transformation: https://openxcom.org/forum/index.php/topic,10159.0.html
- Allow renaming soldiers during transformation: https://openxcom.org/forum/index.php/topic,10214.0.html
- Transfer All hotkey (items only): https://openxcom.org/forum/index.php/topic,6586.msg142652.html#msg142652
- Highlight current music track: https://openxcom.org/forum/index.php/topic,10272.0.html
- TTV: cost per unit, engineer hours, work space required
- TTV: required by transformations: https://openxcom.org/forum/index.php/topic,10011.0.html
Features:
- Support for non-ASCII characters in StatStrings: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#StatStrings
- Added "Prison Cleanup" button
Modding:
- More aggro sounds (`aggroSound` can now also be a list of sounds)
- Add option to delete areas in regions (`deleteOldAreas`)
- Allow reinforcements before battle start (turn 0 allowed)
- Commendations for victories in special missions: https://openxcom.org/forum/index.php/topic,10190.msg142628.html#msg142628
- Support `spawnedItem` and `spawnedEvent` also for research from getOneFree
- Added `spawnedItemCount` to research ruleset
- Added `spawnedItemList` to research ruleset
- Added `missionBountyItemCount` to deployment ruleset
- Ability to show an alien base immediately after spawn (`showAlienBase`)
- Negative recoveryDividers work as multipliers: https://openxcom.org/forum/index.php/topic,6616.msg142693.html#msg142693
- Disable psi-training for soldiers with trainingStatCaps.psiSkill <= 0: https://openxcom.org/forum/index.php/topic,10208.msg142696.html#msg142696
- Option to align text to bottom in pedia article type 7: https://openxcom.org/forum/index.php/topic,9688.0.html
- Ability to reset alien base age during upgrade: https://openxcom.org/forum/index.php/topic,6430.msg142855.html#msg142855
Scripting:
- Added script names
- Added option to delete and override scripts in submods (by name)
- Many small API additions
Bugfixes:
- Don't spawn non-flying reinforcements on water tiles
- Don't save armor of non-soldier units in equipment templates
- Fix display of aliens "being studied" in the Alien Containment GUI
- Fix double-counting of interrogated aliens
- Fixed quick search in the Memorial
- from OXC: fix ground zero tile calculation
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator was updated.
Wiki ruleset reference was updated.
-
New OXCE v7.3 is up.
2021-12-29
QoL:
- Help purchasing missing items when re-equipping a craft
- Hotkey 'Z' to add all soldiers to training and psi-training
- Added status DONE into the Psi Training GUI
- TTV item buy cost (by EttyKitty)
- Quick search in the Soldier Armor GUI
Features:
- Allowed force-landing a HK using a tractor beam
- Display special weapon bigob in the empty hand UI (still requires `specialUseEmptyHand: true`) EDIT: will be changed in 7.3.1+ and require a new flag `specialUseEmptyHandShow: true`
+ Allowed player access to the built-in melee attack for Lobstermen in TFTD
- Save conversion/compatibility: Interrupt alien missions with invalid regions (and re-assign them to STR_NORTH_AMERICA, or whatever the first region is)
- Save conversion/compatibility: Remove invalid regions from alien strategy
- Load each mod only once! Duplicate zip files or directories will be ignored and reported in the log file
Modding:
- More support for non-point mission site areas: https://openxcom.org/forum/index.php/topic,10305.0.html
- Event script can access mission script tracking variable: https://openxcom.org/forum/index.php/topic,7215.msg142856.html#msg142856
- Ability to reset alien base age, part 2: https://openxcom.org/forum/index.php/topic,6430.msg142855.html#msg142855
Scripting:
Bugfixes:
- Fixed a lighting glitch
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator was updated.
Wiki ruleset reference was updated.
-
This is a real New Year's present! Thank you so much for your efforts. I wish you success and inspiration in the New Year!
-
New OXCE v7.4 is up.
2022-01-10
QoL:
n/a
Features:
- Support for animated alien inventory (M-click view)
- Handle side effects for research from events (e.g. remove obsolete ongoing research projects)
- 2x2 soldiers are now displayed under "soldiers/crew" label, not under "hwps/vehicles" label
- Added validation of sound and surface set indices
- Save options snapshot for debug
Modding:
- Research on mission failure and mission site despawn: https://openxcom.org/forum/index.php/topic,10302.0.html
- More events (success, failure, site despawn): https://openxcom.org/forum/index.php/topic,10319.0.html
- Arc/Mission/Event script access to object counters: https://openxcom.org/forum/index.php/topic,10318.0.html
- Custom mission counters: https://openxcom.org/forum/index.php/topic,10318.0.html
- Separate power value just for explosion animation: https://openxcom.org/forum/index.php/topic,10308.0.html
- Check for valid land point for site spawns by UFO: https://openxcom.org/forum/index.php/topic,10305.0.html
- More granular enemy numbers per difficulty (`medQty`): https://openxcom.org/forum/index.php/topic,10304.0.html
- Limits on craft crew by type and size: https://openxcom.org/forum/index.php/topic,10317.0.html
- Custom "select base" and "start dogfight" sounds: https://openxcom.org/forum/index.php/topic,10195.0.html
- Custom craft sounds + interface sounds rework: https://openxcom.org/forum/index.php/topic,10195.0.html
- Prime/unprime sounds: https://openxcom.org/forum/index.php/topic,9663.0.html
- Support vertical text alignment for cutscenes: https://openxcom.org/forum/index.php/topic,9688.msg142868.html#msg142868
- Support for random terrain/deployment map scripts (attribute `mapScripts`)
- Display special weapon bigob in the empty hand UI (requires `specialUseEmptyHandShow: true`)
- Explosion on collapse/tile burning also for soldiers (defined by armor, attribute `specab`)
- Hunter-killer softlock threshold (attribute `softlockThreshold`)
- Multi-UFO retaliation base attacks (attribute `multiUfoRetaliation`)
Bugfixes:
- Fixed armor mismatch of dead soldiers after reload (introduced in OXCE v7.1.11, upgrade recommended)
- Fixed following UFO converted into a mission site with crafts that contain only HWPs
- Fixed available living quarters check before craft transfer (was ignoring 2x2 soldiers)
- Fixed missing access to the Inventory button (at the base) when craft has only 2x2 soldiers
- Fixed missing craft capacity check when changing armor with R-click
- Improved craft capacity checks in New Battle GUI
- Fixed prison check after reload
- Don't show reinforcements alert before turn 1
- Fixed rare endless loop in walking state (to be fixed in OXC too)
- Android: Fixed lingering path preview bug
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Auto-update available on Windows.
Ruleset validator was updated.
Wiki ruleset reference was updated.
-
Well, here it is again ... only everything was fine, and suddenly everyone died. The worst thing is that looking at this LOG I can not understand what exactly to edit. There are no such values in my modification.
-
Well, here it is again ... only everything was fine, and suddenly everyone died. The worst thing is that looking at this LOG I can not understand what exactly to edit. There are no such values in my modification.
The indexes in the log are the internal ones from the game.
In the ruleset, they will be smaller by 1000 (or whatever mod offset is at the time).
I'll check later today too.
-
Wrong bigsprite:
items:
- type: STR_CORPSE_PLASTIC_ARMOR
bigSprite: 0 # before was 9343
Wrong handsprite:
items:
- type: CALCINITE_WEAPON #melee attack
handSprite: 0 # before was 9104
Wrong unit response sounds (449):
armors:
- type: HOVERTANK_AQWA_ARMOR_GAUSS_A_UC
# selectUnitFemale: [446, 447, 448, 449, 450, 451, 452, 453, 454, 455, 456] # 449 doesn't exist
- type: HOVERTANK_AQWA_ARMOR_SONIC_A_UC
# selectUnitFemale: [446, 447, 448, 449, 450, 451, 452, 453, 454, 455, 456] # 449 missing
- type: HOVERTANK_AQWA_ARMOR_ROCKET_A_UC
# selectUnitFemale: [446, 447, 448, 449, 450, 451, 452, 453, 454, 455, 456] # 449 missing
and many potentially wrong `hitAnimation`s... I didn't check all... maybe there are some false positives there, I need to check with Yankes about this particular check
I tried removing all hitAnimations and after that the game started.
(As a workaround, you can enable "Lazy Loading" in options and the sprites won't be validated)
-
Yeah, the hitAnimation validation seems wrong.
Will fix asap.
-
Thanks, I fixed my mistakes.
Yeah, the hitAnimation validation seems wrong.
Will fix asap.
We wait...
-
Problem:
If there are several transport ships at the BASE, two conflicting needs often arise:
1. Sort soldiers by parameters.
2. Establish the order of placement of soldiers in each transport and not violate this order by sorting the general list.
Solution Suggestion:
Add to soldiers list (screenshot) filters:
sort all soldiers;
sorting of soldiers assigned to transport 1;
sorting soldiers assigned to transport 2
- with the preservation (memorization) of the list (order) of the location of soldiers in each transport.
-
1/ the comboboxes would be too small
2/ it would only "solve" the issue for 2 transports, not for 3, 4 or 77
-
1. Place the list of filters in the drop down list (as already done for the other sort buttons).
2.
Base 6x6. Therefore: in principle, it is impossible to build more than 8 hangars on the base. The maximum number of lines in the list will be 9. (Including all soldiers).
-
1/ the comboboxes would be too small
Anyway, they are more than the destination line of a soldier in a transport or the destination line of an armor soldier.
-
1/ the comboboxes would be too small
P.S.
You can make the "OK" button much smaller.
-
New OXCE v7.4.2 is up.
2022-01-18
QoL:
- Indicate `maxRange` on psi and waypoint cursor types
- Hotkey for Multi-level-view (default empty)
- Hotkeys to scroll ground inventory (arrow left and arrow right keys by default)
Features:
- Melee terrain damage can target bigwall objects on the same tile: https://openxcom.org/forum/index.php/topic,8634.msg143262.html#msg143262
- More debug info on the globe (countries, mission zone areas, etc.)
- Added soldier type default armor validation
- Ability for mods to ENFORCE a minimum OXCE version (`enforcedExtendedVersion` in metadata.yml) -- will be removed in OXCE 7.6 and solved differently
Modding:
- Ability to decrease custom counters: https://openxcom.org/forum/index.php/topic,10318.msg143063.html#msg143063
- Custom shot names in the pedia: https://openxcom.org/forum/index.php/topic,9742.msg143229.html#msg143229
Scripting:
- Added new script hook `damageSpecialUnit` to process damage side effects:
* explode on death
* set on fire
* fire extinguisher
* morale loss from HP loss
- These side effects now also apply to the following special damage sources (before they didn't):
* debug mode cheats
* unit on fire damage (per turn)
* unit in smoke damage (per turn)
* OXCE enviroEffects damage (per turn)
Bugfixes:
- Fixed `hitAnimation` validation
- Fixed `bulletSprite` validation
- Prevent "unit freeze" on AI trying to pick up an inaccessible item
- Prevent rare instant mission despawn
- Preserve health and mana on armor transformation between mission stages
- Fixed M-click on a disabled facility in the Build Facilities list
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator was updated.
Wiki ruleset reference was updated.
Auto-update available on Windows.
-
To tag soldiers according to their functions and capabilities, players rename the soldiers. I propose to add the ability to mark soldiers in the list - using different font colors. (Assigning a color is similar to the "wear armor" function).
Since the game already marks (in font color) the soldiers added to the vehicle, I suggest marking only the Name of the soldiers.
-
To tag soldiers according to their functions and capabilities, players rename the soldiers. I propose to add the ability to mark soldiers in the list - using different font colors. (Assigning a color is similar to the "wear armor" function).
Since the game already marks (in font color) the soldiers added to the vehicle, I suggest marking only the Name of the soldiers.
There are only 5 font colors in UFO (3 already used) and only 3 font colors in TFTD (all 3 used).
-
You can add the ability to land transport ships (for repair and refueling with conventional fuel) in cities. The city in this case turns into a "temporary base" (with the ability to buy something or hire a rare one). As soon as the ship leaves the city, the "temporary base" disappears.
P.S. The city may have its own development options. The base city is opened on the globe (not in the list of the player's Bases). UFO can destroy some buildings in cities.
-
Thanks for the update. In win32 and win64, only "All countries not found in ru" confuses. Just was in stock, and suddenly "not found". And I did not find the untranslated lines themselves in the game. %)
-
Thanks for the update. In win32 and win64, only "All countries not found in ru" confuses. Just was in stock, and suddenly "not found". And I did not find the untranslated lines themselves in the game. %)
Ah, I missed that.
It's just a hardcoded string for debug mode, doesn't need translation.
I'll make sure it doesn't appear in the log file in the next version.
-
Ah, I missed that.
It's just a hardcoded string for debug mode, doesn't need translation.
I'll make sure it doesn't appear in the log file in the next version.
Yes, also check the weapon slots on the ships.
[19-01-2022_15-29-16] [WARN] {0} not found in ru
[19-01-2022_15-29-16] [WARN] {4} not found in ru
Thanks again for the update.
-
Yes, also check the weapon slots on the ships.
[19-01-2022_15-29-16] [WARN] {0} not found in ru
[19-01-2022_15-29-16] [WARN] {4} not found in ru
Where do I need to click for this to happen?
-
This happens when you set different weaponTypes for craft weapon slots.
crafts:
- type: STR_INTERCEPTOR
weaponTypes:
- [0,1]
- 2
Start the test mod, go into the ufopaedia, select the interceptor page. Might require clicking the info button for stats for nerds. Then look into the openxcom.log.
[19-01-2022_18-32-38] [WARN] {0,1,0} not found in en-US
[19-01-2022_18-32-38] [WARN] {2} not found in en-US
[19-01-2022_18-32-38] [WARN] {0} not found in en-US
-
This happens when you set different weaponTypes for craft weapon slots.
Thank you, comrade, because my English is limping on all limbs.
And there is.
-
New OXCE v7.4.4 is up.
2022-01-21
QoL:
- Increased maximum for Options::changeValueByMouseWheel https://openxcom.org/forum/index.php/topic,10311.msg143438.html#msg143438
- Hotkeys to close event popups (Esc/Enter): https://openxcom.org/forum/index.php/topic,10321.0.html
Modding:
- Simplified `craftInventoryTile` override by submods (can be used also without `battlescapeTerrainData`)
- Ability to change alien race on alien base upgrade: https://openxcom.org/forum/index.php/topic,6430.msg143440.html#msg143440
- Supply and hunt missions can specify alien race explicitly: https://openxcom.org/forum/index.php/topic,5717.msg143441.html#msg143441
Bugfixes:
- Translation fix (weaponTypes in Stats for Nerds)
- Translation fix (All countries in geoscape debug mode)
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator was updated.
Wiki ruleset reference was updated.
Auto-update available on Windows.
-
Thanks for 7.4.4 !
I went from version 7.3 to version 7.4.4!
But now I have a problem with an old Mod that was working properly until now!
And I don't understand! ???
OXCE/UFO:
[21-01-2022_18-16-23] [ERROR] During linking rulesets of items:
Error for 'STR_FIRE_EXT': Wrong index 1076 for sound set BATTLE.CAT
Ruleset
items:
- type: STR_FIRE_EXT
size: 0.2
costBuy: 700
costSell: 420
weight: 9
bigSprite: 587
floorSprite: 262
handSprite: 256
bulletSprite: 1
fireSound: 77
explosionHitSound: 76
hitAnimation: 96
...
********************************
OXCE/TFTD:
[ERROR] During linking rulesets of items:
Error for 'STR_ALLOY_KNIFE': Wrong index 1086 for sound set BATTLE.CAT
Error for 'STR_KNIFE': Wrong index 1086 for sound set BATTLE.CAT
Ruleset
items:
- type: STR_KNIFE
size: 0.1
costBuy: 100
costSell: 90
weight: 1
bigSprite: 129
floorSprite: 130
handSprite: 802
meleeSound: 86
meleeAnimation: 108
...
- type: STR_ALLOY_KNIFE
size: 0.1
costSell: 1300
weight: 1
bigSprite: 324
floorSprite: 324
handSprite: 804
meleeSound: 86
meleeAnimation: 108
...
In both cases, the "extraSounds.rul" file does not refer to these indexes (76 or 1076 - 86 or 1086).
-
Thanks for 7.4.4 !
I went from version 7.3 to version 7.4.4!
But now I have a problem with an old Mod that was working properly until now!
And I don't understand! ???
Whole point of validation is change random bug that crash game during play or make game misbehave to error during load.
This is critical for modders as only starting game will show most error in items, this is opposite to playing game for 1h to see if all items were defined correctly.
If you can't fix bug in mod you can reduce validation and risk that game will crash during play.
In 7.4.4 game check many sound and surfaces if they really exist in game.
-
I didn't understand anything but thanks for answering! :)
It's ok because I just found a solution!
All these problems come from the fact that the "modded" objects listed use "stock" sounds in the base game!
So I added sounds I found in various Mods and modified the rul files concerned.
And for TFTD I also put "meleeHitSound" instead of "meleeSound"!
-
In both cases, the "extraSounds.rul" file does not refer to these indexes (76 or 1076 - 86 or 1086).
That's the issue.
The mods are using sound indexes, which don't exist.
Either the numbers are wrong (typos), or the extraSounds.rul definitions were forgotten, or deleted.
Or in different words, the game is telling you "Sounds not found."
-
Thanks for the update. There is only one oddity:
[21-01-2022_18-54-25] [INFO] Supressed Error for 'STR_BIODRONE_TERRORIST': This unit has a corresponding item to recover, but still isn't recoverable. Reason: (the unit is marked with 'capturable: false'). Consider marking the unit with 'liveAlien: ""'.
I don’t understand what this could be and whether it should be corrected, since BIODRONE, like all robots, is immune to any form of telepathy and stunning, that is, it is impossible to capture it.
-
Thanks for the update. There is only one oddity:
[21-01-2022_18-54-25] [INFO] Supressed Error for 'STR_BIODRONE_TERRORIST': This unit has a corresponding item to recover, but still isn't recoverable. Reason: (the unit is marked with 'capturable: false'). Consider marking the unit with 'liveAlien: ""'.
I don’t understand what this could be and whether it should be corrected, since BIODRONE, like all robots, is immune to any form of telepathy and stunning, that is, it is impossible to capture it.
Problem is there contradiction, there is `liveAlien:` (default value) but you can't recover it because of `capturable: false`, if your goal is to make this unit impossible to capture then its mean that you need add `liveAlien: ""` to mark that is no way to recover this unit and `capturable: false` is not error.
-
Oh man...
- Hotkeys to close event popups (Esc/Enter): https://openxcom.org/forum/index.php/topic,10321.0.html
I made the above suggestion, but the responses suggested that not only had it been considered in the past and dismissed already, but even the idea of implementing it was probably more effort than it was worth, and I got ashamed for thinking I was making an unreasonable request... so I ended up deleting the thread. :)
-
Yankes, Meridian Thanks for the help, I figured it out and corrected. The error message no longer appears.
-
I don’t understand what this could be and whether it should be corrected, since BIODRONE, like all robots, is immune to any form of telepathy and stunning, that is, it is impossible to capture it.
OK, this will be a long post, but I want to answer all potential questions.
Question 1: why did we add this validation?
We added the validation, because issues/crashes with live unit recovery were constantly reported by players and were hard to identify, both for modders and for developers.
The validation should help identify potential typos, mistakes and oversights.
Question 2: do I need to fix these validation errors? Will the game still start if I don't?
OXCE will still start, potential errors will be reported only in the log file.
If we could clearly identify the intention of the modder, we would create a blocking validation, this is however not possible in this case.
It's the modder who needs to check it and decide how to fix it... because there are multiple different solutions.
Question 3: what does this validation even do?
The validation checks whether the attributes related to live unit recovery are configured consistently.
To simplify the explanation: there are 2 competing attributes:
1. attributes saying if the unit can be recovered alive or not
2. attribute saying what should be recovered, in case a recovery is attempted
There are 4 combinations:
Case A (YES-YES): attributes say that a live unit is recoverable, and a recovery item is defined.
- this is the normal scenario, everything is fine, and there is nothing written in the log
Case B (NO-NO): attributes say that a live unit is not recoverable, and a recovery item is not defined.
- this is also a normal scenario, everything is fine, and there is nothing written in the log
Case C (YES-NO): attributes say that a live unit is recoverable, but a recovery item is not defined.
- this is wrong and the game will 100% crash, if it tries to recover such a live unit
- it is of course possible that the modder made sure that a unit cannot be recovered by some other means... for example by not using the unit at all, or by using it only as a civilian faction... but we can't know that and it's safer to define the attributes consistently also in these cases
- the validation will identify such cases and will report a message in the log file saying something like this:
[21-01-2022_09-12-36] [INFO] Supressed Error for 'CIVILIAN_CASTAWAY_GAL': This unit can be recovered (in theory), but there is no corresponding item to recover.
The proper fix is to either make the live unit not recoverable (i.e. convert it into case B) or define the recovery item (i.e. convert it into case A).
Case D (NO-YES): attributes say that a live unit is not recoverable, but a recovery item is defined.
- this will not crash the game (at the moment), but it may crash the game in the future (when more features are added for example)
- the problem is again the consistency and the inability of the developers to know if the modder wanted this live unit to be recoverable or not (we still can't read minds :) )
- the validation will identify such cases and will report a message in the log file saying something like this:
[21-01-2022_09-12-36] [INFO] Supressed Error for 'STR_LOST_SOUL_MALE': This unit has a corresponding item to recover, but still isn't recoverable. Reason: (the first 'corpseBattle' item of the unit's armor is marked with 'recover: false'). Consider marking the unit with 'liveAlien: ""'.
or this:
[21-01-2022_09-12-36] [INFO] Supressed Error for 'STR_FIELD_GUN_TERRORIST': This unit has a corresponding item to recover, but still isn't recoverable. Reason: (the unit is marked with 'capturable: false'). Consider marking the unit with 'liveAlien: ""'.
The proper fix is to either make the live unit recoverable (i.e. convert it into case A) or un-define the recovery item (i.e. convert it into case B).
In most cases, conversion to case B is what needs to be done, the message even suggests it by saying "Consider marking the unit with 'liveAlien: ""'."; but it is possible that converting to case A is also what the original intention was.
Again, only the modder can say for sure.
Question 4: what are the attributes that say whether a live unit is recoverable or not?
There are 2 main attributes, that are considered during the validation:
#1. the `recover` flag on the item that is used in `corpseBattle` attribute on the unit's armor
Example for a Sectoid (1x1 unit):
armors:
- type: SECTOID_ARMOR0
corpseBattle:
- STR_SECTOID_CORPSE # <----- this item is checked
items:
- type: STR_SECTOID_CORPSE
battleType: 11
recover: true # <----- this flag is checked
recoveryPoints: 5
Example for a Reaper (2x2 unit):
armors:
- type: REAPER_ARMOR
corpseBattle:
- REAPER_CORPSE_1 # <----- this item is checked
- REAPER_CORPSE_2 # <----- NOT relevant
- REAPER_CORPSE_3 # <----- NOT relevant
- REAPER_CORPSE_4 # <----- NOT relevant
corpseGeo: STR_REAPER_CORPSE # <----- NOT relevant
items:
- type: REAPER_CORPSE_1
battleType: 11
recover: true # <----- this flag is checked
recoveryPoints: 3
We recommend using this method when converting from case C/D to case A/B.
#2. the 'capturable' flag on the unit
An example of this could be a vanilla Cyberdisc, which is not capturable.
Not capturable unit are automatically also not recoverable as live aliens.
We do not recommend using this flag to convert from case C/D into case A/B, because it has also side effects: when such unit is stunned, it is automatically insta-killed.
We recommend using option #1.
Question 5: is this check final or will it change in the future?
The check covers a lot of cases now, but not 100% of cases.
There are still corner cases that are not fully covered; for example logic around zombie-like units, just to name one.
We may improve this check in the future if we see there are still issues in the mods; or if we add new OXCE features.
Thank you for your attention, and if you made it this far, congratulations!
-
Thanks for the clarification and congratulations. :D
I have another question: where did "bigSprite" for items with "specialUseEmptyHand" go?
-
Thanks for the clarification and congratulations. :D
I have another question: where did "bigSprite" for items with "specialUseEmptyHand" go?
Modders didn't like it, so it now also needs `specialUseEmptyHandShow: true`
-
Modders didn't like it, so it now also needs `specialUseEmptyHandShow: true`
Understand, thanks. I just didn't see it in the description.
-
When drawing maps, the size of 10x10 (10x20) is often small, and the size of 20x20, although suitable, takes up 1/3-1/2 of the area from the total block of the 6x6 map. (Screenshot)
I assume that there were similar requests, but I did not find them anywhere.
Request: Create the possibility of using a SET of large terrain blocks (20x20) to compile from such blocks a general map with a size of 6x6 blocks.
(The game currently supports using a set of 10x10 terrain blocks to create an overall 6x6 block map from those blocks).
-
Request: Create the possibility of using a SET of large terrain blocks (20x20) to compile from such blocks a general map with a size of 6x6 blocks.
already doable with the standard map script features
-
Can 2x2 tanks crush 1x1 infantry???
-
Can 2x2 tanks crush 1x1 infantry???
Only if the tank falls on them and they cannot step aside.
-
Meridian, I would like to return to the issue of the counter of stunned enemies. Now when "soldierDiaries: false" the stats button disappears and space is made for the stun counter.
-
Meridian, I would like to return to the issue of the counter of stunned enemies. Now when "soldierDiaries: false" the stats button disappears and space is made for the stun counter.
added
there is not enough space, but I leave that problem to you
-
New OXCE v7.5.3 is up.
2022-02-07
QoL:
- Crafts in the TTV (by EttyKitty)
- Track/show soldier stuns when soldier diaries are disabled: https://openxcom.org/forum/index.php/topic,6586.msg143763.html#msg143763
Features:
- Added validation of layered armor definitions (only active when lazy loading is off; for modders use) added in OXCE v7.4.9, removed in OXCE v7.5.2, will be added later
- Craft deployment preview (from Craft Soldiers GUI): https://openxcom.org/forum/index.php/topic,10370.0.html
- Craft deployment preview - players can save a custom xcom deployment for real craft with real units
- Craft deployment preview - modders can define allowed start tiles per craft type: https://openxcom.org/forum/index.php/topic,10370.msg144057.html#msg144057
- Craft deployment preview - modders can define custom preview maps per craft type: https://openxcom.org/forum/index.php/topic,10370.msg144056.html#msg144056
- Base facilities preview (left-click on an Access Lift): https://openxcom.org/forum/index.php/topic,10372.0.html
- Craft-type deployment table in-game modding (from Stats for Nerds GUI) - for players: https://openxcom.org/forum/index.php/topic,10371.0.html
Modding:
- Armor transformation for HWPs and summoned units: https://openxcom.org/forum/index.php/topic,4444.msg143797.html#msg143797
- Cosmetic units, attribute `cosmetic`: https://openxcom.org/forum/index.php/topic,10352.0.html
- Units ignored by the AI, attribute `ignoredByAI`: https://openxcom.org/forum/index.php/topic,10353.0.html
- Overrides for difficulty coefficient effects, `difficultyCoefficientOverrides`: https://openxcom.org/forum/index.php/topic,10354.0.html
Bugfixes:
- Armor transformation size checks (cannot switch into a bigger armor size!)
- `craftInventoryTile` can now be used also on craft that don't use `deployment`, for example the Skyranger
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Ruleset validator was updated.
Wiki ruleset reference was updated.
Auto-update available on Windows.
-
How can you increase the landscape of the battlefield to 70x60
(80×60) withh the help of scripts, if the craft of the player is 20x20 (30x30)?
-
How can you increase the landscape of the battlefield to 70x60
(80×60) withh the help of scripts, if the craft of the player is 20x20 (30x30)?
You can specify battlefield width and length in the alien deployment, attributes `width` and `length`: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Alien_Deployments
-
New OXCE v7.5 is up.
2022-02-05
QoL:
- Crafts in the TTV (by EttyKitty)
- Track/show soldier stuns when soldier diaries are disabled: https://openxcom.org/forum/index.php/topic,6586.msg143763.html#msg143763
Features:
- Added validation of layered armor definitions (only active when lazy loading is off; for modders use)
- Craft deployment preview (from Craft Soldiers GUI): FIXME link
- Craft deployment preview - players can save a custom xcom deployment for real craft with real units
- Craft deployment preview - modders can define allowed start tiles per craft type: FIXME link
- Craft deployment preview - modders can define custom preview maps per craft type: FIXME link
- Base facilities preview (left-click on an Access Lift): FIXME link
- Craft-type deployment table in-game modding (from Stats for Nerds GUI) - for players: FIXME link
It seems to me that there is some mistake here. I can only control the first soldier.
-
It seems to me that there is some mistake here. I can only control the first soldier.
yeah, last minute bug... will fix soon
-
yeah, last minute bug... will fix soon
Many thanks for both the advice and the transport deployment scheme. This is what is really needed.
-
If you save the layout of the soldiers in the transport, then change the order of the soldiers in the list, and then again return to the layout of the soldiers in the transport, then the game crashes.
-
hotfix OXCE v7.5.1 uploaded
EDIT: there is a known issue with layered armors, working on it... there will be another fix version in the next days
(https://openxcom.org/forum/index.php/topic,4058.msg143831.html#msg143831)
-
Hi, any code syntax or reference to use a different custom map?
-
Hi, any code syntax or reference to use a different custom map?
yes, it will be in the FIXME links after I write them :)
for now, here's the test sample I used during development... it's for the 40k mod:
alienDeployments:
- type: STR_CRAFT_DEPLOYMENT_PREVIEW
music:
- HANGAR
briefing:
title: STR_HANGAR_TITLE
palette: 4
desc: STR_HANGAR_DESCRIPTION
music: HANGAR
showCraft: true
showTarget: false
background: BACK16.SCR
shade: 1
terrains:
- XHANGAR
script: XHANGAR
width: 30
length: 20
height: 6
or if you just meant a different deployment for a particular craft, it's the "customPreview" attribute: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Crafts
crafts:
- type: STR_AVENGER
customPreview: STR_MY_STUFF
-
Thank you!
-
For Base Facilities preview, any thoughts on expanding this into missions can be launch from the Base itself? E.g Invisible Alien Infiltration and you have to sniff them out?
-
no
-
Idea. If someone asks for more space.
-
Idea. If someone asks for more space.
Sorry, that idea has been discussed already and has been rejected.
The maximum number of bases in OXCE stays at 8.
-
Sorry, that idea has been discussed already and has been rejected.
The maximum number of bases in OXCE stays at 8.
Space in the interface can be used not only for bases, but also for other functions. If someone needs a place, now you can see where to get this place.
-
I will draw so that they understand me correctly .
-
That would leave very little room for translations on those buttons.
There are languages much more verbose than English, support for those is more important than creating interface space.
-
"Build a new base" - can be replaced with a construction icon.
New bases in the game are not built too often.
Other functions are similar.
In the tactical interface, none of the buttons have an inscription. But even without translation, everything is clear.
-
There is a ton of free space for new features without such dramatic changes.
-
Thank you very much for the update.
-
There is a ton of free space for new features without such dramatic changes.
If you take the Warhammer 40,000 universe (where each "military camp" is treated as a separate military unit), then in fact each "X-COM base" lacks the functions of managing it as a military camp. (At least at the level of the military Company)
This means that players will definitely ask for platoon, company and regimental functions for managing personnel and the facility itself..
-
If you take the Warhammer 40,000 universe (where each "military camp" is treated as a separate military unit), then in fact each "X-COM base" lacks the functions of managing it as a military camp. (At least at the level of the military Company)
This means that players will definitely ask for platoon, company and regimental functions for managing personnel and the facility itself..
But this is X-COM, not Warhammer. Base interface spacing is fine as is. Underlaying idea is to stay vanilla-compliant.
-
hotfix OXCE v7.5.2 uploaded
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
-
But this is X-COM, not Warhammer. Base interface spacing is fine as is. Underlaying idea is to stay vanilla-compliant.
If we consider X-COM as a simulator of a military organization, then the simulation of all the main functions and structures of a military organization is indispensable in the future.
-
But this is X-COM, not Warhammer. Base interface spacing is fine as is. Underlaying idea is to stay vanilla-compliant.
If someone decides to create in the game (modification) such a strategic level that is present in the game "Civilization" or "Total War", then the number of bases in the game will be equal (needed) to the number of regions on the globe. That is more than eight.
(To establish control over the region - you need to capture the base in it)
-
If someone decides to create in the game (modification) such a strategic level that is present in the game "Civilization" or "Total War", then the number of bases in the game will be equal (needed) to the number of regions on the globe. That is more than eight.
(To establish control over the region - you need to capture the base in it)
It's useless. Negotiations have been underway for several years now, but the number of bases has not increased because of this. In addition, modding capabilities allow you to have dozens of ships and combat squads on one base, so there is no formal need to increase the number of bases.
hotfix OXCE v7.5.2 uploaded
What exactly has been changed?
-
What exactly has been changed?
Layered armors optimization and validation was reverted back.
-
It's useless. Negotiations have been underway for several years now, but the number of bases has not increased because of this. In addition, modding capabilities allow you to have dozens of ships and combat squads on one base, so there is no formal need to increase the number of bases.
I guess:
As soon as there are people who are able to implement the strategic concept of Total War (economic control over the territory through military control over the "city" (Base) located on this territory), then there will be people who are able to increase the number of bases to the number of regions.
In the game "Total War" (Civilization), the player can also have a dozen armies in each city. But economic control over the new territory is achieved only through the military capture of enemy cities.
-
When press the button New Battle -
[07-02-2022_01-38-00] [FATAL] A fatal error has occurred: Segmentation fault.
[07-02-2022_01-38-00] [FATAL] 0x5cbe20 OpenXcom::CrossPlatform::stackTrace(void*)
[07-02-2022_01-38-00] [FATAL] 0x5ccca0 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[07-02-2022_01-38-00] [FATAL] 0x41c7f0 signalLogger(int)
[07-02-2022_01-38-00] [FATAL] 0x9f49b0 OpenXcom::UfopaediaStartState::think()
[07-02-2022_01-38-00] [FATAL] 0x76e872fc _C_specific_handler
[07-02-2022_01-38-00] [FATAL] 0x76e9bee0 _chkstk
[07-02-2022_01-38-00] [FATAL] 0x76e6ff00 RtlInitializeResource
[07-02-2022_01-38-00] [FATAL] 0x76e9b5f0 KiUserExceptionDispatcher
[07-02-2022_01-38-00] [FATAL] 0xd59300 std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::vector(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)
[07-02-2022_01-38-00] [FATAL] 0x78e980 OpenXcom::AlienDeployment::getTerrains[abi:cxx11]() const
[07-02-2022_01-38-00] [FATAL] 0x751990 OpenXcom::NewBattleState::cbxMissionChange(OpenXcom::Action*)
[07-02-2022_01-38-00] [FATAL] 0x752a10 OpenXcom::NewBattleState::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[07-02-2022_01-38-00] [FATAL] 0x754a70 OpenXcom::NewBattleState::NewBattleState()
[07-02-2022_01-38-00] [FATAL] 0x7490c0 OpenXcom::MainMenuState::btnNewBattleClick(OpenXcom::Action*)
[07-02-2022_01-38-00] [FATAL] 0x5e8860 OpenXcom::InteractiveSurface::handle(OpenXcom::Action*, OpenXcom::State*)
[07-02-2022_01-38-00] [FATAL] 0x6a4380 OpenXcom::State::handle(OpenXcom::Action*)
[07-02-2022_01-38-00] [FATAL] 0x5e3f50 OpenXcom::Game::run()
[07-02-2022_01-38-00] [FATAL] 0x41c950 SDL_main
[07-02-2022_01-38-00] [FATAL] 0x9f64e0 console_main
[07-02-2022_01-38-00] [FATAL] 0x9f6600 WinMain
[07-02-2022_01-38-00] [FATAL] ??
[07-02-2022_01-38-00] [FATAL] ??
[07-02-2022_01-38-00] [FATAL] 0x76d25550 BaseThreadInitThunk
[07-02-2022_01-38-00] [FATAL] 0x76e83840 RtlUserThreadStart
[07-02-2022_01-38-03] [FATAL] OpenXcom has crashed: Segmentation fault.
-
When press the button New Battle -
likely just some side effect of modding... delete `battle.cfg` file and try again pls
...or maybe even upload that battle.cfg file here so that I can check what failed and try to handle it a bit more gracefully next time
-
Excuse me, as for the layered armors, please might someone explain what this feature readded in openxcom extended 7.5.2 does/allows to do?
-
Excuse me, as for the layered armors, please might someone explain what this feature readded in openxcom extended 7.5.2 does/allows to do?
it allows modders to create many complicated paperdolls a little bit more efficient
(for players, this feature is irrelevant)
more info here: https://openxcom.org/forum/index.php/topic,6290.msg104464.html#msg104464
-
likely just some side effect of modding... delete `battle.cfg` file and try again pls
...or maybe even upload that battle.cfg file here so that I can check what failed and try to handle it a bit more gracefully next time
I deleted battle.cfg and ran the game without any mods - same result.
-
I deleted battle.cfg and ran the game without any mods - same result.
I was able to reproduce with your options.cfg and with the official build
I will release a fix today
-
Confirm this error (Fatal Error when pressing "New battle")
* error in OXCE 7.5.1 & 7.5.2; In 7.4.2 - all OK
* deleted battle.cfg - same error
* disable all mods - same error
-
hotfix OXCE v7.5.3 uploaded
Download: https://openxcom.org/forum/index.php/topic,5258.0.html
Changelog:
- 7.5.1 - fixed craft preview having only 1 soldier
- 7.5.2 - fixed crash on layered armors
- 7.5.3 - fixed crash on new battle
-
Everything is working. Thank you for the update. :)
-
Have you considered to enable discussions on your github repository? I like its realization in form of reddit-like posts with voting up and down
-
Have you considered to enable discussions on your github repository? I like its realization in form of reddit-like posts with voting up and down
For the foreseeable future, I will stick to this forum only.
My todolist is already endless, and I don't have time to watch more than one place.
-
Can't we heal units, summoned from fused item?
-
Can't we heal units, summoned from fused item?
I'm not aware of such limitation.
-
With oxce 7.5.3 I just got a ufo where the mission says "STR_ALIEN_RETALIATION_TERRO". While it appears to be an issue with the "early retaliation fix" mod said mod worked just fine on 7.1.4.
-
Are the win64 version of OXCE 7.5.3 is compatible with android version OXCE 7.5.3?
I can use save game files from win64 version in android version, and vice versa?
-
With oxce 7.5.3 I just got a ufo where the mission says "STR_ALIEN_RETALIATION_TERRO". While it appears to be an issue with the "early retaliation fix" mod said mod worked just fine on 7.1.4.
The mod (current version from openxcom.mod.io) doesn't contain any translations.
Please report to the mod author.
Are the win64 version of OXCE 7.5.3 is compatible with android version OXCE 7.5.3?
I can use save game files from win64 version in android version, and vice versa?
Yes, they are 100% compatible.
-
Thank you for providing the update.
I've just installed OXCE V7.5.3 and the 'New Battle' crash seems to be gone completely. (https://openxcom.org/forum/Themes/InsidiousV1-k/images/post/thumbup.gif)
-
Hi Meridian,
I have managed to create a build of OXCE inside Docker for my own purposes. It saves me having to install the sdl1.2 dependencies on my main Ubuntu install.
Would you mind if I published the build tools & instructions for the docker image to GitHub, and the docker image & run instructions itself to docker hub (https://hub.docker.com/) for others (probably no-one ;D) to use?
Just to be clear, of course the image would only contain the OXCE ubuntu binary build, and none of the assets (UFO/TFTD). They still need to be provided to the docker app (mounted) before it will run. Just like always.
It would make it a bit more convenient for me to run OXCE over multiple systems, and possibly for others, too.
-
I'm not aware of such limitation.
Well, I spawn units from fuse grenade item, I set its side to xcom (`spawnUnitFaction: 0`), and I can't target it with medkit...
-
Well, I spawn units from fuse grenade item, I set its side to xcom (`spawnUnitFaction: 0`), and I can't target it with medkit...
the `bleedImmune` default for summoned player units is true;
you can manually set it to false on their armor;
then it will work
bool BattleUnit::isWoundable() const
{
return !_armor->getBleedImmune(!(_type=="SOLDIER" || (Options::alienBleeding && _originalFaction != FACTION_PLAYER)));
}
-
How to implement the function: for the successful completion of tasks, the player receives a new military rank, which allows an additional number of bases (1-2-4-8) and receives additional types of troops at his disposal?
-
the `bleedImmune` default for summoned player units is true;
you can manually set it to false on their armor;
then it will work
bool BattleUnit::isWoundable() const
{
return !_armor->getBleedImmune(!(_type=="SOLDIER" || (Options::alienBleeding && _originalFaction != FACTION_PLAYER)));
}
Thank you very much!
Another question, I'm sure it's a pretty newbie one. I am not sure how it supposes to work, but it looks like enemy units ignore patrol node connections. For instance, I created several zones and I want enemy units to stay there. So i made patrol nodes disconnected, but it does not help at all. What actually node connections do?
I remember playing vanilla, and I think on many crafts high rank aliens were waiting me inside the UFO at the second floor. How should I isolate them in this case?
-
Another question, I'm sure it's a pretty newbie one. I am not sure how it supposes to work, but it looks like enemy units ignore patrol node connections. For instance, I created several zones and I want enemy units to stay there. So i made patrol nodes disconnected, but it does not help at all. What actually node connections do?
I remember playing vanilla, and I think on many crafts high rank aliens were waiting me inside the UFO at the second floor. How should I isolate them in this case?
Sorry, I don't remember how it works.
Your best bet is to ask Warboy; or trace the AI code line by line.
How to implement the function: for the successful completion of tasks, the player receives a new military rank, which allows an additional number of bases (1-2-4-8) and receives additional types of troops at his disposal?
The tasks can give unique items.
The unique items can be researched to unlock various things, for example additional types of troops.
The unique items can also be used as a material to construct a special base facility, which is needed to construct every other base facility, thus limiting number of bases.
-
I placed my instructions to 'build' and use an OXCE docker container here: https://github.com/pedroterzero/oxce-docker
If I get permission, I could publish the built images to docker hub (https://hub.docker.com/) so any interested end user can skip the 'build' stage.
I have tested this on Ubuntu 20.04, the container itself is Ubuntu 18.04. It seems to work perfectly.
If one has docker installed this allows to run OXCE with just a few commands and no extra dependencies on the machine.
-
I placed my instructions to 'build' and use an OXCE docker container here: https://github.com/pedroterzero/oxce-docker
If I get permission, I could publish the built images to docker hub (https://hub.docker.com/) so any interested end user can skip the 'build' stage.
I have tested this on Ubuntu 20.04, the container itself is Ubuntu 18.04. It seems to work perfectly.
If one has docker installed this allows to run OXCE with just a few commands and no extra dependencies on the machine.
permission given
-
permission given
Thank you! I published the image and it (and its instructions) can now be found here https://hub.docker.com/r/pedroterzero/oxce
I'll try to keep this updated with every new OXCE build, it should only take 1-2 minutes to create a new image. The most limiting factor is probably my awareness of when a new version gets published ;)
-
dear pedroterzero, thanks for your willingness! But it needs docker to be installed to run? Please could you explain? Would't be better to build an appimage (https://github.com/AppImage/AppImageKit)?
-
dear pedroterzero, thanks for your willingness! But it needs docker to be installed to run? Please could you explain? Would't be better to build an appimage (https://github.com/AppImage/AppImageKit)?
That's a good point, and I did consider this, but I work with docker daily and I've never used AppImage myself. It's [my choice of docker] kind of based on my own usage patterns ;)
-
That's a good point, and I did consider this, but I work with docker daily and I've never used AppImage myself. It's [my choice of docker] kind of based on my own usage patterns ;)
oh ok, just checked internet and it requires docker to be installed...while it is more simple to update builds on the other hand i thought appimage was kinda more immediate for the casual user/gamer because it''s an onee-click thing, but it needs every single image to be build manually... if i got right :)
-
The tasks can give unique items.
The unique items can be researched to unlock various things, for example additional types of troops.
The unique items can also be used as a material to construct a special base facility, which is needed to construct every other base facility, thus limiting number of bases.
Many thanks.
-
Meridian, pay attention to these cards. To avoid crashes from the preview in ufopedia, I advise you to enter them into the base assembly. Just for the convenience of those who like to play without modifications.
-
Meridian, pay attention to these cards. To avoid crashes from the preview in ufopedia, I advise you to enter them into the base assembly. Just for the convenience of those who like to play without modifications.
People who play without modifications, should only see the Preview button on Skyranger, Lightning and Avenger.
Firestorm and Interceptor don't show the Preview button, because they don't have any space for the crew.
I guess there are mods, which have a crew just for pilots and not for landing/battle... I'll update the Preview button to appear only if the craft maps are properly defined too.
-
People who play without modifications, should only see the Preview button on Skyranger, Lightning and Avenger.
Firestorm and Interceptor don't show the Preview button, because they don't have any space for the crew.
I guess there are mods, which have a crew just for pilots and not for landing/battle... I'll update the Preview button to appear only if the craft maps are properly defined too.
Yes, I completely forgot about my pilots. Just in case, it is worth making an option to turn off the preview. Binding to "allowLanding" is not necessary. Let modmakers have access to both options for solving the problem.
-
I'd say "allowLanding: false" is a direct instruction, that this craft has nothing about battlescape, thus no need to have a preview.
-
I'd say "allowLanding: false" is a direct instruction, that this craft has nothing about battlescape, thus no need to have a preview.
Correct, but I will still only add conditions, which are directly required to prevent crashes here.
For now, these are:
1. unit capacity > 0 (`soldiers` > 0)
2. map must be defined (`battlescapeTerrainData` is defined)
If we need more conditions in the future, they can be added.
-
How do I use this?
Name: visibility_mode var BattleUnitVisibility.Tag
Sorry, the description is not obvious...
-
This do nothing if you do not add new tags for this, idea was you can define different and each script can interact with each other based on this value, like you have normal visibility bonus script but it should not work for infrared visibility. This value allow to check if you should apply bonuses or not.
-
This do nothing if you do not add new tags for this, idea was you can define different and each script can interact with each other based on this value, like you have normal visibility bonus script but it should not work for infrared visibility. This value allow to check if you should apply bonuses or not.
Thanks, I think I get the basic idea, but I cant figured out the proper syntax for that. Could you pls provide a script example of this? Like for instance, how do I apply a bonus to night vision, that comes from soldier bonus tag?
-
Can AI use sprint if this option is on for the player?
-
Can AI use sprint if this option is on for the player?
Maybe.
It was added here: https://github.com/MeridianOXC/OpenXcom/commit/8c3da2096de818b3ff3646f08a15bebc86ae5388
I never tried it, so can't confirm.
-
Thanks, I think I get the basic idea, but I cant figured out the proper syntax for that. Could you pls provide a script example of this? Like for instance, how do I apply a bonus to night vision, that comes from soldier bonus tag?
To use it you need define new tag similar to other tags but it not used like other ones:
extended:
tags:
RuleItem:
ITEM_NV_GOGGLES: int
BattleUnitVisibility:
VISIBILITY_NV_GOGGLES: int
scripts:
visibilityUnit:
- offset: 3
code: |
var int itemA;
var int itemB;
var int targetShade;
var ptr BattleItem item;
var ptr RuleItem type;
#get info about left hand item
observer_unit.getLeftHandWeapon item;
item.getRuleItem type;
type.getTag itemA Tag.ITEM_NV_GOGGLES;
#get info about left hand item
observer_unit.getRightHandWeapon item;
item.getRuleItem type;
type.getTag itemB Tag.ITEM_NV_GOGGLES;
if eq visibility_mode null; #default visibility
#if left or rigth item have NV bonus
if or eq itemA 1 eq itemB 1;
target_unit.getTileShade targetShade;
if gt targetShade 9;
add current_visibility 48; #16*3 = 3 tiles better visibility in dark
set visibility_mode Tag.VISIBILITY_NV_GOGGLES; #toggle to NV mode
end;
end;
else eq visibility_mode Tag.VISIBILITY_NV_GOGGLES; #assume that other script already set "NV" mode, we only add small bonus in that case
if or eq itemA 1 eq itemB 1;
add current_visibility 16;
end;
end;
return current_visibility visibility_mode;
-
To use it you need define new tag similar to other tags but it not used like other ones:
extended:
tags:
RuleItem:
ITEM_NV_GOGGLES: int
BattleUnitVisibility:
VISIBILITY_NV_GOGGLES: int
scripts:
visibilityUnit:
- offset: 3
code: |
var int itemA;
var int itemB;
var int targetShade;
var ptr BattleItem item;
var ptr RuleItem type;
#get info about left hand item
observer_unit.getLeftHandWeapon item;
item.getRuleItem type;
type.getTag itemA Tag.ITEM_NV_GOGGLES;
#get info about left hand item
observer_unit.getRightHandWeapon item;
item.getRuleItem type;
type.getTag itemB Tag.ITEM_NV_GOGGLES;
if eq visibility_mode null; #default visibility
#if left or rigth item have NV bonus
if or eq itemA 1 eq itemB 1;
target_unit.getTileShade targetShade;
if gt targetShade 9;
add current_visibility 48; #16*3 = 3 tiles better visibility in dark
set visibility_mode Tag.VISIBILITY_NV_GOGGLES; #toggle to NV mode
end;
end;
else eq visibility_mode Tag.VISIBILITY_NV_GOGGLES; #assume that other script already set "NV" mode, we only add small bonus in that case
if or eq itemA 1 eq itemB 1;
add current_visibility 16;
end;
end;
return current_visibility visibility_mode;
Thank you very much!
-
Small request to community, I mess with unit pathfinding in version 7.5.5 and probably break some thing, if someone look for bugs in new version I would be thankful.
In meantime I will mess with this code more and look for adding multipliers for move cost.
-
I have a question because I want to set up some CI/CD for some IDT mods (everyone would be free to use it though, of course);
- would it be possible to run JUST the OXCE validation and exit immediately (preferably with non-zero exit code if validation failed, but it could also be scraped from logs)
- if so, would this validation require the vanilla [UFO] assets to be present? It would make the pipeline a bit more involved in that case, but not impossible.
If this can be achieved, when committing to GitHub, using GitHub Actions, I can set up a pipeline that does some basic sanity checking automatically.
Thanks for any insights
-
This will require original data, at least for surfaces validation, some surfaces are from base game, if we skip then then it would report false positives.
Other data is not logically required to validate most of data but there are hardcoded checks for it to be present.
Another question is what it should load, as curretlyis expect very specific places to load mods (plus zip files).
Overall it would be preferred to add special mode for this only, some kind of new command line parameter that allow only loading `Mod` and return 0 or 1 depend if it throw exception.
-
That would be awesome. But even if the vanilla game files are required, it would still be useful, but I would have to expand the pipelines to allow providing those files somehow. Making it a bit more complex to set up.
The most important bit would be the checking then exiting (with 0/1 exit code). If it wasn't dependent on vanilla files it would just be a bonus.
Overall it would be preferred to add special mode for this only, some kind of new command line parameter that allow only loading `Mod` and return 0 or 1 depend if it throw exception.
If this gets implemented, I would be very interested in it.
-
I noticed that the notes panel that can be brought up from anywhere via Ctrl+N, can indeed be brought up from anywhere, including the notes panel. It's possible to press the hotkey multiple times, and have to close the menu multiple times as a result. It might be a good idea to disable the keyboard shortcut when it's already open.
-
In recent nightly I added option to control cost of armor moving, now is possible to implement "glue" gun that prevent unit form moving from given spot.
By default each unit use value from:
armors:
- type: STR_NONE_UC
moveCost:
basePercent: [100, 100] #TU%, ENERGY%
Then in y-script you can alter it per unit:
begin;
var int temp;
unit.MoveCost.getBaseTimePercent temp;
add temp 100;
unit.MoveCost.setBaseTimePercent temp;
end;
This properties can have any value but game enforce that result TU cost is in range [1, 254] and Energy in [0, 255].
As side notes, now save files should be smaller by up to 40% because game stop print some whitespaces that take took lot wasted of space in file.
-
Do you guys have any plans to fix that issue?
-
There is multiple corner cases to consider when fixing some thing like this, maybe in some future I will visit this again as there still some cases I would like to fix.
[ps]
I look a bit on this case, it can't be easy fix by switch drawing background and unit as this back part is already drawn on top of background.
Problem is that tiles on front overlap back part.
-
Yeah, I guess... Is there an option to crop it?
-
crop what exactly? And when exactly?
Yesterday I think ablaut it and how exactly could possible to tackle this problem. And I probably get solution that could fix it and other similar problems.
Right now in OXCE back part is drawn when game try draw back tile, but we could split this back graphic in half and draw each part with with parts that are on side tiles.
-
crop what exactly? And when exactly?
Yesterday I think ablaut it and how exactly could possible to tackle this problem. And I probably get solution that could fix it and other similar problems.
Right now in OXCE back part is drawn when game try draw back tile, but we could split this back graphic in half and draw each part with with parts that are on side tiles.
(https://i.pinimg.com/474x/29/6f/29/296f2918a46b80297d5692472a19f598.jpg)
-
I make some initial test for solution (in attachment is example).
But I see it not fully fix it as wheat is so hight that is still easy peak out disc graphic.
Another thing is that now selection box do not go pass middle of disc as it use to.
-
I wonder if the original game also had this bug?
-
If you want you can check it out:
https://github.com/Yankes/OpenXcom/commit/92533e82a817c55c2c20fb17bb0ee8681d2417d5
This probably stay as experiment and will not be included to OXCE.
-
Oh, cool, I'll look through it. Although, I'm not that good at rendering things =)
-
Question is could we fix it other way around? instead making workaround wheat we could simply remove wheat when unit stand on it.
This will solve most graphic glitches too when unit move.
-
Well, what about something with not so solid shape, like Reaper, for example?
-
I mean very simple logic:
if tile have unit, do not show this graphic or show different one.
Simply each tile will have two graphic styles, one for "no unit" and another "have unit over".
Small hack:
if (unit == nullptr)
{
// Draw object
tmpSurface = tile->getSprite(O_OBJECT);
if (tmpSurface)
{
if (tile->isBackTileObject(O_OBJECT))
{
if (tile->getObstacle(O_OBJECT))
Surface::blitRaw(surface, tmpSurface, screenPosition.x, screenPosition.y - tile->getYOffset(O_OBJECT), obstacleShade, false, _nvColor);
else
Surface::blitRaw(surface, tmpSurface, screenPosition.x, screenPosition.y - tile->getYOffset(O_OBJECT), tileShade, false, _nvColor);
}
}
}
Make interesting result (see in attachment).
-
Looks promising! Do we need to define it for each MCD we want to alter this way?
-
Its not implemented, this is only hack to check if it will work, how its will exactly work will be determined later.
-
I have a question, why items, placed on map with `items` property can be fused with `fuseTimers` and `randomizedItems` are not fused?
-
Yes, this is whole point of this two properties, one is designed to place "fused" items and second is for not "fused" items.
-
I thought the point is that one is random, another fixed... Ok, if it's intended
-
What do you think about moving to C++ 20? =)
-
What do you think about moving to C++ 20? =)
This is breaking change, at least after 2024 when every env we use have full C++20 support.
-
You need to be running OXCE 7.5.7 (https://lxnt.wtf/oxem/#/Extended) (Preview Build) or later to use this new version.
Do you want to tell us anything interesting?
-
You need to be running OXCE 7.5.7 (https://lxnt.wtf/oxem/#/Extended) (Preview Build) or later to use this new version.
Do you want to tell us anything interesting?
Version 7.5.7 has an interesting new feature that allows for better control of movement costs:
In recent nightly I added option to control cost of armor moving, now is possible to implement "glue" gun that prevent unit form moving from given spot.
By default each unit use value from:
armors:
- type: STR_NONE_UC
moveCost:
basePercent: [100, 100] #TU%, ENERGY%
Then in y-script you can alter it per unit:
begin;
var int temp;
unit.MoveCost.getBaseTimePercent temp;
add temp 100;
unit.MoveCost.setBaseTimePercent temp;
end;
This properties can have any value but game enforce that result TU cost is in range [1, 254] and Energy in [0, 255].
As side notes, now save files should be smaller by up to 40% because game stop print some whitespaces that take took lot wasted of space in file.
It is a pretty fun addition. (https://openxcom.org/forum/Themes/InsidiousV1-k/images/post/thumbup.gif)
-
Thanks for the information. I just would like to understand why there was no announcement with a description of the changes? Or is there a big 7.6.0 release planned with a lot of changes? And when is it planned?
-
Thanks for the information. I just would like to understand why there was no announcement with a description of the changes? Or is there a big 7.6.0 release planned with a lot of changes? And when is it planned?
When will be new version released is up to Meridian. And every thing that is working at this point from nightly it will be included. This mean it could be lot of changes or only few.
And for announcement, post that The Martian link is from this thread, more official could be only change log in new release :>
-
Thanks for the information. I just would like to understand why there was no announcement with a description of the changes? Or is there a big 7.6.0 release planned with a lot of changes? And when is it planned?
The official update is not planned at the moment.
The next official version number will be 7.6, earliest possible date for it is May 2022 (or later).
-
The next official version number will be 7.6, earliest possible date for it is May 2022 (or later).
I understand. Thanks. Will wait. Armageddon is canceled, so there's time.
-
Suggestion
Quick change of vehicle equipment on keys 1-9 by analogy with the equipment of a soldier
-
And Lord said:
upon thy breast shalt thou go, and earth shalt thou eat all the days of thy life.
If God want to humans to fly he would give them wings.
Now OXCE support this God command and allow punish puny humans that try to fly using alien tech.
You can make now that any human that try fly up will pay heavy energy penalty for doing so,
flaying down as is more in line of God plan could be even cost less than previously.
armors:
- type: STR_FLYING_SUIT_UC
moveCost:
#fist level of multipliers
basePercent: [100, 100] #overall move cost
#second level of multipliers
baseNormalPercent: [100, 100] #move cost for ground
baseFlyPercent: [100, 100] #move cost for flying
#third level of multipliers
walkPercent: [100, 50] #cost of normal move type
runPercent: [75, 75] #cost of run aka with `ctrl`
strafePercent: [100, 50] #cost of strafe when `ctrl` and only one tile aside
sneakPercent: [100, 50] # !new move type with `alt`, force unit to move on ground even if is capable of flying
flyWalkPercent: [100, 50] #cost of normal move type in air
flyRunPercent: [75, 75] #cost of run aka with `ctrl` in air
flyStrafePercent: [100, 50] #cost of strafe when `ctrl` and only one tile aside in air
flyUpPercent: [100, 0] #cost of flying up
flyDownPercent: [100, 0] #cost of flying down
gravLiftPercent: [100, 0] #cost for using gravLift
[ps]
fixed type in example, correct version of OXCE is 7.5.10
-
Funny glitch that change tank graphic when you swap move type.
-
New changes in nightly:
- Script now can change movement type of unit, aka swap fly with walk.
- Rule set and script can alter cost of moving item in inventory:
items:
- type: STR_PISTOL
inventoryMoveCost:
basePercent: 200
-
looks very interesting =)
I cant see vanilla multiple layer toggle in extended options. What if I toggle it on, then change the mod with extended options - can I toggle it off?
-
looks very interesting =)
I cant see vanilla multiple layer toggle in extended options. What if I toggle it on, then change the mod with extended options - can I toggle it off?
You have debug turned on in the options.cfg file, so it shows the debug button instead.
Normal players will see the layer toggle button.
-
Oh, I see, thx
-
How to disable the option to kill prisoners? I was unaware of its addition/existence until someone brought that up on XPZ channel randomly.
-
How to disable the option to kill prisoners? I was unaware of its addition/existence until someone brought that up on XPZ channel randomly.
1/ If you mean in the Alien Containment GUI, there is no option for it, it was always like that (since 12th October 2013 when the Alien Containment GUI was added).
Even though it doesn't say it explicitly, the "Remove" button does kill the alien and puts its corpse into general stores, both in OXC and OXCE.
3 years ago (29th April 2019), I have added some more checks when removing/killing the aliens: the corpse is not generated if the corpse item has either `recover: false` or `recoverCorpse: false`.
So you could use that, but it will affect also the recovery from the battlefield, not only from the alien containment and from the interrogation.
2/ If you mean after Interrogation, then there is an option called "Retain interrogated aliens".
-
1/ If you mean in the Alien Containment GUI, there is no option for it, it was always like that (since 12th October 2013 when the Alien Containment GUI was added).
Even though it doesn't say it explicitly, the "Remove" button does kill the alien and puts its corpse into general stores, both in OXC and OXCE.
Yes I mean that, or more precisely situation when you have no prison space at all (or so it seems?), and the button says explicitly "Kill" (it's along sale and transfer buttons). However I think I can handle it mod-side... I just need to know when precisely this option appears, and when it doesn't - if you have normal prison overflow, it doesn't seem to be the case.
-
Yes I mean that, or more precisely situation when you have no prison space at all (or so it seems?), and the button says explicitly "Kill" (it's along sale and transfer buttons). However I think I can handle it mod-side... I just need to know when precisely this option appears, and when it doesn't - if you have normal prison overflow, it doesn't seem to be the case.
Hmm, that's strange.
I thought there were only 2 possibilities:
a/ if "Live alien sale" option is disabled, then there is only 1 button called "Remove" (which does the same as "Kill")
b/ if "Live alien sale" option is enabled, then there are 2 buttons called "Kill" and "Sell"
I will try different combinations later today, maybe there's a combination I am forgetting...
EDIT: I did indeed misremember... see corrected statement 2 posts below
-
Hmm, that's strange.
I thought there were only 2 possibilities:
a/ if "Live alien sale" option is disabled, then there is only 1 button called "Remove" (which does the same as "Kill")
b/ if "Live alien sale" option is enabled, then there are 2 buttons called "Kill" and "Sell"
I will try different combinations later today, maybe there's a combination I am forgetting...
In both XCF and Piratez, "live alien sale" and "retain interrogated aliens" are "yes" and "no", respectively. Upon excess of prisoners, the game forces a sale, not a kill. The forced sale did not leave corpses, just money. Attached are examples of Piratez and XCF.
-
In both XCF and Piratez, "live alien sale" and "retain interrogated aliens" are "yes" and "no", respectively. Upon excess of prisoners, the game forces a sale, not a kill. The forced sale did not leave corpses, just money. Attached are examples of Piratez and XCF.
OK, I read the code and here's an updated version (I did misremember a few things)
if (Options::canSellLiveAliens == true AND Options::retainCorpses == true)
{
show 3 buttons (kill, sell, transfer/cancel)
}
otherwise
{
show 2 buttons (remove, transfer/cancel)
}
kill button = always kills
sell button = always sells
remove button:
1. sells if Options::canSellLiveAliens == true AND Options::retainCorpses == FALSE
2. kills in all other cases
Yes I mean that, or more precisely situation when you have no prison space at all (or so it seems?), and the button says explicitly "Kill" (it's along sale and transfer buttons). However I think I can handle it mod-side... I just need to know when precisely this option appears, and when it doesn't - if you have normal prison overflow, it doesn't seem to be the case.
Kill button (with explicit label "Kill") only ever appears when "Retain corpses" and "Sell aliens" options are both simultaneously turned on.
Since Piratez forces "Retain corpses" to be turned off... I don't see a way how the "Kill" button could appear in Piratez.
I'll need help... best a save where I can see it happening.
-
I'll need help... best a save where I can see it happening.
Here's my Piratez save from my previous campaign that I used for the screenshots. I added manually the extra prisoners.
If changed to "retainCorpses: true" in "Piratez_Globals.rul" then I get the "Kill" button.
-
That's correct, isn't it?
I meant a save in real Piratez, without submods.
-
There are two submods: cities lores and stat strings. The save of the Piratez version is M3 or so, but I ran it on the latests mod version.
-
There are two submods: cities lores and stat strings. The save of the Piratez version is M3 or so, but I ran it on the latests mod version.
Sigh :(
You have submodded Piratez with "retainCorpses: true"... which effectively turns on the "Kill" button.
(I know about this scenario, it is correct, and I don't need a save to illustrate it)
I want to see a situation/save where "retainCorpses: false" and you can still somehow see the "Kill" button, as reported by Dioxine.
-
Sigh :(
You have submodded Piratez with "retainCorpses: true"... which effectively turns on the "Kill" button.
(I know about this scenario, it is correct, and I don't need a save to illustrate it)
I want to see a situation/save where "retainCorpses: false" and you can still somehow see the "Kill" button, as reported by Dioxine.
My bad, I didn't get it. The switch to "true" was a direct ruleset modification of Piratez.
As per the "retainCorpses: true", I cannot produce said "kill" case, as I think it isn't possible without a submod as you put it.
The OP in the Matrix Room who reported this issue wasn't clear if this was due to a stock or modded game.
-
Is this info valid? https://github.com/MeridianOXC/OpenXcom/blob/66cadb7e5db5f2ba2a60c2b4dbeed33812acfa38/src/Basescape/NewResearchListState.cpp#L300 (https://github.com/MeridianOXC/OpenXcom/blob/66cadb7e5db5f2ba2a60c2b4dbeed33812acfa38/src/Basescape/NewResearchListState.cpp#L300)
I think we do save it in `discovered` section of the save file...
-
Is this info valid? https://github.com/MeridianOXC/OpenXcom/blob/66cadb7e5db5f2ba2a60c2b4dbeed33812acfa38/src/Basescape/NewResearchListState.cpp#L300 (https://github.com/MeridianOXC/OpenXcom/blob/66cadb7e5db5f2ba2a60c2b4dbeed33812acfa38/src/Basescape/NewResearchListState.cpp#L300)
I think we do save it in `discovered` section of the save file...
yes, the info is valid.
in the `discovered` section, we save the discovered topics, not the unlocked topics
-
ok, I see, thanks!
-
Sorry for asking it may be 2nd time, but I still don't understand 2 stage ship mission capture mechanics. Last time I got cargo ship and stunned 2 aquatoids. One of them I left on desk but 2nd brought to Triton and put there. I managed to clear 2nd stage but aquatoid who left in Triton game consider as dead. That's sux cause I need him for research. So questions - still annoying bug in OXCE or it designed by default? What should I do next time to prevent deaths of captured aliens on 1st stage? Should I leave them outside Triton? And how about cruise ship as well? In some mobs (like TWoTS) no ship there at all just escape tile area.
-
I would need a save file before the end of the mission to explain what happened.
Without it I can just say I am not aware of any bugs.
-
I noticed OXCE Nightly has a new version. Since few versions ago OXCE shows the TUs and Energy available on the battlescape unit path in green and orange font, respectively. But the new version shows them in white font, making a bit difficult to tell which one is which at a glance. Is this a setting that can be reversed somewhere? Or there's a better way to do this?
-
I noticed OXCE Nightly has a new version. Since few versions ago OXCE shows the TUs and Energy available on the battlescape unit path in green and orange font, respectively. But the new version shows them in white font, making a bit difficult to tell which one is which at a glance. Is this a setting that can be reversed somewhere? Or there's a better way to do this?
Upper one is TU, lower one is energy.
The previous colors were confusing (for me at least), inconsistent with OXC and also didn't work in TFTD.
I fixed the colors and also several combinations of settings, which didn't work either.
-
Upper one is TU, lower one is energy.
The previous colors were confusing (for me at least), inconsistent with OXC and also didn't work in TFTD.
I fixed the colors and also several combinations of settings, which didn't work either.
Can those colors be part of a user setting?
-
Can those colors be part of a user setting?
Why are you asking me questions you know the answer to?
Yes, everything can be done.
I don't think the option is needed and I am very picky adding new user options.
-
Why airlock no longer dismantle? Sometimes I need rebuild base in another location but now it's impossible to do. Checked vanilla TFTD and TWoTS both.
-
Why airlock no longer dismantle? Sometimes I need rebuild base in another location but now it's impossible to do. Checked vanilla TFTD and TWoTS both.
A bug.
Will be fixed with the next release.
-
I noticed with TWoTS that the equipment given to the drones is not saved across missions, like with aquanauts, so when you always want to give them the same equipment, you need to do it every time. I suppose this could be an OXCE issue, rather than the mod? Shouldn't the equipment be treated the same way irrespective of whether you are equipping a soldier or an equipment-carrying drone?
-
Is the drone a HWP-like unit?
If yes, it doesn't really "exist" on geoscape like soldiers... and nothing can be saved on it.
-
Is the drone a HWP-like unit?
If yes, it doesn't really "exist" on geoscape like soldiers... and nothing can be saved on it.
It's a 1x1 unit. So maybe yes. In some respects, it's different from traditional 2x2 HWPs. But I suppose the result is the same.
The differences are for example that some but not all 1x1 drones can examine and pick up items or bodies. So that feature is distinct from the size.
I wonder why a 2x2 HWP can't identify a body (whether it's alive or not, for example) while 1x1 can. I wonder if this has something to do with the precise location of 2x2 being undefined or something else.
-
I wonder why a 2x2 HWP can't identify a body (whether it's alive or not, for example) while 1x1 can. I wonder if this has something to do with the precise location of 2x2 being undefined or something else.
It may very well. The default is editable. Yes, and Reapers have always been considered alive.
-
Segfault on what I'm pretty sure is a collision with an not-yet-visible enemy. X-Com Files 2.5 with some tweaks, OXCE 7.5.3.
Edit: Needs the agent to be running and not looking where they go, of course.
-
Segfault on what I'm pretty sure is a collision with an not-yet-visible enemy. X-Com Files 2.5 with some tweaks, OXCE 7.5.3.
Edit: Needs the agent to be running and not looking where they go, of course.
Something wrong with pathfinding, goes into negative Z coordinates (36,52,-1).
Doesn't happen in OXCE 7.5.5 or higher.
@Yankes: do you want to check it on 7.5.3? or just let it go?
-
If I have some free time I will check it, some refactors could move this bug around (aka is still present but different condition is needed)
-
Sorry for asking it here, but my question have possible future request, depends on answers. For example I have two research projects:
- name: STR_PROJECT_1
cost: 10
points: 50
needItem: true
- name: STR_PROJECT_2
cost: 10
points: 50
needItem: true
So questions:
1. Is it possible automatically finish STR_PROJECT_2 when STR_PROJECT_1 finished, make it grey color in tree if it already started or not but it present as possible in lab project list? I tested mechanics with "disables" command, what makes it red, removes from list, removes scientists from it as well, but I'm looking something like "complete" command.
2. If it's not possible could we have it as future request in OXCE?
Thank you all for your answers in advance.
-
getOneFree command
-
GetOneFree could do trick, but it's not finishes two or more "bonus" projects simultaneously. It pick one random or or sequentially from the list.
-
OXCE crashes when I pressing "preview" button on Moray interceptor. I think it happened because this ship used for interception purposes but not for delivery aquanauts.
[14-06-2022_21-00-54] [FATAL] A fatal error has occurred: Segmentation fault.
[14-06-2022_21-00-54] [FATAL] 0x5cbe20 OpenXcom::CrossPlatform::stackTrace(void*)
[14-06-2022_21-00-54] [FATAL] 0x5ccca0 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[14-06-2022_21-00-54] [FATAL] 0x41c7f0 signalLogger(int)
[14-06-2022_21-00-54] [FATAL] 0x9f4930 OpenXcom::UfopaediaStartState::think()
[14-06-2022_21-00-54] [FATAL] 0x7fff6e19c6d0 _C_specific_handler
[14-06-2022_21-00-54] [FATAL] 0x7fff6e1b1fb0 _chkstk
[14-06-2022_21-00-54] [FATAL] 0x7fff6e161020 RtlRaiseException
[14-06-2022_21-00-54] [FATAL] 0x7fff6e1b0bd0 KiUserExceptionDispatcher
[14-06-2022_21-00-54] [FATAL] 0x522710 OpenXcom::BattlescapeGenerator::run()
[14-06-2022_21-00-54] [FATAL] 0x447960 OpenXcom::CraftSoldiersState::btnPreviewClick(OpenXcom::Action*)
[14-06-2022_21-00-54] [FATAL] 0x5e8860 OpenXcom::InteractiveSurface::handle(OpenXcom::Action*, OpenXcom::State*)
[14-06-2022_21-00-54] [FATAL] 0x6a4380 OpenXcom::State::handle(OpenXcom::Action*)
[14-06-2022_21-00-54] [FATAL] 0x5e3f50 OpenXcom::Game::run()
[14-06-2022_21-00-54] [FATAL] 0x41c950 SDL_main
[14-06-2022_21-00-54] [FATAL] 0x9f6460 console_main
[14-06-2022_21-00-54] [FATAL] 0x9f6580 WinMain
[14-06-2022_21-00-54] [FATAL] ??
[14-06-2022_21-00-54] [FATAL] ??
[14-06-2022_21-00-54] [FATAL] 0x7fff6c757020 BaseThreadInitThunk
[14-06-2022_21-00-54] [FATAL] 0x7fff6e162630 RtlUserThreadStart
[14-06-2022_21-01-02] [FATAL] OpenXcom has crashed: Segmentation fault.I'm adding save file too.
Question about OXCE special strings - any STR in ruleset what could be used to prevent crash and remove preview button there when player selecting non-transport ship?
-
OXCE crashes when I pressing "preview" button on Moray interceptor. I think it happened because this ship used for interception purposes but not for delivery aquanauts.
[14-06-2022_21-00-54] [FATAL] A fatal error has occurred: Segmentation fault.
[14-06-2022_21-00-54] [FATAL] 0x5cbe20 OpenXcom::CrossPlatform::stackTrace(void*)
[14-06-2022_21-00-54] [FATAL] 0x5ccca0 OpenXcom::CrossPlatform::crashDump(void*, std::__cxx11::basic_string<char, s