All Activity

Scaling Percentage = New Dimension ÷ Original Dimension × 100% If result < 100% → Downscale If result > 100% → Upscale (add “+” sign) Examples: Downscale by height: (515÷720)×100%=71.52% Downscale by width: (1920÷2560)×100%=75% Upscale by width: (2560÷1920)×100%=+133.33% Upscale by height: (720÷515)×100%=+139.80% Try to use 2 decimal places consistently for all % values. I hope you understand my explanation.

Hi, Updated my config so updated my skin... here we go. 1280 x 800 2026-08-27.spzip

how did you arrive the percentage?

No worries, I can live with that, it has been like this for very long time now. Hope it doesn't started developing new issue because you know.... RAM is.... yeah... that... "a little pricing issues" Thanks for the help anyway

No, no, it’s okay! I thought I might have missed something and was looking in the wrong place. Thank you for clarifying 🙏 and for the example - it makes sense now. 🔥

Hi. It's easy. Click on the image on the panel screen, open the Manager, find your image, and click change. Then, at the very top, there are settings for how and what you want to change. If the image is an Image, in the panel, you enter the new path to the new image (folder on the disk), and if necessary, enter the size, and that's it.

Is its resource usage normal? A transparent background can consume 10% of the GPU, and OpenGL around 3%—unless the target framerate is set to 1.The one built into AIDA64, however, manages to have absolutely no impact on performance. Checking the OpenGL option the transparent background turns black. I need a transparent background to use with my wallpaper, but I don't want it to interfere with my gaming—what should I do?

I've sent you a private message about this.

I'm afraid AIDA64 won't be able to help you about this issue 😞 The SPD chip on your memory modules seem be unstable, no matter of the clock frequency.

Hello everyone, in previous versions it was easy to change the panel image, but now it's difficult. Could you please help me with how to change the image? Thank you.

Alright, I have turn off XMP, it's now running at 4800 MT/s, I never touch timing tuning, so no change there. The problem still persist. It's still disappear. I was about to say I'll report back after 1 month long term testing, we're not even making 2 hours in and it's doing again. It is very random, sometimes I can go multiple days without this happening, sometimes it happen a few hours in. I only do cold boot once a day, if it broke on that day, it stay broken until tomorrow. Does AIDA might has logs that I can check? Or Windows might know something?

I’ve made a new 1920x480 SensorPanel skin inspired by the RTX 5080. What do you guys think? Is there anything you think I should improve or change? And is there anything else you’d like to see added to the design?

