Project Idea Sanity Check

40 views
Skip to first unread message

Jephunah Smith

unread,
Mar 7, 2013, 8:31:17 PM3/7/13
to open...@googlegroups.com
I had an idea for a project and I want to check with someone familiar with the code of OpenNERO to verify feasibility.

Long and short of it is that I want to see if it is possible to modify the game in such a way as to have a different class of unit on the battlefield.  One which will target its own team and avoid the enemy.  Ideally I would be able to change its weapon characteristics in order to cause its beam to provide positive effects, rather than negative, but that is not critical to the project.

Anyone know if I am biting off more than I can chew with this? 

Igor Karpov

unread,
Mar 8, 2013, 12:00:58 AM3/8/13
to open...@googlegroups.com
Hello Jephunah,

Assuming you mean the NERO mod, what you are proposing sounds doable, depending on the amount of time you have. Currently, the code for counting damage from guns (in mods/NERO/NeroEnvironment.py) is somewhat brittle, however, so if you do end up modifying it, I would double check to make sure your changes are doing what you think they are doing by using different colors of lasers, different looking units (changing size is pretty easy) and looking at the over-head debugging information which you can toggle with F2.

Good luck!

--Igor.


--
You received this message because you are subscribed to the Google Groups "opennero" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opennero+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Jephunah Smith

unread,
Mar 8, 2013, 3:34:23 PM3/8/13
to open...@googlegroups.com
When you said, "depending on the amount of time you have", what did you mean?  The time-frame I have on this is basically to the last week of April, but I work full-time, and have another class that has a project I will be working on as well.

Would adding a new unit type require major modifications to the engine?

Jephunah Smith

unread,
May 4, 2013, 2:54:05 AM5/4/13
to open...@googlegroups.com
Has anything changed with the build steps now that the boost pro site is closing?  I can't seem to get the CMake tool to find Boost.  I have done several different variations of install, download source and point to it, etc.  It just won't detect it.

Igor Karpov

unread,
May 4, 2013, 10:42:44 AM5/4/13
to open...@googlegroups.com
Two things to try:

 - try deleting the version of cmake/FindBoost.cmake that ships with OpenNERO - this will get cmake to use the one that comes with it instead.
 - in source/CMakeLists.txt there is a list of boost versions that might need to be updated.



--

Jephunah Smith

unread,
May 4, 2013, 2:27:27 PM5/4/13
to open...@googlegroups.com
I did add the boost version I tried to install first to the line in CMakeLists.txt under Source/ as follows:
SET(Boost_ADDITIONAL_VERSIONS 1.51.0 1.48.0 1.48 1.47.0 1.47 1.46.1 1.46.0 1.46 1.45.0 1.45 1.44.0 1.44 1.43.0 1.43 1.42.0 1.42)

When that didn't work, I just installed the 1.48.0 version, still no go.

Another thing.  The cmake folder under trunk/ only has 4 files in it:
bundly.py
bundle.sh
OpenNero-Info.plist
TargetDoc.cmake

I am not sure where to find FindBoost.cmake to delete it.  The only file on my system with that name is the one under the CMake 2.8/ install.

What was the lastest version of CMake you have used to build the OpenNERO source?


On Thursday, March 7, 2013 7:31:17 PM UTC-6, Jephunah Smith wrote:

Jephunah Smith

unread,
May 4, 2013, 3:37:06 PM5/4/13
to open...@googlegroups.com
Actually, I just read the post by Sule on Jan 21st and realized that you had already removed that file from the source.  I don't know if I had mentioned that I was trying to build the latest so that part is already done on my system.  The built in version of FindBoost.cmake already has quite a bit of future release values listed:

# Currently this module searches for the following version numbers:
# 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1,
# 1.36, 1.36.0, 1.36.1, 1.37, 1.37.0, 1.38, 1.38.0, 1.39, 1.39.0,
# 1.40, 1.40.0, 1.41, 1.41.0, 1.42, 1.42.0, 1.43, 1.43.0, 1.44, 1.44.0,
# 1.45, 1.45.0, 1.46, 1.46.0, 1.46.1, 1.47, 1.47.0, 1.48, 1.48.0,
# 1.49, 1.49.0, 1.50, 1.50.0, 1.51, 1.51.0, 1.52, 1.52.0,
# 1.53, 1.53.0, 1.54, 1.54.0, 1.55, 1.55.0, 1.56, 1.56.0

Is it possible that the following lines in the CMakeLists.txt conflict with what is already being done in the built in FindBoost.cmake?

FIND_PACKAGE (Boost COMPONENTS python filesystem serialization system date_time)

IF (NOT Boost_FOUND)
  # show an error message that boost was not found
  MESSAGE(FATAL_ERROR "Boost libraries were not found, please install from http://www.boost.org/")
ELSE (NOT Boost_FOUND)
  # show the boost libraries that were found
  # workaround for extra keywords showing up in Boost_LIBRARIES
  LIST(REMOVE_ITEM Boost_LIBRARIES "optimized")
  LIST(REMOVE_ITEM Boost_LIBRARIES "debug")
  foreach(arg ${Boost_LIBRARIES})
    MESSAGE(STATUS "Boost library: ${arg}")
  endforeach(arg ${Boost_LIBRARIES})
ENDIF (NOT Boost_FOUND)

Thanks

Jephunah Smith

unread,
May 4, 2013, 4:30:59 PM5/4/13
to open...@googlegroups.com
Was able to fix the issue.  I disabled the line in the Source/CMakeLists.txt:

SET(Boost_ADDITIONAL_VERSIONS 1.48.0 1.48 1.47.0 1.47 1.46.1 1.46.0 1.46 1.45.0 1.45 1.44.0 1.44 1.43.0 1.43 1.42.0 1.42)

I also had to add the BOOST_ROOT value manually in the CMake Gui.

I don't know if disabling the SET(... line was necessary, but I thought I would mention it.  The BOOST_Path may be unset as well, as the BOOST_ROOT was listed as an alternative in the FindBoost.cmake file.

Anyway, thanks for the help.
Reply all
Reply to author
Forward
0 new messages