Search the Community

https://en.wikipedia.org/wiki/Raspberry_Pi https://www.raspberrypi.org/products/raspberry-pi-4-model-b/ https://www.raspberrypi.org/products/raspberry-pi-4-model-b/specifications/ https://www.tomshardware.com/reviews/raspberry-pi-4-b,6193.html https://www.anandtech.com/show/14581/raspberry-pi-4-launched-quad-cortex-a72-project-board-for-35-dollars https://www.raspberrypi.org/magpi-issues/MagPi83.pdf Major improvements across the "board". The quad-core Cortex-A72 with other improvements is anywhere from 25% to 300% faster than the A53 used in the Raspberry Pi 3 . No eMMC but an SSD could be used with one of the two new USB 3 ports (booting from USB or Ethernet not supported at launch, should be ready within weeks). There are three RAM options: 1 GB ($35), 2 GB ($45), 4 GB ($55). The RAM is now LPDDR4 instead of LPDDR2. The 2 GB option is a bit unnecessary IMO and seems to be the least popular, as it's the model least likely to be sold out online (as far as I can tell). Ethernet speed can actually hit close to 1 Gbps (943 Mbps), up from 237 Mbps. There is Bluetooth 5.0 support but I haven't seen any testing related to that (I would love to use it for longer range audio transmission to BT 5.0 headphones). RasPi 3 cases are incompatible due to some port shuffling. There are now two micro-HDMI ports instead of one full size HDMI, so you probably need a new cable. The device can output to two 4K displays at 30 FPS, or one 4K display at 60 FPS (presumably two 1080p displays @ 60+ FPS, and so on). Although the new GPU has 4K@60Hz H.265 decode support, actually streaming 4K and even lower resolutions on Raspbian had issues in testing, that will hopefully be resolved with updates soon. LibreELEC developers have been working with the Pi Foundation for months to support the Pi 4, and have an alpha version out. Power draw and heat are up. You'll probably want a FLIRC case or something that can provide cooling. Power is now provided using a USB Type-C cable. Due to a screw up by the Raspberry Pi Foundation, some USB-C cables don't work. But the ones that do work should be the cheapest. Can it run TDM? The CPU and GPU are much better and the potentially quadrupled RAM could be a big help. The 4 GB version can be a legitimate desktop replacement for many users, albeit with some quirks.

I got the following error when building in Ubuntu 19.10: make[3]: Entering directory '/home/biel/games/src/DarkRadiant/plugins/script' CXX ScriptingSystem.lo CXX ScriptCommand.lo CXX ScriptModule.lo CXX ScriptMenu.lo CXX ScriptWindow.lo CXX SceneNodeBuffer.lo CXX PythonModule.lo In file included from /usr/include/pybind11/pytypes.h:12, from /usr/include/pybind11/cast.h:13, from /usr/include/pybind11/attr.h:13, from /usr/include/pybind11/pybind11.h:49, from PythonModule.h:5, from PythonModule.cpp:1: PythonModule.cpp: In static member function ‘static void script::PythonModule::RegisterToPython(const ModuleRegistrationCallback&)’: PythonModule.cpp:30:13: error: ‘dev0’ was not declared in this scope 30 | PYBIND11_VERSION_PATCH << std::endl; | ^~~~~~~~~~~~~~~~~~~~~~ make[3]: *** [Makefile:674: PythonModule.lo] Error 1 make[3]: Leaving directory '/home/biel/games/src/DarkRadiant/plugins/script' make[2]: *** [Makefile:442: all-recursive] Error 1 make[2]: Leaving directory '/home/biel/games/src/DarkRadiant/plugins' make[1]: *** [Makefile:751: all-recursive] Error 1 make[1]: Leaving directory '/home/biel/games/src/DarkRadiant' make: *** [Makefile:492: all] Error 2

