Messages

1

Open Feedback / Mind Control and LoS

« on: November 20, 2019, 06:03:05 am »

Coming back for a campaign (first time in a few years) and progressed to the point of higher-level sectoids with mind control abilities.  I recall from the past (or at least thought) that psionics could only occur if an enemy has line of sight (not necessarily the alien with the mind control capabilities, but any enemy in line of sight of any friendly would allow a psi-capable alien to take advantage of).  I'm finding that this doesn't seem to be the case as I've been regularly on the receiving end of psionic attacks without any apparent enemy nearby.  As an example, I'm currently in a landed very large UFO mission and after only a few turns it seems that I'm constantly being barraged by psi attacks, even though the entire outside of the UFO has been cleared (I'm progressing inward, at this point, but haven't actually entered the UFO yet).

I looked online and the only info I can find is from the wiki, which states:

Alien Psionics Targeting

If any of your squad members, even a HWP, is visible to any alien during the Alien Turn, every member of your squad is at risk of attack from any psionic aliens, regardless of whether the spotter is psionic.

It should be noted that once you pass Turn 20, or if there are only 1 or 2 aliens left on the map, all of your squad members and their locations are revealed to the AI. This means you can expect a steady stream of psionic attacks after that turn if there any of the remaining aliens are capable of Psionic attack.

I may be about turn 20 now, but this has been going on for turns well before turn 20.  Did OpenXcom change the rules on this, or am I missing something obvious?

2

Suggestions / Re: interface: equip screen - "next/previous soldier" by arrow keys?

« on: November 13, 2012, 02:34:32 am »

clever idea.  I imagine it wouldn't really detract from the original design either.

3

Open Feedback / Re: Member Map

« on: November 13, 2012, 02:23:57 am »

Fun!  Good idea :-)

4

Programming / Re: Build fails with wstring::back() not found in linux

« on: November 10, 2012, 05:04:15 am »

Thanks for the replies.  Turns out that the pull was from a slightly older commit.  An upstream pull and merge fixed the problem.

5

Programming / Build fails with wstring::back() not found in linux (solved)

« on: November 08, 2012, 06:05:37 am »

Hi all!  It's been a while since I've been around, but recently updated to the most recent commit.  I'm getting a build error, though, and I'm not sure exactly what's up.  My build fails with the following:

Code: [Select]

/home/alienjon/git/OpenXcom/src/Interface/Text.cpp: In member function ‘void OpenXcom::Text::setText(const wstring&)’:
/home/alienjon/git/OpenXcom/src/Interface/Text.cpp:132:60: error: ‘std::wstring’ has no member named ‘back’
make[2]: *** [src/CMakeFiles/openxcom.dir/Interface/Text.cpp.o] Error 1
make[1]: *** [src/CMakeFiles/openxcom.dir/all] Error 2
make: *** [all] Error 2
Any ideas what could be up?

6

Programming / Re: Logging support (for bug reports and stuff)

« on: December 13, 2011, 04:20:24 am »

There's a (I suppose simple) logger that I've written for my own projects with a few options.  No dependencies or anything, just a simple text output to a error.log file.  Here's the implementation, if people think it's interesting enough I can incorporate/push it for people to check out more seriously.  It's all static so a log output can be requested anywhere that Logger.hpp is included:

Code: [Select]

/**
* @brief A domain error.
* @param e The error.
*/
static void error(const std::domain_error& e);

/**
* @brief An invalid argument error.
* @param e The error.
*/
static void error(const std::invalid_argument& e);

/**
* @brief A length error.
* @param e The error.
*/
static void error(const std::length_error& e);

/**
* @brief An out of range error.
* @param e The error.
*/
static void error(const std::out_of_range& e);

/**
* @brief A logic error.
* @param e The error.
*/
static void error(const std::logic_error& e);

/**
* @brief A range error.
* @param e The error.
*/
static void error(const std::range_error e);

/**
* @brief An overflow error.
* @param e The error.
*/
static void error(const std::overflow_error& e);

/**
* @brief An underflow error.
* @param e The error.
*/
static void error(const std::underflow_error& e);

/**
* @brief A runtime error.
* @param e The error.
*/
static void error(const std::runtime_error& e);

/**
* @brief A general std error.
* @param e The error.
*/
static void error(const std::exception& e);

/**
* @brief A non-exception error.
* @param error The error.
*/
static void error(const std::string& error);

/**
* @brief Log an informational message.
* @param message The message.
*/
static void log(const std::string& message);

/**
* @brief Log a warning.
* @param warning The warning.
*/
static void warn(const std::string& warning);

7

Programming / Re: Which development tools do you use?

« on: December 13, 2011, 04:03:00 am »

Eclipse representin' 

On a related note, I noticed that the wiki is looking for details on compiling in various platforms and that Eclipse hasn't been done yet.  Anyone planning on doing this?  I've now worked with this program in both Linux (Gentoo & Ubuntu) and Windows w/ MinGW, and as it's been a while since I've trolled the OpenXcom code/project I wouldn't mind getting a bit more involved again.

On an also related note: SupSuper.  A while back I noted that I was using Eclipse and included my .cproject and .project files in a Git push.  I've since discovered that's a bad idea (I've been working on one of my own projects - sorry for the haitus :-/).  Apparently they note system-specific information (ie: mingw32-make for Windows (instead of make for Linux) as well as library specific positions.  I don't know if anything came of it after we spoke last time, but I wanted to pass that along.