Recent Posts

Pages: 1 2 [3] 4 5 ... 10
GeeXLab - english forum / Luajit for Linux
« Last post by stakov999 on March 08, 2018, 06:37:29 PM »
Hello all,

Did anyone tried to run GeexLab (specially Imgui functions) with luajit rather than lua5.3 ?
Is it even possible ?

Thank you in advance
Best regards

Radeon Software Adrenalin Edition 18.2.3 Highlights
Support For
    • Vulkan®1.1 Support
      • Product is conformant with the Vulkan® 1.1 Specification. Vulkan and the Vulkan logo are registered trademarks of the Khronos Group Inc.
    • Sea of Thieves™
      • Up to 29% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon™ RX Vega 64 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 3840x2160. RS-215
      • Up to 39% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon™ RX 580 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 1920x1080. RS-216
    • Final Fantasy® XII The Zodiac Age
    • Up to 13% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon™ RX Vega 56 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 2560x1440. RS-212
    • Up to 20% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon™ RX 580 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 2560x1440p. RS-213
Fixed Issues
  • Radeon FreeSync may intermittently incorrectly engage during Chrome video playback resulting in playback flicker.
  • Radeon FreeSync may rapidly change between min and max range when enabled causing stutter in fullscreen games on multi display system configurations.
  • Flickering may be observed on the performance metrics overlay when Enhanced Sync is enabled on some Radeon FreeSync connected displays.
  • Radeon Overlay may exhibit minor flickering when enabled while playing games using the Vulkan® API.
  • Fortnite™ may experience lighting or fog corruption on some graphics quality presets.
  • Radeon ReLive instant replay clips may intermittently contain small amounts of audio distortion.
  • Middle-earth™: Shadow of War™ may experience an application crash when launched as a Universal Windows® Application.
  • For Honor™ may experience an intermittent application crash on launch.
Radeon™ Software for Linux® Driver 17.50 Highlights
    • Enables Vulkan® 1.1 support
      • Closed source driver conformant with the Vulkan® 1.1 Specification
      • Open source driver is based on the Vulkan® 1.1 Specification and will be submitted to the Khronos Conformance Process. Current conformance status can be found at
    • Delivers amdgpu-pro and amdgpu-all-open stacks using the same packaging infrastructure
    • Large Page Support is enabled by default
General Discussion / Re: Adafruit RGB Matrix HAT + RTC for Raspberry Pi
« Last post by JeGX on March 08, 2018, 02:06:50 PM »
The RGB matrix HAT works fine with LED panels with the HUB75 interface. Are you sure you have a HUB75 panel ? Maybe you have a HUB12 panel (see here).
3D-Tech News Around The Web / Vulkan API specifications 1.1.70 released
« Last post by JeGX on March 08, 2018, 12:27:17 PM »
Change log for March 7, 2018 Vulkan 1.1.70 spec update:

  * Vulkan 1.1 initial release. Bump API patch number and header version
    number to 70 for this update. The patch number will be used for both
    Vulkan 1.1 and Vulkan 1.0 updates, and continues to increment
    continuously from the previous Vulkan 1.0.69 update.

    NOTE: We are not publishing an updated 1.0.70 specification, or 1.1
    reference pages, along with 1.1.70. There are still minor issues to work
    out with those build targets. However, we will soon generate all three
    types of documents as part of the regular spec update cycle.

    NOTE: The GitHub KhronosGroup/Vulkan-Docs repository now maintains the
    current specification in the `master` branch. The `1.0` branch is out of
    date and will not be maintained, since we will be generating both 1.1
    and 1.0 specifications from the `master` branch in the future.