Folks, I've decided to start a new thread on this since the other recent Linux threads are not really the appropriate place (IMHO) to discuss the gory details about fixing the 2.05-beta source code so that it compiles and runs under Linux. Unfortunately, there is already some existing discussion about compiles against 2.05-beta (and "latest SVN") mixed about in these 2 threads: Compiling TDM 2.04 Under LinuxCalling on Linux devs: TDM team needs helpTo start this thread off, I'm replying to this post by duzenko. Good news! I tweaked the 'if (1)' line (in 'renderer/RenderSystem.cpp') to be 'if (0)' then rebuilt and ran TDM. Although, IMHO, this is a rather haphazard way to go about things (I'd prefer to run a debugger, with full source code available), it looks like you may have hit the nail on the head, duzenko! Note: I'm using SVN revision #6642 to run this test since that's the only one I'd gotten to successfully build when I last gave up on this. And I'm running with the 2.04 (not 2.05-beta) PK4 resources, so this test isn't as "pure" as I'd like it to be. But the 2 missions ("Closemouthed Shadows" and "The Outpost") which had been immediately failing (at the 'memcpy()') after the "Press 'attack' to start the mission" point are now running! Now, be aware that the crashes that Baal experienced appeared to be different than my crashes, so please don't consider this problem solved just yet! But it's an important first step. I tried to do some further testing, but ran into limitations of my memory of certain SVN commands, so that will have to wait for another day.

DarkRadiant stopped compiling after a series of system package updates in openSUSE Tumbleweed today. Oddly enough, I get an error related to boost again, although I compile DR with the same Boost version downloaded from the official website and compiled locally (was 1.54, now 1.59 but same issue). Core DR appears to compile, the error is in the filters plugin. Can anyone please take a look and fix this? make[2]: Entering directory '/home/mircea/Games/Quake/TheDarkMod/DarkRadiant_GIT/plugins/filters' CXX XMLFilter.lo CXX BasicFilterSystem.lo CXX filters.lo CXXLD filters.la libtool: warning: '/usr/lib64/gcc/x86_64-suse-linux/5/../../../../lib64/libxml2.la' seems to be moved .libs/XMLFilter.o: In function `boost::re_detail_106000::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::unwind_extra_block(bool)': /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp:1250: undefined reference to `boost::re_detail_106000::put_mem_block(void*)' .libs/XMLFilter.o: In function `boost::cpp_regex_traits<char>::transform_primary(char const*, char const*) const': /usr/include/boost/regex/v4/cpp_regex_traits.hpp:966: undefined reference to `boost::re_detail_106000::cpp_regex_traits_implementation<char>::transform_primary(char const*, char const*) const' .libs/XMLFilter.o: In function `boost::cpp_regex_traits<char>::transform(char const*, char const*) const': /usr/include/boost/regex/v4/cpp_regex_traits.hpp:962: undefined reference to `boost::re_detail_106000::cpp_regex_traits_implementation<char>::transform(char const*, char const*) const' .libs/XMLFilter.o: In function `void boost::re_detail_106000::raise_error<boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits<char> > > >(boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::error_type)': /usr/include/boost/regex/pattern_except.hpp:75: undefined reference to `boost::re_detail_106000::raise_runtime_error(std::runtime_error const&)' .libs/XMLFilter.o: In function `boost::re_detail_106000::cpp_regex_traits_implementation<char>::error_string(boost::regex_constants::error_type) const': /usr/include/boost/regex/v4/cpp_regex_traits.hpp:449: undefined reference to `boost::re_detail_106000::get_default_error_string(boost::regex_constants::error_type)' .libs/XMLFilter.o: In function `boost::re_detail_106000::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::extend_stack()': /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp:217: undefined reference to `boost::re_detail_106000::get_mem_block()' .libs/XMLFilter.o: In function `boost::re_detail_106000::save_state_init::save_state_init(boost::re_detail_106000::saved_state**, boost::re_detail_106000::saved_state**)': /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp:107: undefined reference to `boost::re_detail_106000::get_mem_block()' .libs/XMLFilter.o: In function `boost::re_detail_106000::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::match_imp()': /usr/include/boost/regex/v4/perl_matcher_common.hpp:214: undefined reference to `boost::re_detail_106000::verify_options(unsigned int, boost::regex_constants::_match_flags)' .libs/XMLFilter.o: In function `boost::re_detail_106000::save_state_init::~save_state_init()': /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp:115: undefined reference to `boost::re_detail_106000::put_mem_block(void*)' /usr/include/boost/regex/v4/perl_matcher_non_recursive.hpp:115: undefined reference to `boost::re_detail_106000::put_mem_block(void*)' .libs/XMLFilter.o: In function `boost::re_detail_106000::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, boost::match_results<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >)': /usr/include/boost/regex/v4/perl_matcher.hpp:382: undefined reference to `boost::re_detail_106000::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)' collect2: error: ld returned 1 exit status Makefile:490: recipe for target 'filters.la' failed make[2]: *** [filters.la] Error 1 make[2]: Leaving directory '/home/mircea/Games/Quake/TheDarkMod/DarkRadiant_GIT/plugins/filters' Makefile:446: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/mircea/Games/Quake/TheDarkMod/DarkRadiant_GIT/plugins' Makefile:752: recipe for target 'install-recursive' failed make: *** [install-recursive] Error 1

