Entraides et échanges autour de la technologie Scol - Informations and exchanges on the Scol technology
Vous pouvez changer la langue de l'interface une fois inscrit - You can change the language once registered
You are not logged in.
Thank you for letting us know.
The next version of OpenSpace3D (which will hopefully release in a few weeks) will export application for API 28.
About the size of your application, the default export contains every version (x86, x86_64, armeabi-v7a and arm64-v8a), so it is indeed bigger. Creating both versions separately is a very good solution as it decreases the size of the application both for your upload and the final user that download it from the Play Store. The next version of OpenSpace3D will also feature the App Bundle export, that has a higher upload limit and let the Play Store automatically generates the smallest apk for the final user.
We do not use any of the tools you use nor use C#, everything we code is in C++, so I cannot help you about C#-specific libraries and tools.
For Android, we use the Native Development Kit (NDK) and CMake to compile our dependencies, then Android Studio with NDK and CMake to compile Scol.
About your second sentence, I'm sorry but I didn't understand what you meant. Do you mean you already have a way to do a windows to mac or mac to windows cross-compilation ?
If I remember correctly, there's Visual Studio Code (not the same thing as simply Visual Studio) that allows C# development on all
platforms, although I'm not sure if it is just a code editor or a fully-fledged IDE, and don't know the extent of its cross-compiling capabilities
From what we have been able to test so far, the problem seems to depend on specific device models (or maybe even specific devices). We tested OpensSpace3D on a wide array of Android version (ranging from 4.4 to 8.1), with or without dual cameras and with low as well as high processing power. As of today, it works fine on all of the devices we currently own, but it seems there are a few devices that still won't work. But as Arkeon said, we cannot debug without having the phone in our hands, and your devices are not among those we own.
Hello,
We do need a Mac too when compiling for OSX / iOS, so we cannot help you in this regard.
Even when you export an application from OpenSpace3D, you still need a Mac with Xcode and an Apple developer license to finalize the application
No, there's not really any support for arabic as of now in OpenSpace3D
There is not really any minimum or recommended specs for OpenSpace3D, as it mostly depends on the kind of application you are creating. The only real requirement is to have at least Android 4.4 Kitkat (might change in the future).
OpenSpace3D works fine even on entry-level smartphone, although the biggest applications ran at low FPS.
The performance needed from your device varies with the number of object in your scene, the number of polygons, the number and size of your textures, etc. Keep in mind that settings such as shadows can significantly slow your application down on lower-end devices.
You can already move 3d interfaces by moving their parent (although not the labels form the "labellist" plugIt since they have no parents), but it is true that most of the recents interface plugITs lack these functionnalities. I will add actions to these plugIts soon to change that.
A few plugITs such as the "textzone" and "button" can already be moved and resized at the moment.
Hello,
The "stats file" plugIt allows to generates a .csv file (located in Documents/OpenSpace3D/tmp/logs) containing stats about your application. You can provide the stats you want to track to the "stats file" plugIt via the actions named like the variables you set inside the plugIt.
I suppose the "New log" event is supposed to be triggered when a new line is added to the file, but I just discovered that it isn't working at the moment.
I will try to correct this and rewrite this plugIt's documentation to make it more helpful by the next release.
Having an exemple for every plugIt seems like a good idea, we just need the time to make them. Any help is welcome !
Thank you for your feedback !
Salut,
Pour ton idée de roue de la fortune, peut-être que tu peux appliquer une force de rotation aléatoire sur ta roue, et déterminer le résultat en fonction de l'angle de ta roue quand elle s'arrête (ou quand tu l'arrête de force après un timer).
Par exemple, si ta roue a 8 valeurs, et qu'une fois arrêtée, son angle est entre 0° et 45°, tu est tombé sur la première valeur, s'il est entre 45° et 90° tu est sur la deuxième valeur ... A ajuster en fonction de ton nombre de valeurs et de l'angle de départ de ta roue ![]()
Pour appliquer une force de rotation à un objet, regarde le plugIT "physic tools". Pour récupérer l'angle de ta roue, tu peux utiliser le plugIT "Object position" (fait juste attention car il te retournera l'angle sur les 3 axes, avec chaque angle compris entre -180° et 180°)
N'hésite pas à nous faire part de l'avancement du projet ! ![]()
Hello,
To see an exemple of game made with OpenSpace3D, you can look at the Aliencrash demo in the OpenSpace3D/demos/aliencrash folder.
For informations about the features of OpenSpace3D, you can read the online documentation here : http://www.openspace3d.com/documentation/en/
Note that you can also access the documentation of each plugIT directly with the question mark icon at the top right of each plugIT window.
You can also find video tutorials on our youtube channel, or buy the ebook that will guide you with several tutorials to learn all the core features of OpenSpace3D http://www.openspace3d.com/lang/en/buy- … enspace3d/
For the loading of levels, you must use the "instantiate" plugIT that will instantiate the new level. Here is the plugIT documentation http://www.openspace3d.com/documentatio … lugit.html and you can find it in use in the aliencrash demo.
If the cubes you want to position are objects of the scene, you can use an "object position" plugIT to retrieve the position of the first object, pass it through a "vector add" plugIT that add 1.5 on the X axis, then use a second "object position" plugIT to set the position of the second object
Should be fixed for the video, I set to private insted of unlisted by mistake, sorry ^^'
Hello cel
Is it what you were expecting for the measure plugIT ?
https://youtu.be/QaRQze6M01w
You can download the files to try it by yourself here. Just replace them in your installation of OpenSpace3D
http://redmine.scolring.org/projects/op … ls/measure
put the texture path ("assets/texture/mytexture.jpg") directly in the "value" field, not in the link parameter. Make a single link and let the link parameter empty.
As a general advice, you cannot refer to the variables from the link parameter in the plugITs, as I guess that this is what you were trying to do by putting 1, 2, 3 in the "value" field.
Also, you cannot assign value to link parameters as I saw in your first video with "1 = ...". If you have several parameters in your link and need to change just a few of them, here is an exemple : if my plugit sends a position (made of 3 parameters : x, y and z), and I want to set the y position to 6.4, I can write in the link parameter "$1 6.4 $3" so y is changed but x and z remains the same.
Hello
To do it this way, you only need one "change texture" plugIT. Put your textures' paths in the "value" field of each entry of your list, and create the link "Dialog List.Selected value -> change texture.change"
Another way to do it is to use the "Material list" plugIT that allows you to attach a list of materials to an object and features a built-in selection interface.
Hello,
About the Measure plugIT, it is possible, but you would need to set all the points of your measure at once. Would this solve your problem ?
Nothing is planned about integrating a new language in OpenSpace3D, but it seems unlikely, as it would probably require the creation of a full API. If you need help to use Scol, you can check the Redmine for tutorials and functions documentation [1] [2]. You can also check the source code of some PlugITs to see exemples of use.
We will probably add some new gui elements later, but feel free to submit any suggestion