I have a Corsair iCUE LINK H150i LCD connected through an iCUE LINK System Hub. AIDA64 sees the System Hub and LCD in the Corsair Link Dump, but no coolant temperature appears under Computer → Sensor. SignalRGB is able to read the H150i coolant temperature, so the sensor is available from the hardware. I tested with SignalRGB completely closed and there was no change. Corsair Hydro Platinum Sensor Support and Corsair Link Sensor Support are both enabled. Is iCUE LINK System Hub coolant-temperature monitoring currently supported by AIDA64? AIDA64 Extreme v8.35.8400. System Hub VID/PID: 1B1C:0C3F. Corsair Link Dump below... ------[ Versions ]------ Program Version : AIDA64 Extreme v8.35.8400 LLKD Version : 1021 BenchDLL Version: 4.7.931.8-x64 Windows Version : Microsoft Windows 11 Pro 10.0.26200.9168 (64-bit) GetProductInfo : 0x00000030 ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : MSI MPG Z690 Carbon WiFi (MS-7D30) Motherboard Chipset : Intel Alder Point-S Z690, Intel Raptor Lake-S DMI MB Manufacturer : Micro-Star International Co., Ltd. DMI MB Product : MPG Z690 CARBON WIFI (MS-7D30) DMI MB Version : 1.0 DMI MB Serial : 07D3011_MB1E278307 DMI SYS Manufacturer: Micro-Star International Co., Ltd. DMI SYS Product : MS-7D30 DMI SYS Version : 1.0 DMI SYS Serial : Default string DMI BIOS Version : 1.O0 ------[ DevClass / Human Interface Devices ]------ <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_04d9&pid_fc61&mi_02&col01#9&36b93218&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_04D9&PID_FC61&MI_02&COL01\9&36B93218&0&0000</INSTANCE><PARENTINST>USB\VID_04D9&PID_FC61&MI_02\8&205EA12D&0&0002</PARENTINST><BUSNUM>0000000F</BUSNUM><ADDR>00000001</ADDR><REV>0110</REV> <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_0fd9&pid_00a5#8&190c98b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0FD9&PID_00A5\8&190C98B5&0&0000</INSTANCE><PARENTINST>USB\VID_0FD9&PID_00A5\A7FZA6031KLIEX</PARENTINST><BUSNUM>00000015</BUSNUM><ADDR>00000001</ADDR><REV>0120</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_04d9&pid_fc61&mi_02&col02#9&36b93218&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_04D9&PID_FC61&MI_02&COL02\9&36B93218&0&0001</INSTANCE><PARENTINST>USB\VID_04D9&PID_FC61&MI_02\8&205EA12D&0&0002</PARENTINST><BUSNUM>0000000F</BUSNUM><ADDR>00000002</ADDR><REV>0110</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_0db0&pid_005a&mi_07#7&35ef7b7e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0DB0&PID_005A&MI_07\7&35EF7B7E&0&0000</INSTANCE><PARENTINST>USB\VID_0DB0&PID_005A&MI_07\6&ECFA209&0&0007</PARENTINST><BUSNUM>0000000A</BUSNUM><ADDR>00000001</ADDR><REV>0003</REV> <DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10#2&316cd0d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10\2&316CD0D&0&0000</INSTANCE><PARENTINST>CORSAIRBUS\VIRTUALDEVICE&10\1&79F5D87&7&{E7FD4ACE-EE13-11E2-AFDA-000C29100502}</PARENTINST><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR> <DESC>HID-compliant game controller</DESC><DEVPATH>\\?\hid#vid_3f3a&pid_0113&mi_02#c&15ad7161&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_3F3A&PID_0113&MI_02\C&15AD7161&0&0000</INSTANCE><PARENTINST>USB\VID_3F3A&PID_0113&MI_02\B&2A8A2536&0&0002</PARENTINST><BUSNUM>00000013</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c3f&mi_00#8&31878c0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0C3F&MI_00\8&31878C0&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_0C3F&MI_00\7&12619196&0&0000</PARENTINST><BUSNUM>00000018</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1bc5&mi_02#8&cfc72f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1BC5&MI_02\8&CFC72F3&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_1BC5&MI_02\7&2EC3E3BC&0&0002</PARENTINST><BUSNUM>00000005</BUSNUM><ADDR>00000001</ADDR><REV>010?</REV> <DESC>HID-compliant game controller</DESC><DEVPATH>\\?\hid#vid_231d&pid_0125&col01#9&184176e9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_231D&PID_0125&COL01\9&184176E9&0&0000</INSTANCE><PARENTINST>USB\VID_231D&PID_0125\8&604ECF1&0&1</PARENTINST><BUSNUM>00000012</BUSNUM><ADDR>00000001</ADDR><REV>220<</REV> <DESC>HID-compliant game controller</DESC><DEVPATH>\\?\hid#vid_044f&pid_b352#8&24e0fba&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_044F&PID_B352\8&24E0FBA&0&0000</INSTANCE><PARENTINST>USB\VID_044F&PID_B352\7&2CD522FB&0&3</PARENTINST><BUSNUM>0000000B</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV> <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1908&pid_1331&mi_04#9&3046f1b0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1908&PID_1331&MI_04\9&3046F1B0&0&0000</INSTANCE><PARENTINST>USB\VID_1908&PID_1331&MI_04\8&10C57A6&0&0004</PARENTINST><BUSNUM>00000010</BUSNUM><ADDR>00000001</ADDR><REV>0200</REV> <DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_231d&pid_0125&col02#9&184176e9&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_231D&PID_0125&COL02\9&184176E9&0&0001</INSTANCE><PARENTINST>USB\VID_231D&PID_0125\8&604ECF1&0&1</PARENTINST><BUSNUM>00000012</BUSNUM><ADDR>00000002</ADDR><REV>220<</REV> <DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_04d9&pid_fc61&mi_00#9&10f5496c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_04D9&PID_FC61&MI_00\9&10F5496C&0&0000</INSTANCE><PARENTINST>USB\VID_04D9&PID_FC61&MI_00\8&205EA12D&0&0000</PARENTINST><BUSNUM>0000000D</BUSNUM><ADDR>00000001</ADDR><REV>0110</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_03f0&pid_098d&mi_03&col01#7&2d6ab24f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_03F0&PID_098D&MI_03&COL01\7&2D6AB24F&0&0000</INSTANCE><PARENTINST>USB\VID_03F0&PID_098D&MI_03\6&862FE20&0&0003</PARENTINST><BUSNUM>00000002</BUSNUM><ADDR>00000001</ADDR><REV>4108</REV> <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_03f0&pid_098d&mi_03&col02#7&2d6ab24f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_03F0&PID_098D&MI_03&COL02\7&2D6AB24F&0&0001</INSTANCE><PARENTINST>USB\VID_03F0&PID_098D&MI_03\6&862FE20&0&0003</PARENTINST><BUSNUM>00000002</BUSNUM><ADDR>00000002</ADDR><REV>4108</REV> <DESC>HID-compliant game controller</DESC><DEVPATH>\\?\hid#vid_044f&pid_b351#a&334f1579&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_044F&PID_B351\A&334F1579&0&0000</INSTANCE><PARENTINST>USB\VID_044F&PID_B351\9&287565A&0&4</PARENTINST><BUSNUM>00000016</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a34#7&3986b499&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0A34\7&3986B499&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_0A34\06600113A1109AAF2EDF3361021C00F5</PARENTINST><BUSNUM>0000000C</BUSNUM><ADDR>00000001</ADDR><REV>0004</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1bc5&mi_01#8&30d3b0b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1BC5&MI_01\8&30D3B0B5&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_1BC5&MI_01\7&2EC3E3BC&0&0001</PARENTINST><BUSNUM>00000004</BUSNUM><ADDR>00000001</ADDR><REV>010?</REV> <DESC>HID-compliant device</DESC><DEVPATH>\\?\hid#vid_1462&pid_7d30#6&11ddc1ed&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1462&PID_7D30\6&11DDC1ED&0&0000</INSTANCE><PARENTINST>USB\VID_1462&PID_7D30\A02021081202</PARENTINST><BUSNUM>00000001</BUSNUM><ADDR>00000001</ADDR><REV>0001</REV> <DESC>HID-compliant touch screen</DESC><DEVPATH>\\?\hid#vid_1a86&pid_e5e3#a&5422186&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1A86&PID_E5E3\A&5422186&0&0000</INSTANCE><PARENTINST>USB\VID_1A86&PID_E5E3\9&2B686FBC&0&2</PARENTINST><BUSNUM>00000014</BUSNUM><ADDR>00000001</ADDR><REV>0000</REV> <DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1bc5&mi_00&col01#8&341f7d7b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1BC5&MI_00&COL01\8&341F7D7B&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_1BC5&MI_00\7&2EC3E3BC&0&0000</PARENTINST><BUSNUM>00000003</BUSNUM><ADDR>00000001</ADDR><REV>010?</REV> <DESC>HID-compliant game controller</DESC><DEVPATH>\\?\hid#vid_231d&pid_012e#b&21ef2f0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_231D&PID_012E\B&21EF2F0&0&0000</INSTANCE><PARENTINST>USB\VID_231D&PID_012E\A&A54CF49&0&2</PARENTINST><BUSNUM>00000017</BUSNUM><ADDR>00000001</ADDR><REV>220<</REV> <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a32&mi_03#8&a7763c2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0A32&MI_03\8&A7763C2&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_0A32&MI_03\7&275FE611&0&0003</PARENTINST><BUSNUM>00000011</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV> <DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1bc5&mi_03#8&24bfff38&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1BC5&MI_03\8&24BFFF38&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_1BC5&MI_03\7&2EC3E3BC&0&0003</PARENTINST><BUSNUM>00000006</BUSNUM><ADDR>00000001</ADDR><REV>010?</REV> <DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c3f&mi_01#8&20bec502&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0C3F&MI_01\8&20BEC502&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_0C3F&MI_01\7&12619196&0&0001</PARENTINST><BUSNUM>00000019</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV> <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1bc5&mi_00&col02#8&341f7d7b&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1BC5&MI_00&COL02\8&341F7D7B&0&0001</INSTANCE><PARENTINST>USB\VID_1B1C&PID_1BC5&MI_00\7&2EC3E3BC&0&0000</PARENTINST><BUSNUM>00000003</BUSNUM><ADDR>00000002</ADDR><REV>010?</REV> <DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_04d9&pid_fc61&mi_01#9&12e1f456&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><INSTANCE>HID\VID_04D9&PID_FC61&MI_01\9&12E1F456&0&0000</INSTANCE><PARENTINST>USB\VID_04D9&PID_FC61&MI_01\8&205EA12D&0&0001</PARENTINST><BUSNUM>0000000E</BUSNUM><ADDR>00000001</ADDR><REV>0110</REV> <DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c4e#7&1d9c247f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0C4E\7&1D9C247F&0&0000</INSTANCE><PARENTINST>USB\VID_1B1C&PID_0C4E\A6B5T34400QHUQ</PARENTINST><BUSNUM>00000007</BUSNUM><ADDR>00000001</ADDR><REV>0200</REV> ------[ HID Device Info / HID-compliant vendor-defined device ]------ Manufacturer : Corsair Product : iCUE LINK System Hub Serial Number : 6380863AFAB21E58A76510D58FDF3C53 Device ID : 1B1C-0C3F Revision : 0100h Device Instance : HID\VID_1B1C&PID_0C3F&MI_00\8&31878C0&0&0000 Usage : 0001h Usage Page : FF42h Input Report Byte Length : 513 Output Report Byte Length : 513 Feature Report Byte Length: 0 ------[ HID Device Info / HID-compliant vendor-defined device ]------ Manufacturer : Corsair Product : iCUE LINK System Hub Serial Number : 6380863AFAB21E58A76510D58FDF3C53 Device ID : 1B1C-0C3F Revision : 0100h Device Instance : HID\VID_1B1C&PID_0C3F&MI_01\8&20BEC502&0&0000 Usage : 0002h Usage Page : FF42h Input Report Byte Length : 33 Output Report Byte Length : 0 Feature Report Byte Length: 0 ------[ HID Device Info / HID-compliant consumer control device ]------ Manufacturer : Corsair Product : CORSAIR iCUE LINK AIO LCD Screen Module Serial Number : A6B5T34400QHUQ Device ID : 1B1C-0C4E Revision : 0200h Device Instance : HID\VID_1B1C&PID_0C4E\7&1D9C247F&0&0000 Usage : 0001h Usage Page : 000Ch Input Report Byte Length : 512 Output Report Byte Length : 1024 Feature Report Byte Length: 32 ------[ DevClass / USBXpress Devices ]------ < No USBXpress Device Found > < No Corsair Link Device Found >