I have recently upgraded from openSUSE 13.2 to openSUSE Tumbleweed. I am able to compile DarkRadiant without any errors, but I can no longer run it. DR will immediately crash at startup when I try to do so. The crash takes place immediately after the menu in which I select the engine path, so it might occur when DR attempts to render something. mircea@linux-qz0r:~/Games/Quake/TheDarkMod/darkmod> /home/mircea/Games/Quake/TheDarkMod/DarkRadiant_GIT/install/bin/darkradiant Segmentation fault (core dumped) mircea@linux-qz0r:~/Games/Quake/TheDarkMod/darkmod> If it's of any help, here is also the darkradiant log: (140385268681216) Started logging to /home/mircea/.darkradiant/darkradiant.log (140385268681216) This is DarkRadiant 2.0.2 x64 (140385268681216) wxWidgets Version: 3.0.2 (140385268681216) ModuleRegistry: Warning! Module with name MainFrame requested but not found! Does anyone know what is happening please, and help me get DR back up and running? Relevant packages are: Boost 1.54.0 (separate), wxWidgets 2.8.12, gcc 5.0, Mesa 11.0.3. I attempted new settings but no change.

I am trying to compile the latest SVN engine, on openSUSE Tumbleweed (via gcc 4.8). Compilation goes well until the end, when the process mysteriously fails for an unexplained reason. The only thing that seems to be printed is the name of the file and something called "Error 1". Anyone else running across this, and knows of a solution? Thanks. cm/CollisionModel_load.cpp: At global scope: cm/CollisionModel_load.cpp:42:13: warning: ‘versioned’ defined but not used [-Wunused-variable] static bool versioned = RegisterVersionedFile("$Id: CollisionModel_load.cpp 6551 2015-10-15 18:48:23Z stevel $"); ^ In file included from include/boost/filesystem/path_traits.hpp:23:0, from include/boost/filesystem/path.hpp:25, from include/boost/filesystem.hpp:16, from framework/../idlib/../idlib/Image.h:29, from framework/../idlib/../idlib/Lib.h:230, from framework/../idlib/precompiled.h:106, from framework/precompiled_engine.h:28: include/boost/system/error_code.hpp:221:36: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable] static const error_category & posix_category = generic_category(); ^ include/boost/system/error_code.hpp:222:36: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable] static const error_category & errno_ecat = generic_category(); ^ include/boost/system/error_code.hpp:223:36: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable] static const error_category & native_ecat = system_category(); ^ scons: *** [build/release/core/cm/CollisionModel_load.o] Error 1 scons: building terminated because of errors.

Hello! First of all, you guys are awesome for bringing out a standalone TDM!! One "issue" that i observed during compilation of TDM2.0 source in VC2010 Ultimate on Windows 7 is that the DirectX SDK path is hardcoded as C:\Program Files (x86)\... which caused the the 'Engine' project build to fail, as my path was different. I had to go to 'engine.vcxproj', and manually replace all such paths for the source to compile. May i suggest that the path be taken from the environment variables (DXDSK_DIR or DIRECTX_SDK_HOME) instead?