Scolring - Forum

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.

Pages: 1

#1 Openspace3D » Google Play's target API level requirement » 17-Jul-2019 22:07:52

jasolo
Replies: 12

From https://developer.android.com/distribut … t-sdk.html :
When you upload an APK, it needs to meet Google Play’s target API level requirements. Starting August 1, 2019, Google Play requires that new apps target at least Android 9.0 (API level 28), and that app updates target Android 9.0 from November 1, 2019. Until these dates, new apps and app updates must target at least Android 8.0 (API level 26).

I have created an APK for arm64 with Openspace3D 1.80 and after the upload Google Play says my app targets API level 26. Can I target level 28? Maybe with a future update of the Android plugin?

Other problem with my AR app is the size of the APK using the Default option. It seems to contain the 32 and 64 bits versions, so the size is greater than 100 MB and Google Play does not accept the APK. I have to create both versions separately (arm32 and arm64). That is the solution?

#2 Re: Showcase » TenteExpo 2017 » 2-Jun-2017 07:36:45

jasolo
arkeon wrote:

Do you have a facebook post we can share ?

There is no facebook post, I just shared the Play Store link in the facebook page of the fans' group: https://www.facebook.com/tenteros.land/

#3 Showcase » TenteExpo 2017 » 1-Jun-2017 23:43:39

jasolo
Replies: 4

I have created an app of Augmented Reality for the TENTE Expo 2017:
https://play.google.com/store/apps/deta … teexpo2017
tenteexpo2017qr.png unnamed.png

tenteexpo-20170518_230047.jpg tenteexpo-20170518_230113.jpg tenteexpo-20170518_230229.jpg tenteexpo-20170518_230301.jpg tenteexpo-20170518_230331.jpg tenteexpo-20170518_231243.jpg tenteexpo-20170518_232530.jpg tenteexpo-20170518_232537.jpg tenteexpo-20170518_232640.jpg tenteexpo-20170518_232737.jpg

TENTE is a discontinued spanish construction game similar to Lego but incompatible (not a clone). In the 80's it was more popular than Lego in Spain, but the factory broke in the 90's because of the crisis and bad decisions. Another company bought the game, but a decade without new models has passed. TENTE was also distributed in France, Italy, Germany, Mexico, Brazil, USA (Hasbro) and Japan (Nomura Toys).

Since 2012 a group of fans organize an annual exhibition in Spain with original and custom models, and posters. For many of these expos I have created an augmented reality app for Android. Previously using Unity + Vuforia, but after Vuforia changed its license, I looked for alternatives and found OpenSpace3D. big_smile For this app, I have modified the ARCards demo. The 3D models, most of them animated, were designed by fans using 3D bricks instead of the real ones (we have adapted to TENTE the LDraw software originally made for Lego). Many of the posters at the expo have a model whose photo is the marker required by the app, including the main poster.

Thanks to arkeon for answering my questions during the development of this app. wink

#4 Re: Openspace3D » Date format of Screenshot PlugIT » 14-May-2017 15:21:52

jasolo

OK. Another question about the screenshots. The orientation of my android app is landscape and all the captured images are also landscape. But people could take a shot in portrait and then they'll see the image is rotated (landscape instead of portrait). I suppose the solution is to use the Orientation sensor plugit whose Z value is (-45, 45) in landscape, (-135, -45) in portrait and so on. But I don't know what element to change with that info ¿the active camera?

#5 Re: Openspace3D » Date format of Screenshot PlugIT » 14-May-2017 11:47:35

jasolo

The last solution works, but I don't want two pictures. I'm back to my original question, when the ".png.jpg" trick creates a jpg with 75% quality. I don't know what function is the responsible, but maybe it has the quality as parameter and it's called with the 75 value or the default value is 75. In that case I would want to change it to 90 or 95 (good quality for jpg and smaller size than png).

#6 Re: Openspace3D » Date format of Screenshot PlugIT » 13-May-2017 22:09:22

jasolo

I'm trying first in Windows but I've also tried with Android. Using _BTSAVEbitmap gives also a png.

The code after all these changes, in case I've made some mistake:

