Amd Gpu Tweaks
Arleen Jerdee
There was a bug in gnome-tweaks 46.0 that was preventing the font setting from working. That has already been fixed and will be in the next release. Using gsettings directly like already suggested should work in the meantime.
At some point, I got ahold of a sales tape by Fred Herman, who years ago was a huge sales guru. In 30 minutes, he taught me a whole new definition of selling that enabled me to look only for those who would want to buy my product and not to pester the rest. In a few months, that philosophy turned me into a sales superstar, a #1 Sales Manager out of 70 sales managers for seven years, VP of Sales with 650 sales reps, and today considered by some as a world expert on selling. Tiny tweaks did, in fact, lead to a big change.
Thank you, David (and Amy), for educating me and hopefully reminding the readers of this blog that tiny tweaks can indeed create huge change. I will continue to believe that being forever in search of small things can ensure that we get better each day. It is a formula for success that has, and always will, work.
There are actually a bunch of gnome specific packages (many already installed as part of the default gnome3 installation) that you can look at by searching the package set for gnomeExtensions.* like this.
Annoyingly, I usually have to restart GNOME to be able to see applications with desktop items in the list of applications and gnome-shell search. Does gnome-tweaks launch from the command-line? (Or you could try to restart GNOME.)
What would be more helpful is to allow the tweaks to be (1) re-ordered in the browser and/or (2) grouped into sub-folders under the 'Tweaks' folder in order to quickly find and modify the right tweak in a large presentation file.
(I am currently trying to convince some older users that it is faster to use the ipn environment than to do what their current practice is: Saving isometric views of all the parts out to AutoCAD and tracing tweak lines. So far, I have proved nothing, since these complex assemblies end up taking so long to organize to look correct. I think the largest time-waster is FINDING the tweak you need to change after-the-fact.)
It is recommended to remove all third-party extensions before updating, then install the compatible versions after updating and rebooting. All Most extensions in the Manjaro repos are already updated.
Thank you. I removed all the extensions that are no longer compatible. No change. Then I disabled all extensions and rebooted. No change. Then I updated in Terminal with extensions disabled. No change: no General in Tweaks.
I also do not have the general as a first menu item, as I read this I checked tweaks.
Booted an old vm that was not updated for a while and there is a general item in tweaks.
VM has manjaro gnome stable running, last update 18-10-2023 & gnome 44.5
You probably run gnome 45 now? With gnome-tweaks 45.
Oh, by the way you can control that in /etc/systemd/login.conf or create your own conf file in /etc/systemd/logind.conf.d/. Mine for example since I keep my laptop lid closed since I have three external monitors and always am connected to power:
I installed the module on my mac with $ pip install django-widget-tweaks and placed 'widget_tweaks' in the INSTALLED_APPS = [...] part of my app's settings.py file. Those were the only 2 things I saw that I needed to do after reading the documentation for how to use widget tweaks.
(for me) The problem was that I was working in an virtural env in PyCharm) but I have a global python as well. From my command line I was running manage.py runserver, the problem being that my global python doesn't have the widget-tweaks library installed. ( I didn't realize I wasn't running from the venv)
I got this since I added 'widget_tweaks', above the started apps.You need to add it under the started apps, you can add pip installed like this INSTALLED_APPS += [ 'widget_tweaks', ] under INSTALLED_APPS.Only add pip installed apps in INSTALLED_APPS += [] and started apps in INSTALLED_APPS = [].
I already had Python2.7, so I ran the pillow installation procedure and I had error messages returned. I figured that maybe I should reinstall python, so I googled "Python 2.7", and I was invited to install 2.7.0.
OK, at the moment there's a version 2.0.2.4 and a version 2.0.2.5 in the download folder. I downloaded the latest version only. This is where I discovered that I needed version 2.0.2.4 installed beforehand. I would recommend the instruction is changed as follows:
Hi, thanks for the suggestions, I've tweaked the installation text to avoid pitfalls. The plan was to only have to download the latest version - what did you encounter when you tried to go straight for 2.0.2.5? I'm away from my normal set up right now so I can't verify my assumption.
I can't remember what I encountered, but it didn't match up with what the installation manual was showing. It was enough information to suggest that maybe 2.0.2.5 was not sufficient to incorporate all the tweaks.
Anyway, I've been doing some tweaks of my own in planemaker and also the lua scripts:
- I've made the taxi and landing lights much brighter. This is a trick I've learned from other aircraft, but it makes nighttime life a lot more pleasant!
So in progress right now, I'm reworking the electrical system completely. The existing logic was such that all the electrical consumers were tied to the batteries/external power. It was possible to have engines running with generators coupled, and when the battery was switched off, everything was dark. That wasn't acceptable to me.
I'm splitting the L and R main busses, and setting up two more inverter busses. Essentially there will be three groups of consumers (L Main, R Main, Inverter). There's four sources (L Gen, Battery or External feeding the left bus), R Gen Feeding the right bus. Cross tie will allow L and R to feed each other. At the moment the inverter consumers are coupled directly to either bus, but eventually I'll figure out how to had two more switches.
I've worked on the master.lua file. That's the caution lights sorted out, primary fuel pumps, fuel gauges, lighting, "stab deice" and autopilot put onto the correct busses.
R Main Bus
Nav 2/ Com 2 Radios and CDI Needles
HSI and RMI compass Plate (copilots side)
Remaining Caution Lights (L Generator, R Generator Overheat, R Engine Oil Pressure)
AC Busses (115v and 26V)
Fuel Level Indicators
Fuel Flow Indicators
Oil Pressure Indicators
Engine Torque
Other things I can't find yet:
Secondary Fuel Pumps
Overspeed governor
Fuel X-Feed Valve
Beta System
Hydraulic Fuel Pump
Other things I can find, but can't solve:
Attitude Indicator (more on that below)
So, the general arrangement of busses is as follows:
Battery or External Power switch can be selected to energise the battery/external power bus (there's no consumers off this bus, so it's very simple).
DC Master switch is selected to energise the L Main Bus when Battery/External Power is energised
L Generator Feeds the L Main Bus
R Generator Feeds the R Main Bus
Cross Tie will ensure that power can be fed between the L and R Main Busses
The AC Busses are at present permanently connected to both the L and R Main Busses. If either main bus is alive, then the AC Busses are also alive. There should be two inverter switches, one for each Main Bus (with either switch feeding both AC Busses). At this stage, I have to live without the switches until such time that I'm confident enough dive into blender and do a deeper edit of the .obj file.
So now you can break the cross ties and watch most of your systems degrade as Mr de Havilland originally intended.
Other behaviours:
Battery will charge up from either external power, or the Left Main Bus. It will do so gradually rather than instantly
Generators will trip if the gen switches are on, but engines are no longer running (I might develop the logic further to include generator failures).
A generator that is tripped requires a momentary reset to re-energise
A generator that is switched off, can be switched back on without need for a manual reset.
That leaves the attitude indicators:
I want to split them up into the L and R Main Busses.
However their properties are tied together. It's one lua file, and one power failure condition described within.
Now I'm stuck here. With every other guage, I can dive into the "cockpit.obj" file and have a root around for the the appropriate datarefs, and then manipulate things to suit. I can't even find a single reference to the Artificial Horizon, either within the cockpit.obj file, or anywhere else. I'll keep hunting, but some tips will be useful.
Next stop:
- Fuel Management system. It's very ropey! Try this with engines running, switch off a fuel pump, and then switch on again. You engine continues to die, even if you put the igniter back into continuous mode. I want to get this system into an airworthy condition, and hopefully make use of the secondary pumps.
I've learned much in the last three days:
- Diving into lua scripts, .obj files, editing them in notepad++. I've learned about local variables, X-Plane datarefs, custom datarefs. How to manipulate them. How to bang my head against a brick wall wondering why the iterative functions aren't iterating (because I declared a variable within a function, and not outside it!). (That generator reset spring back switch really tested my will!)
If you're prepared to purchase Carenado aircraft, then there's no reason why you shouldn't purchase this one.
She looks lovely, she sounds nice and she flies nicely and for most people that is sufficient. Normal procedures are mostly fine with this aircraft.
However for people like me, this aircraft is a great opportunity to make better and more in depth. I've sent an email to the author of this aircraft asking if he'd be interested in reviewing my mods with a view to incorporating into the official release. Maybe if he says yes, then everyone will get it.
ff7609af8f