View allAll Photos Tagged debugging
An idea of some decent pose manager pursues me for long time.
Yesterday I found a way to pick all idles (poses) from ESPs.
Basically this is just a draft and the mod itself is in the similar 'draft stage'.
And I will not rush to implement it
What functionality I have in mind right now:
- pick ESP/ESM and preview its poses by pressing left or right arrow keys (Alt key must be hold).
- Mark a pose as favourive with Alt-F
- In case no favourite pose list created yet, it asks you to create one, will make it _active_, fav. poses will go into that list
- Create as much pose lists as you can
- Fav. poses will go into _active_ pose list
- Pick any pose list and apply poses
- Assign name to a pose
Tiny tech details:
- I don't want to go for MCM each time I need to change something, so there must be as much hotkeys as possible
- Alt key can be replaced with any, as well as other keys
- Ofc., the data must be shareable between other play throughs, users etc
The problems:
- You will never know whether the pose is stand or anything as the pose information is spread across bunch of forms in the ESP. Idle's editor name is useless "FNISIDleDuplicate00XXX" in most cases (I use "Halo's poser.esp")
- The data is shareable, but I don't believe in community-generated list of poses. Most of you will start with zero pose lists
- I'd like to use some UI element to display current pose name. Debug.Notification is way too slow
- There will be plenty of dummy T-poses in "Halo's poser.esp"
Any idea is welcomed, but don't expect I'll implement everything you will suggest
"Brothers: A Tale of Two Sons" - 2400x3200 Downsampling , 4xSSAA , Debug camera ,removed debug info , Engine ini tweaks , custom fov, SweetFX , white line removed with photoshop
The Witcher 3: Wild Hunt | Downsampled from ~32MP | Debug Console | HD Reworked Project | Photomode 2inOne | Debug Console Extensions | High Quality Faces | Nvidia Ansel |
The Witcher 3 : Wild Hunt , Debug Console Enabler 1.12
Sweet FX presets : â™›1.000 Times Better v1.3
The Witcher 3: Wild Hunt | Downsampled from ~32MP | Debug Console | HD Reworked Project | Photomode 2inOne | Debug Console Extensions | High Quality Faces | Nvidia Ansel |
The Witcher 3: Wild Hunt | Downsampled from ~32MP | Debug Console | HD Reworked Project | Photomode 2inOne | Debug Console Extensions | High Quality Faces | Nvidia Ansel |
Dark Souls Remastered
• Debug Menu (free camera and timestop. FOV cannot be changed in free camera mode, it is locked)
• 9400x5400 (cropped and downsampled)
• Reshade
"Brothers: A Tale of Two Sons" - 2400x3200 Downsampling , 4xSSAA , Debug camera ,removed debug info , Engine ini tweaks , custom fov, SweetFX
This is a debugging image for helping to sort out the lakes tagged as coastline in OpenStreetMap. There are various lakes and areas of water that are not sea that are currently marked with natural=coastline. They should actually be marker natural=water as per guidance on the OSM wiki.
"Brothers: A Tale of Two Sons" - 2400x3200 Downsampling , 4xSSAA , Debug camera ,removed debug info , Engine ini tweaks , custom fov, SweetFX
I just love the art in this game.. so beautifull , it's like i want to take a walk there :)
Advanced menu > Debug Settings and CameraOffsetRearView Z=0.000 can make it easier to navigate through low-ceiling spaces. Camera is vertically level with your avatar instead of pointing downwards.
The Witcher 3: Wild Hunt | Downsampled from ~32MP | Debug Console | HD Reworked Project | Photomode 2inOne | Debug Console Extensions | High Quality Faces | Nvidia Ansel |
I've been having some issues with our MoMA-bound Cabspotting visualization lately, and, as is often the case, ended up having to create another visualization just to figure out what the problem was.
Each of the white dots represents a discreet data sample–the location of a specific cab at a particular time. Here, samples for each cab are placed on a separate row and arranged temporally from left to right. More "active" cabs (i.e., the ones with more available samples) are placed at the top.
The green and red marks at the top represent the start and end times of the displayed period. For each cab, an algorithm seeks through the list of segments between each sample that fall within them. The hue corresponds to the position in the line between the start and end of the period: Green lines are closer to the start time, red ones to the end time.
So, what does it show? Primarily, that there is quite a bit of "bad" data in our set. Those long lines at the bottom indicate extended periods of time during which those cabs weren't transmitting their locations. Most cabs tend to ping the depot every 30-60 seconds, but some do it less than once per hour. For the most part, though, the consistency of that green-to-red column seems to indicate that we've got a pretty good idea of where most of the cabs were in that time period, and with a reasonable degree of resolution.
God, I'm such a geek.