fun cbTakeShot(inst, from, action, param, rep, p) =
  let V3DgetSessionView c3dXsession -> viewstr in
  let p -> [filePrefix only3d] in
  let (localtime time) -> [seconds minutes hours day month year wd yd] in
  let strcatn filePrefix::(itoa year)::(if month<10 then "0" else "")::(itoa month)::(if day<10 then "0" else "")::(itoa day)::"_"::(if hours<10 then "0" else "")::(itoa hours)::(if minutes<10 then "0" else "")::(itoa minutes)::(if seconds<10 then "0" else "")::(itoa seconds)::(if only3d then ".png" else ".jpg")::nil -> file in
  (
    if (only3d) then 
    (
	  if (SO3BufferWriteContent viewstr.V3D_buffer (_getmodifypack file)) == nil then nil else
      (
        let _LDalphaBitmap _channel (_checkpack file) -> abmp in
        let _GETalphaBitmaps abmp -> [bmp alpha] in
        (
          _BTSAVEbitmap bmp (_getmodifypack (strcat file ".jpg")); // jpg 95%
        
          //delete png file
          _deletepack (_checkpack file);
          
          //free loaded bmp
          _DSalphaBitmap abmp;
        );
        SendPluginEvent inst "Saved" file nil;
      );      0;
    )
    else
    (
      let _GETscreenSize -> [sw sh] in
      let _FILLbitmap _CRbitmap _channel sw sh 0x0 -> bmp in
      let _CAPTUREscreen bmp 0 0 sw sh 0 -> bmp in
      (
        _SAVEjpeg bmp _getmodifypack file 75;
        _DSbitmap bmp;
        SendPluginEvent inst "Saved" file nil;
      );
      0;
    );
  ); 
  0;;

#7 Re: Openspace3D » Date format of Screenshot PlugIT » 13-May-2017 20:22:26

jasolo

I've replaced the original code

if (SO3BufferWriteContent viewstr.V3D_buffer (_getmodifypack file)) == nil then nil else
        SendPluginEvent inst "Saved" file nil;

with yours but it doesn't work. When the extension code is the original

if only3d then ".png" else ".jpg"

the result is a png. And with the trick ".png.jpg" a jpg 75% quality is created. It's the same as before. sad

#8 Re: Openspace3D » Date format of Screenshot PlugIT » 13-May-2017 17:51:47

jasolo

Well, the problem of the android viewers with the pngs was due to the path of the file prefix: "%pictures%/screenshots/myprefix". Just reducing to one folder "%pictures%/myprefix" solves the problem. Anyway I would prefer jpgs with higher quality instead of pngs because of the smaller size.

#9 Re: Openspace3D » Date format of Screenshot PlugIT » 13-May-2017 17:36:08

jasolo

Good to know the function alternative, iri.

I've found that the files saved as ".png.jpg" are jpgs with 75% quality, not pngs. yikes I've read in this forum that png was used because 3D is RGBA, I think, but it seems that the program uses the format indicated in the extension. Any possibility to change  by code the quality used to save jpgs?

#10 Re: Openspace3D » Date format of Screenshot PlugIT » 13-May-2017 10:49:14

jasolo

My app have to be finished in less than two weeks so I have modified the code of the Screenshot PlugIT. In cscreenshot.pkg I've replaced the line:

let strcatn filePrefix::(strtrim strreplace (strreplace (ctime time) " " "_") ":" "-")::(if only3d then ".png" else ".jpg")::nil -> file in

by these ones:

let (localtime time) -> [seconds minutes hours day month year wd yd] in
let strcatn filePrefix::(itoa year)::(if month<10 then "0" else "")::(itoa month)::(if day<10 then "0" else "")::(itoa day)::"_"::(if hours<10 then "0" else "")::(itoa hours)::(if minutes<10 then "0" else "")::(itoa minutes)::(if seconds<10 then "0" else "")::(itoa seconds)::(if only3d then ".png.jpg" else ".jpg")::nil -> file in