Hello everyone, I recently bought the Lian Li 8.8 to have the sensor data permanently displayed. Unfortunately, in my opinion, the Lian Li software is inadequate for this purpose, so I've been working with the SensorPanel in AIDA64 and have already created a screen displaying the information I need. Unfortunately, I missed the sale at the beginning of August, but I'd like to buy the Extreme version. Are there any current discounts available? Thanks!

I’m sorry if my earlier comments misled you. You can only adjust either the width or the height of the panel. For example, if I want to change the height of a 2560×720 panel to 1920×515, I would enter 71.52% in the Scale by… option, which produces a panel size of 1831×515. This way, instead of resizing by width, I can resize the panel by height.

Looking for one of the various moderno themes in 480x320. I see they exist, but not on their site for downloading

WO WO WO!! 😲 What have you done, man?! 🔥 This new “Scale by” feature is AMAZING! The new “Scale by” feature is awesome! Finally, we can just enter the exact size we want instead of fighting with the dimensions. Seriously, THANK YOU to the whole team. What a great improvement! 🙏👏

I installed the latest AIDA64 beta and rebooted Windows, but the issue remains. I’m attaching the ISA Sensor Dump. isasensordump_x870crosshair2006.txt

I know it's not technically overclocking in case the memory module is rated at that speed that you choose as an XMP profile, but it may worth a try to check if the issue goes away once you lower the memory speed to a more conservative value like DDR5-4800.

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If the issue persists, please post an ISA Sensor Dump and we'll investigate it further.