Github Issues:

  * Clarify how mapped memory ranges are flushed in
    flink:vkFlushMappedMemoryRanges (public issue 127).
  * Specify that <<synchronization-pipeline-stages, Pipeline Stages>> are a
    list of tasks that each command performs, rather than necessarily being
    discrete pieces of hardware that one task flows through. Add a
    "`synchronization command`" pipeline type which all synchronization
    command execute (it's just TOP + BOTTOM), with an explanatory note
    (public issue 554).

Internal Issues:

  * Regenerate all images used in the spec in Inkscape with a consistent
    look-and-feel, and adjust image size attributes so they're all legible,
    and not too large with respect to the spec body text (internal issue
  * Document in the <<extensions,extensions>> appendix and in the style
    guide that `KHX` extensions are no longer supported or used in the
    Vulkan 1.1 timeframe (internal issue 714).
  * Remove the leftover equations_temp directory after PDF build completes
    (internal issue 925).
  * Update the <<credits, Credits (Informative)>> appendix to include
    contributors to Vulkan 1.1, and to list them according to the API
    version(s) they contributed to (internal issue 987).
  * Add a NOTE to the introduction explaining that interfaces defined by
    extensions which were promoted to Vulkan 1.1 are now expressed as
    aliases of the Vulkan 1.1 type (internal issue 991).
  * Instrument spec source conditionals so spec can be built with 1.1
    features, extensions promoted to 1.1, or both (internal issues 992,
  * Modify the XML schema and tools to support explicit aliasing of types,
    structures, and commands, and use this to express the promotion of 1.0
    extensions to 1.1 core features, by making the extension interfaces
    aliases of the core features they were promoted to. Mark up promoted
    interfaces to allow still generating 1.0 + extension specifications
    (internal issue 991).
  * Platform names, along with corresponding preprocessor symbols to enable
    extensions specific to those platforms, are now reserved in vk.xml using
    the <platform> tag. Update the registry schema and schema specification
    to match (internal issue 1011).
  * Updated the <<textures-texel-replacement, Texel Replacement>> section to
    clarify that reads from invalid texels for image resources result in
    undefined values (internal issue 1014).
  * Modify description of patch version so it continues to increment across
    minor version changes (internal issue 1033).
  * Clarify and unify language describing physical device-level core and
    extension functionality in the <<fundamentals-validusage-extensions,
    Valid Usage for Extensions>>, <<fundamentals-validusage-versions, Valid
    Usage for Newer Core Versions>>, <<initialization-functionpointers
    Command Function Pointers>>, <<initialization-phys-dev-extensions,
    Extending Physical Device From Device Extensions>>
    <<extended-functionality-instance-extensions-and-devices, Instance
    Extensions and Device Extensions>> sections and for
    flink:vkGetPhysicalDeviceImageFormatProperties2. This documents that
    instance-level functionality is tied to the loader, and independent of
    the ICD; physical device-level functionality is tied to the ICD, and
    associated with device extensions; physical devices are treated more
    uniformly between core and extensions; and instance and physical
    versions can be different (internal issue 1048).
  * Updated the <<commandbuffers-lifecycle, Command Buffer Lifecycle>>
    section to clarify the ability for pending command buffers to transition
    to the invalid state after submission, and add a command buffer
    lifecycle diagram (internal issue 1050).
  * Clarify that some flink:VkDescriptorUpdateTemplateCreateInfo parameters
    are ignored when push descriptors are not supported (internal issue
  * Specify that flink:vkCreateImage will return an error if the image is
    too large, in a NOTE in the slink:VkImageFormatProperties description
    (internal issue 1078).
  * Remove near-duplicate NOTEs about when to query function pointers
    dynamically in the <<initialization, Initialization>> chapter and
    replace by extending the NOTE in the <<fundamentals-abi, Application
    Binary Interface>> section (internal issue 1085).
  * Restore missing references to "`Sparse Resource Features`" in the
    flink:VkBufferCreateFlagBits description (internal issue 1086).
  * Tidy up definitions of descriptor types in the `GL_KHR_vulkan_glsl`
    specification, the <<descriptorsets, Resource Descriptors>> section and
    its subsections, and the <<interfaces-resources-descset, Descriptor Set
    Interface>> for consistency, reduction of duplicate information, and
    removal of GLSL correspondance/examples (internal issue 1090).
  * Correctly describe code:PrimitiveId as an Input for tessellation control
    and evaluation shaders, not an Output (internal issue 1109).
  * Relax the requirements on chroma offsets for nearest filtering in
    <<textures-implict-reconstruction, Implicit Reconstruction>> (internal
    issue 1116).

Other Issues:

  * Clarify the intended relationship between specification language and
    certain terms defined in the Khronos Intellectual Property Rights
    policy. Specific changes include:
  ** Rewrote IP/Copyright preamble and introduction to better agree with
     normative language both as laid out in the introduction, and the
     Khronos IPR policy.
  ** Added notion of fully informative sections, which are now tagged with
     "`(Informative)`" in their titles.
  ** Removed non-normative uses of the phrase "`not required`"
  ** Clarified the distinction between terms "`optional`" and "`not
     required:`" as they relate to the IPR Policy, and updated specification
     text to use terms consistent with the intent.
  ** Reduced additions to RFC 2119, and ensured the specification agreed
     with the leaner language.
  ** Removed the terms "`hardware`", "`software`", "`CPU`", and "`GPU`" from
     normative text.
  ** Moved several paragraphs that should not have been normative to
     informative notes.
  ** Clarified a number of definitions in the Glossary.
  ** Updated the document writing guide to match new terminology changes.
  * Explicitly state in the <<fundamentals-objectmodel-lifetime-acquire,
    application memory lifetime>> language that that for objects other than
    descriptor sets, a slink:VkDescriptorSetLayout object used in the
    creation of another object (such as slink:VkPipelineLayout or
    slink:VkDescriptorUpdateTemplateKHR) is only in use during the creation
    of that object and can be safely destroyed afterwards.
  * Updated the <<textures-scale-factor, Scale Factor Operation>> section to
    use the ratio of anisotropy, rather than the integer sample rate, to
    perform the LOD calculation. The spec still allows use of the sample
    rate as the value used to calculate the LOD, but no longer requires it.
  * Update `vulkan_ext.c` to include all platform-related definitions from
    the Vulkan platform headers, following the split of the headers into
    platform-specific and non-platform-specific files.
  * Fix bogus anchor name in the <<commandbuffers, Command Buffers>> chapter
    which accidentally duplicated an anchor in the pipelines chapter. There
    were no reference to this anchor, fortunately.
  * Add valid usage statement for slink:VkWriteDescriptorSet and
    slink:VkCopyDescriptorSet requiring that the slink:VkDescriptorSetLayout
    used to allocate the source and destination sets must not have been
    destroyed at the time flink:vkUpdateDescriptorSets is called.
  * Document mapping of subgroup barrier functions to SPIR-V, and clarify a
    place where subgroupBarrier sounds like it's execution-only in the
    standalone `GL_KHR_shader_subgroup` specification.
  * Use an HTML stylesheet derived from the Asciidoctor `colony` theme, with
    the default Arial font family replaced by the sans-serif Noto font
  * Numerous minor updates to README.adoc, build scripts, Makefiles, and
    registry and style guide specifications to support Vulkan 1.1 outputs,
    use them as defaults, and remove mention of `KHX` extensions, which are
    no longer supported.

New Extensions:

  * `VK_EXT_vertex_attrib_divisor`

General Discussion / Adafruit RGB Matrix HAT + RTC for Raspberry Pi
« Last post by deba on March 08, 2018, 08:34:26 AM »

Hi All,
I purchased a Adafruit RGB Matrix HAT + RTC and mounted it on my Ras Pi 3 .I followed all the steps mentioned in the link when I try to run my code ,I dont see the desired result.I just see few lines of leds lit.I dont know what i'm doing wrong.
I ordered the LED board from

Could it be that the HAT is not compatible with this LED board?

This article discusses TSCMAA, which employs an optimized CMAA and integrates temporal accumulation in order to create a temporally stable post-processing AA solution as a MSAA alternate technique without compromising on image quality. TSCMAA is also designed to run efficiently on low- and medium-end graphics processing units (GPUs), such as integrated GPUs, and to be minimally invasive. This makes it acceptable as an MSAA alternate with better temporal stability in a wide range of applications, which include aliasing-prune geometry such as text, patterns, lines, and foliage.
3D-Tech News Around The Web / New SDK released for Vulkan 1.1
« Last post by Stefan on March 07, 2018, 06:00:06 PM »
New SDK released for Vulkan 1.1! ####Released 3/7/2018####
This Linux/Windows SDK supports Vulkan API revision 1.1.70. The prior Linux/Windows LunarG SDK release supported Vulkan API revision 1.0.68.
Please note --- this new SDK supports Vulkan 1.1.70, and is backward-compatible with Vulkan 1.0.70.
Please refer to the detailed release notes for driver and CMake requirements.
###Overview of new features in SDK 1.1.70###
  • Support for Vulkan Version 1.1.x, the first major Vulkan update
  • The VulkanInfo utility now features a json backend, for use with the device simulation layer
  • New extensions for Vulkan 1.1.70:
    • VK_KHR_maintenance3
    • VK_EXT_vertex_attribute_divisor
  • Many bug fixes, validation coverage and accuracy improvements, and many feature additions
###Extensions now promoted from experimental or vendor extensions to Khronos extensions###
  • VK_KHR_multiview  (formerly VK_KHX_multiview)
  • VK_KHR_device_group  (formerly VK_KHX_device_group)
  • VK_KHR_device_group_creation  (formerly VK_KHX_device_group_creation)
  • VK_KHR_external_memory_capabilities (formerly   VK_NV_external_memory_capabilities)
  • VK_KHR_external_memory  (formerly VK_NV_external_memory)
###Vulkan 1.0 extensions now promoted to core ###
  • VK_KHR_multiview
  • VK_KHR_device_group
  • VK_KHR_device_group_creation
  • VK_KHR_bind_memory_2
  • VK_KHR_descriptor_update_template
  • VK_KHR_sampler_ycbcr_conversion
  • VK_KHR_get_memory_requirements_2
  • VK_KHR_maintenance3
  • VK_KHR_external_memory_capabilities
  • VK_KHR_external_fence_capabilities
  • VK_KHR_external_semaphore_capabilities
  • VK_KHR_get_physical_device_properties_2
  • VK_KHR_maintenance1
  • VK_KHR_external_memory
  • VK_KHR_external_semaphore
  • VK_KHR_16bit_storage
  • VK_KHR_external_fence
  • VK_KHR_maintenance2
  • VK_KHR_variable_pointers
  • VK_KHR_dedicated_allocation
###Additional extension considerations###
  • All KHX extensions have been promoted to KHR extensions
  • The KHX versions of these extensions are no longer supported
###More information###
Please read the Release Notes for Linux or Release Notes for Windows on LunarXchange in the Docs section for more details.
Download the SDK here.
For more information about LunarG, please check out our website.
3D-Tech News Around The Web / NVIDIA Vulkan developer driver 389.10
« Last post by Stefan on March 07, 2018, 05:32:44 PM »
  Windows driver version 389.10 and Linux driver version 387.42.05 provide new features for Vulkan developers to test their upcoming Vulkan applications.
 Windows 389.10
   Linux 387.42.05
   Release Updates   March 7th, 2018 - Windows 389.10, Linux 387.42.05
3D-Tech News Around The Web / (WebGL) Caffeine path tracing demo + tutorial
« Last post by JeGX on March 06, 2018, 07:13:01 PM »
Path tracing is a powerful, surprisingly simple, and woefully expensive rendering technique. In this tutorial, I’ll be walking you through the construction of the Caffeine demo, which implements realtime path tracing in WebGL.

- Caffeine path tracing tutorial
- Caffeine path tracing demo
- Caffeine path tracing source code

Pages: 1 2 [3] 4 5 ... 10