Hi, and welcome to CIGI. A little more background information would be helpful. I'm guessing from the m_Net.openSocket() method this is on the Windows platform, correct? Did you build the ccl_lib from source, did your co-worker build it from source, or did you get a pre-built DLL from somewhere? I've not built the ccl 4.0 lib yet, but version 3.3 is only dependent upon the MS CRT lib. If you are seeing a lot of dependent libs, I suspect those would be coming from your network module that you use...
Hi, and welcome to CIGI. A little more background information would be helpful. I'm guessing from the m_Net.openSocket() method this is on the Windows platform, correct? Did you build the ccl_lib from source, did your co-worker build it from source, or did you get a pre-built DLL from somewhere? I've not built the ccl 4.0 lib yet, but version 3.3 is only dependent upon the MS CRT lib. If you are seeing a lot of dependent libs, I suspect those would be coming from your network module that you use...
Updating the paths in config\sky.def will get the skydome working correctly.
OK, to get MPV minimally operational on Windows, I downloaded: HostEmulator_Win32_v3.3.3.zip mpv_content_2006-01-11.zip mpv-2.2.0-win32.zip I unpacked all of them to my C:\Temp directory: C:\Temp\HostEmulator_Win32_v3.3.3 C:\Temp\mpv_content_2006-01-11 C:\Temp\mpv-2.2.0-win32 I changed my C:\Temp\mpv-2.2.0-win32\config\system.def file to use: system { // The IP address of the host. host_addr = "127.0.0.1"; // The port that the host will be listening on. host_port = 8001; // The port that this program...
OK, to get MPV minimally operational on Windows, I downloaded: HostEmulator_Win32_v3.3.3.zip mpv_content_2006-01-11.zip mpv-2.2.0-win32.zip I unpacked all of them to my C:\Temp directory: C:\Temp\HostEmulator_Win32_v3.3.3 C:\Temp\mpv_content_2006-01-11 C:\Temp\mpv-2.2.0-win32 I changed my C:\Temp\mpv-2.2.0-win32\config\system.def file to use: system { // The IP address of the host. host_addr = "127.0.0.1"; // The port that the host will be listening on. host_port = 8001; // The port that this program...
OK, I will need to setup a test environment so I can look at this with you.
Actually, entity ID 0 is classically associated with the Ownship entity, which may or may not have a 3D model attached to the entity - it depends on your use case, but it is not a requirement. You are free to allocate entity IDs as you see fit for your application. Just in case alpha is an issue, I would try setting alpha to 255 for debugging. I confess it has been a while since I last used MPV and I don't have a current setup to look at right now. Which platform are you using for MPV: Windows or...
PHP updated
There appear to be two issues here: the TIFF plug-in is not being found and the terrain data is not being found. Which operating system are you running this on? The sample St. Louis terrain data must be downloaded and installed separately. Have you done this? If so, the terrain config file will need to be updated to point to it.
Does not support Boost 1.73
Here is a small example of adding components to an entity definition in HEMU3: entity { name = "f18c"; type = 118; class = fixedwing; component { name = "PositionLights"; id = 0; def_state = 0; state { name = "off"; value = 0; } state { name = "on"; value = 1; } } component { name = "AntiCollisionLights"; id = 1; def_state = 0; state { name = "off"; value = 0; } state { name = "on"; value = 1; } } } Hopefully this and the HEMU3 help file documentation will get you on track to meet your entity control...
My apologies for my tardy reply. In order to use scripting for these controls, you will need to define your entity type(s) and respective component parts in the HEMU3 entities.def configuration file. The HEMU3 script engine does type checking for these items, but the raw packet dialog does not. Best regards, Curt
Hi, can elaborate a bit more on what you are looking for and which operating system you want to target? The stand-alone demo environment is to download the CIGI Host Emulator 3 and the CIGI Multi-Purpose Viewer (and associated MPV Content). The host emulator only runs on Windows. If you are looking to implement either your own host or image generator, there are two open source CIGI libraries to choose from to manage the sending & receiving of CIGI messages over a transport protocol. Best regards,...
The link to the MPV wiki (http://sourceforge.net/apps/mediawiki/cigi/index.php?title=Mpv-main) is currently broken. Kind regards, Curt
Missing #ifdef _LIBCIGI_EXCEPTIONS logic for Interpreters
Is your view frustum attached to the entity you created with a valid EntityType or to a second entity that is nearby? If it is the former, did you add an adequate view offset to ensure the view frustum is outside the geometry of the model selected by the EntityType? If the view frustum is inside the model geometry and the model does not have backface polygon rendereing enabled (they typically do not), then you will see little or no geometry rendered. If it is the latter, have you confirmed the two...
Is your view frustum attached to the entity you created with a valid EntityType or to a second entity that is nearby? If it is the former, did you add an adequate view offset to ensure the view frustum is outside the geometry of the model geometry selected by the EntityType? If the view frustum is inside the model and the model does not have backface polygon rendereing enabled (they typically do not), then you will see little or no geometry rendered. If it is the latter, have you confirmed the two...
Is your view frustum attached to the entity you created with a valid EntityType or to a second entity that is nearby? If it is the former, did you add an adequate view offset to ensure the view frustum is outside the geometry of the model geometry selected by the EntityType? If the view frustum is inside the model geometry and the model does not have backface polygon rendereing enabled (they typically do not), then you will see little or no geometry rendered. If it is the latter, have you confirmed...
A beta version of the CCL that include v4.0 support exists, but has not been uploaded yet to SourceForge. There is also a second, clean-sheet development, libcigi, that supports v4.0.
Sounds like there are two things happening here. First, if you request an EntityType in an EntityControl packet that is not configured in MPV, it displays a default red object model to alert you to the error. Second, your view is being attached to the entity you create without enough offset from the entity position, so the view is very close to or inside the entity model. Hope this helps, Curt
As it happens, I recently built the 'ccl_3_3_3a.tar.gz' on Linux. I can confirm there is not a 'include/cigicl/CigiEventList.h' file in the installation. Is it possible 'CigiEventList.h' is part of the application code base and your build environment is not finding it?
First, my apologies for not looking at this sooner. There appears to be a minor GUI bug in HEMU 3.3.3. If you select your "Front" view in the Views tab, then select another view, and then re-select your "Front" view you should then see the view component listed in the Components box.
I've encountered a one character bug in the CCL 3.3.3a 'configure' script that causes the script to hang when executed on a Linux PC with a RHEL 2.6.32-696.23.1.el6.x86_64 kernel. I don't have permission to open a bug ticket, so I'm posting it here. Adding one character fixes the problem. < { < cat <<_ASUNAME -- > { > cat <<\_ASUNAME I'm not a automake expert, so I don't know if the automake environment simply needs to be regenerated on a newer platform to correct this bug or if the fix needs to...
Hi Alexander, Looking at the excerpt you posted, it looks syntactically correct to me. Are you using HEMU 3.3.3 or an earlier version? The sample 'Views.def' file included with HEMU 3.3.3 includes a component for View 0: Front and is shown in the Components tab when selected in the Views tree list. Can you upload the complete 'Views.def' file you are using?
Can you explain in more detail why you believe CIGI 4.0 prevents on-the-fly entity creation? The only significant difference between CIGI 3.x vs. 4.0 regarding entity creation was the split of the Entity Control packet into a smaller Entity Control packet for entity creation and infrequent control parameters and the new Entity Position packet for the frame-by-frame entity position updates. CIGI 4.0 also adds entity Animation Control, Velocity Control, & Acceleration Control packets. If you want to...
I have two HEMU 3.3.2 scripts that are essentially identical except for the lat/lon/alt...