ROG Crosshair 2006 – missing/incorrect motherboard sensor readings in AIDA64 Hi, I’m experiencing a sensor monitoring issue in AIDA64 on an ASUS ROG Crosshair 2006 (X870E). In the latest AIDA64 version, some motherboard sensors either disappear completely or show incorrect values. In the previous version, the sensors would disappear intermittently: sometimes they were detected correctly after launching AIDA64, and sometimes they were missing. The issue seems related to ASUS monitoring software. After installing Armoury Crate or ASUS MB Manager, motherboard sensor readings in AIDA64 become unreliable or disappear. At the same time, HWiNFO reads the same motherboard sensors correctly and consistently, even when AIDA64 has the issue. System: ASUS ROG Crosshair 2006 (X870E) Windows 11, latest build AIDA64: latest version Armoury Crate / ASUS MB Manager installed HWiNFO: no sensor issues Could you please check whether there is a compatibility issue with sensor monitoring on the ROG Crosshair 2006, especially when ASUS monitoring services are installed? I can provide sensor dumps, ISA Sensor Debug information, or other diagnostics if needed.

The month, day, and week are shown as static digital image sensors, acting as fixed readouts rather than flip mechanisms. They update once at midnight, so there is no functional reason to use them as flipping displays.

It looks looks like BHSY on tab 4 has done it.

In two days the premiere of GTA6, so let's celebrate this event with a new 480x1920 panel, it does not provide sensors so that everyone can add their own according to their taste Prześlij opinię GTA6.spzip

I second BHSY statement. Your programmers are outstanding. Now if they could only come up with a Linux verson!