At present I use a personal TCPIP virtualdevice base on the virtualdevice (chai3d 2.0) compile on 32bits and 64bits windows plateform (with embarcadero XE7 C++ builder) for a wifi training simulation.
1) Why there is no virtualdevice in chai3d 3.1.1 ?
2) My virtualdevice seem doesn't work with chai3d 3.1.1 simulations, why it doesn't work?
3) Is the mapfile system different?
4) Is the virtualdevice (chai3d 2.0) not compatible with chai3d 3.1.1?
5) Is there a solution to make it compatible?
Thank you very much for your possible answers
The virtual will become available again by the end of this month. Please keep an eye of the forum.
The old virtual device application is no longer supported (CHAI3D 3.0 and higher) as it needed to be entirely redesigned to run on all operating systems.
Why the old virtualdevice doesn't work with the chai3d 3.1.1 version?
Are the mechanism to simulate a virtualdevice very differents? Or only the map file adress is different?
I looked the new examples for 3D animations and the open device mechanisms seems the sames in 2.0 or 3.1.1
3.1.1 version 2.0 version
cHapticDeviceHandler* handler; cHapticDeviceHandler* handler;
cGenericHapticDevicePtr hapticDevice; cGenericHapticDevice* newHapticDevice;
handler = new cHapticDeviceHandler(); handler = new cHapticDeviceHandler();
handler->getDevice(hapticDevice, 0); handler->getDevice(newHapticDevice, 0);
for my virtualdevice develop under embarcadero XE7 in 32 or 64 bits (with minors changes)
hMapFile = CreateFileMapping((HANDLE)0xFFFFFFFF,
NULL, // Default security.
PAGE_READWRITE | SEC_COMMIT, // Read/write permission.
0, // Max. object size.
1024, // Size of hFile.
"dhdVirtual"); // Name of mapping object.
lpMapAddress = MapViewOfFile(hMapFile,FILE_MAP_ALL_ACCESS,0,0,0);
pDevice = (TVirtualDelta*)lpMapAddress;
I don't anderstand where is the new way to detect the virtual device in the 3D animation?
Could you help me please to solve my problem?
The virtual device was removed from CHAI3D 3.x as a new virtual device that uses the Force Dimension interface will be available very shortly. The new virtual device will be multi-platform and will offer additional capabilities for simulation real haptic devices.
If you are in urgent need of using the old virtual device, you would just need to include files CVirtualDevice.h and CVirtualDevice.cpp in the CHAI3D 3.1 project, with possibly a few updates (see files CMyCustomDevice.h/.cpp for more information). You would also need to list it in the CHapticDeviceHandler.cpp file as it was the case in the CHAI3D 2.0 version.
We will keep you updated as the new virtual device becomes available.
With some delay, it is two months that my virtual peripheral works properly with your informations, thank you again for your great reactivity. Just a new question, where are you in the development of new virtual peripheral multiplatform for chaid 3.1.1?
In February 2016 you said me that a new virtual peripheral multiplatform device will coming soon...
Have you advanced on new virtual peripheral multiplatform for chaid 3.1.1 development?
Will the graphic interface always developed in borland c++, or in visualstudio?
Mine works perfectly with a borland c++ interface, but I would like to migrate to a VisualStudio C++ interface now, have you got some works in this way.
Thanks for reply.