It's my first time with Scol code, so surely there is a better code to do the same. I have also changed the extension string ".png" to ".png.jpg" because many Android galleries don't detect PNGs but they are capable of showing them with the jpg extension (I don't know the reason, but it works).

#11 Openspace3D » Date format of Screenshot PlugIT » 1-May-2017 15:22:34

jasolo
Replies: 19

The file name of the image saved with the Screenshot PlugIT is "mon_may_01_15-55-10_2017" when the date is "Monday May 1, 2017 15:55:10". I would prefer "20170401_155510", shorter and better for sorting. Can I use another date format?

#12 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 15-Apr-2017 22:33:42

jasolo

Sorry, I didn't notice your last post until now. Meanwhile I split the model in parts and a new problem appeared: the model showed no colour, although it has coloured faces (no problem in Windows or Android). The solution was to use a texture. hmm It runs smoothly in the RPi3 with all the parts adding a total of 58k vertices.

For your test, this is an old version of the mesh with near 89k vertices: https://www.dropbox.com/s/vblm8bb6dbeul … o.zip?dl=1

It is a mesh from a LDraw model, after removing many of the internal faces. The fact of being virtual bricks results on unoptimized meshes.

#13 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 9-Apr-2017 16:50:08

jasolo

I can try to separate my model in several models and show them with the same marker. Or decreasing the number of vertices is the only option?

#14 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 9-Apr-2017 12:24:57

jasolo

I've made a simple app, but again I get a white screen (only in Raspberry, in Windows works). The last lines of the log at the console:

Creating resource group 0.mainScene
Added resource location '/usr/share/prueba/partition/' of type 'ScolFileSystem' to resource group '0.mainScene'
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
Creating resource group 0.main8.castillomota
Added resource location '/usr/share/prueba/partition/' of type 'ScolFileSystem' to resource group '0.main8.castillomota'
Mesh: Loading /usr/share/prueba/partition/prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh.

Creating resource group 0.mainScene
Added resource location '/usr/share/prueba/partition/' of type 'ScolFileSystem' to resource group '0.mainScene'
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
SO3 EXCEPTION(SExceptionInvalidParameters): SSAO technique, not supported by the graphic card! in SSsaoHandler::SeTechniqueParameterValue at /home/pi/Documents/scol-svn/scol/plugins/so3engine/src/SO3Renderer/SO3SsaoHandler.cpp (line 2521)
Creating resource group 0.main8.castillomota
Added resource location '/usr/share/prueba/partition/' of type 'ScolFileSystem' to resource group '0.main8.castillomota'
Mesh: Loading /usr/share/prueba/partition/prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh.

I also activated the log file in usm.ini. It shows the same SO3 exception and the message "Error while setting SSAO parameter!". The log when loading the 3d model is:

Sat Apr  8 22:23:19 201 : Creating resource group 0.main8.castillomota

Sat Apr  8 22:23:19 201 : Added resource location '/usr/share/prueba/partition/' of type 'ScolFileSystem' to resource group '0.main8.castillomota'

Sat Apr  8 22:23:19 201 : USING : scol_fopen : /usr/share/prueba/partition/prueba/castillomota/materials/castillomota.material

Sat Apr  8 22:23:19 201 : /usr/share/prueba/partition/ - prueba/castillomota/materials/castillomota.material - /usr/share/prueba/partition/prueba/castillomota/materials/castillomota.material

Sat Apr  8 22:23:19 201 : >>> Open archive : /usr/share/prueba/partition/prueba/castillomota/materials/castillomota.material

Sat Apr  8 22:23:19 201 : >>> Open archive : /usr/share/prueba/partition/prueba/castillomota/materials/castillomota.material

Sat Apr  8 22:23:19 201 : >>> Open archive : /usr/share/prueba/partition/prueba/castillomota/materials/castillomota.material

Sat Apr  8 22:23:19 201 : >>> Open archive : /usr/share/prueba/partition/prueba/castillomota/materials/castillomota.material

Sat Apr  8 22:23:19 201 : USING : scol_fopen : /usr/share/prueba/partition/prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh

Sat Apr  8 22:23:19 201 : /usr/share/prueba/partition/ - prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh - /usr/share/prueba/partition/prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh

Sat Apr  8 22:23:19 201 : Mesh: Loading /usr/share/prueba/partition/prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh.

Sat Apr  8 22:23:19 201 : >>> Open archive : /usr/share/prueba/partition/prueba/castillomota/meshes/castillomota_castillo_cartillo_mota-tan2.mesh

Sat Apr  8 22:23:19 201 : OGRE EXCEPTION(7:InternalErrorException): 32 bit hardware buffers are not allowed in OpenGL ES. in GLES2HardwareIndexBuffer at /home/pi/Documents/scol-svn/dependencies/Ogre/Sources/RenderSystems/GLES2/src/OgreGLES2HardwareIndexBuffer.cpp (line 50)

Sat Apr  8 22:23:19 201 : OGRE EXCEPTION(7:InternalErrorException): 32 bit hardware buffers are not allowed in OpenGL ES. in GLES2HardwareIndexBuffer at /home/pi/Documents/scol-svn/dependencies/Ogre/Sources/RenderSystems/GLES2/src/OgreGLES2HardwareIndexBuffer.cpp (line 50)

Sat Apr  8 22:23:19 201 : An exception has occurred: OGRE EXCEPTION(7:InternalErrorException): 32 bit hardware buffers are not allowed in OpenGL ES. in GLES2HardwareIndexBuffer at /home/pi/Documents/scol-svn/dependencies/Ogre/Sources/RenderSystems/GLES2/src/OgreGLES2HardwareIndexBuffer.cpp (line 50)

arkeon wrote:

second check is to make sure your model have a correct material

I'm not sure how to check it. The 3D model is an OBJ exported from Blender with the default parameters. It only has face colours.

#15 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 6-Apr-2017 22:49:49

jasolo

The original ar-cards demo works with 256 MB. smile Also my modification but only the models from the demo, so now the problem seems to be the 65536 vertices limit. The log shows no warning about that and it's near identical to the ar-cards log. The first difference is:

Mesh: Loading /usr/share/PROGRAM-NAME/partition/assets/models/converted/MY-MODEL/meshes/castillomota_castillo_cartillo_mota-tan2.mesh.

Once running there are several lines like this:

Page[3]  pre: 40, aft: 40, error = 1,051564

And I think the next line appears when the marker of my model is detected, but the program doesn't show my mesh:

Material scheme converted from Default to ShaderGeneratorDefaultScheme on material : ASSET/TransShadow with group : 0.main82.trex

I replaced the trex with my mesh, so some names maintain the "trex". My mesh doesn't have textures, only colours.

For comparison, when the Andy marker is detected and Andy appears:

Material scheme converted from Default to ShaderGeneratorDefaultScheme on material : ASSET/TransShadow with group : 0.main12.andy
Material scheme switch from Default to ShaderGeneratorDefaultScheme on material : andyv2_Robot_material
Material scheme switch from Default to ShaderGeneratorDefaultScheme on material : andyv2_mass
Material scheme switch from Default to ShaderGeneratorDefaultScheme on material : andyv2_Material_shell
glGetError 0x506
GLSL ES compiled: andyv2_vsLightGENNORM0_GLSLES
Compiled
GLSL ES compiled: andyv2_fpLightGENDIFF0SPEC0NORM0_GLSLES
Compiled
glGetError 0x506
GLSL ES compiled: andyv2_fpLightGENAMB0DIFF0NORM0_GLSLES
Compiled
glGetError 0x506
GLSL ES compiled: andyv2_fpLightGENDIFF0SPEC0NORM0FresnelREFMSK_GLSLES
Compiled

#16 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 5-Apr-2017 20:15:50

jasolo

After replacing those files, ar-piano works in the raspberry. smile But not my modification of arcards. After the initial logo, the screen is white. It works in Windows. In my modification I've removed all the blocks except trex, pterodactylus, andy and drawfish, and replaced the mesh of trex with an OBJ with 100k faces and 65k vertices. So maybe this mesh is excesive or I should increase the memory of the RP3 dedicated to GPU.

#17 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 3-Apr-2017 19:24:20

jasolo

My version is 8.0 jessie. Same error after enabling I2C and SPI, rebooting and upgrading the raspberry.

#18 Re: Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 3-Apr-2017 12:18:08

jasolo

Although now I'm not near the raspberry, I'm sure that the camera option is enabled but the others are disabled (I2C, spi). I'll enable them and use a screen. I suppose my system has the last version (updated a couple of days ago), but I'll check it.

#19 Openspace3D » Problem trying to execute examples in Raspberry Pi 3 Model B » 2-Apr-2017 23:55:46

jasolo
Replies: 17

I want to create an Augmented Reality app for Raspberry and Android. By the moment I'm modifying the "arcards" demo and the first test on Android was OK, but failed on a Raspberry Pi 3 Model B with a Raspberry Pi Camera v2. I'm connected to the RPi through WiFi using Putty and XMing. I get the same error with the original example "ar_piano". The DEB package is created in the Raspberry as indicated in the readme.txt in the export folder. This is the text during the execution:

pi@raspberrypi:~ $ ar-piano
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Unable to query physical screen size, defaulting to 100 dpi.
To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
PuTTY X11 proxy: Unsupported authorisation protocol
xcb_connection_has_error() returned true
PuTTY X11 proxy: Unsupported authorisation protocol
xcb_connection_has_error() returned true
Creating resource group General
Creating resource group Internal
Creating resource group Autodetect
SceneManagerFactory for type 'DefaultSceneManager' registered.
Registering ResourceManager for type Material
Registering ResourceManager for type Mesh
Registering ResourceManager for type Skeleton
MovableObjectFactory for type 'ParticleSystem' registered.
ArchiveFactory for archive type FileSystem registered.
ArchiveFactory for archive type Zip registered.
ArchiveFactory for archive type EmbeddedZip registered.
DDS codec registering
FreeImage version: 3.15.3
This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See http://freeimage.sourceforge.net for details
Supported formats: bmp,ico,jpg,jif,jpeg,jpe,jng,koa,iff,lbm,mng,pbm,pbm,pcd,pcx,pgm,pgm,png,ppm,ppm,ras,tga,targa,tif,tiff,wap,wbmp,wbm,psd,cut,xbm,xpm,gif,hdr,g3,sgi,exr,j2k,j2c,jp2,pfm,pct,pict,pic
PVRTC codec registering
ETC codec registering
Registering ResourceManager for type HighLevelGpuProgram
Registering ResourceManager for type Compositor
MovableObjectFactory for type 'Entity' registered.
MovableObjectFactory for type 'Light' registered.
MovableObjectFactory for type 'BillboardSet' registered.
MovableObjectFactory for type 'ManualObject' registered.
MovableObjectFactory for type 'BillboardChain' registered.
MovableObjectFactory for type 'RibbonTrail' registered.
*-*-* OGRE Initialising
*-*-* Version 1.10.0unstable (Xalafu)
Creating resource group SO3/Internal/Widgets/BitmapWidget
Installing plugin: OpenGL ES 2.0 RenderSystem
OpenGL ES 2.x Rendering Subsystem created.
Plugin successfully installed
Installing plugin: ParticleFX
Particle Emitter Type 'Point' registered
Particle Emitter Type 'Box' registered
Particle Emitter Type 'Ellipsoid' registered
Particle Emitter Type 'Cylinder' registered
Particle Emitter Type 'Ring' registered
Particle Emitter Type 'HollowEllipsoid' registered
Particle Affector Type 'LinearForce' registered
Particle Affector Type 'ColourFader' registered
Particle Affector Type 'ColourFader2' registered
Particle Affector Type 'ColourImage' registered
Particle Affector Type 'ColourInterpolator' registered
Particle Affector Type 'Scaler' registered
Particle Affector Type 'Rotator' registered
Particle Affector Type 'DirectionRandomiser' registered
Particle Affector Type 'DeflectorPlane' registered
Plugin successfully installed
Installing plugin: Octree Scene Manager
Plugin successfully installed
ArchiveFactory for archive type ScolFileSystem registered.
ArchiveFactory for archive type ScolURL registered.
CPU Identifier & Features
-------------------------
 *   CPU ID:
 *      VFP: no
 *     NEON: yes
-------------------------
Registering ResourceManager for type Texture
OverlayElementFactory for type Panel registered.
OverlayElementFactory for type BorderPanel registered.
OverlayElementFactory for type TextArea registered.
Registering ResourceManager for type Font
Unable to determine hardware version. I see: Hardware   : BCM2835
,
 - expecting BCM2708 or BCM2709.
If this is a genuine Raspberry Pi then please report this
to projects@drogon.net. If this is not a Raspberry Pi then you
are on your own as wiringPi is designed to support the
Raspberry Pi ONLY.
AL lib: (EE) alc_cleanup: 1 device not closed

The problem seems to be wiringPI not detecting the RPi3. The installed version is 2.44 and the command "gpio -v" shows the expected info. Also there are messages about putty. In a previous test with the RPi connected to a monitor, keyboard and mouse (no remote terminal) the screen got white after showing the initial logo and got frozen. Sorry, no available log from that test.

Pages: 1

Board footer

Powered by FluxBB