Looking for a new house, and got sick of having to wade through the same listings every few days. So this script stops pins showing up in the map if I've already viewed them on the map.Previously viewed properties are stored in your browsers local storage, so easiest way to clear is pasting the code below into the console while on RealEstate.com.au
Can get script at [https://gist.github.com/sacah/49cb7073605513af76a1#file-hide-previously-viewed-properties-realestate-com-au-user-js](https://gist.github.com/sacah/49cb7073605513af76a1#file-hide-previously-viewed-properties-realestate-com-au-user-js)
I have a RaspberryPi with a 750gb attached HDD, on this drive I store a folder called Photos, it contains many sub-directories with photos in them.I wanted to create a new directory that had the same structure of Photos, but all the images are smaller thumbnailed versions.To accomplish this I tried a number of programs and scripts I found online for linux, but most didn't handle sub-directories, I then tried to find programs on Windows that would do this across the network, but they either didn't handle sub-directories or didn't handle errors in network traffic and would bomb out.Read more...
GFX files are basically SWFs, to edit them rename them to a *.swf file and with a hex editor change the first 3 bytes from CFX to CWS, then any Flash Decompiler will happily open them.
I've opened them up and inspected the Actionscript which all worked though I'm yet to try editing one, my guess is you should just be able to change the first 3 bytes back to CFX and rename it back to an *.gfx file for it to work, though depending how it modifies the SWF it might break something extra that GFX files have that SWF doesn't.
Let me know if you've had any success, or more info, I'll update this post as I find out more.
So just bought Dungeon Siege 3 and was horrified with the unchangeable camera angles. So I set about having a dig around the game to try and find a way to change the camera, while digging around I noticed a console file, and the Dungeon Siege III.exe had a number of console commands in it, so I replaced the Help Topics file with the Console, so now when I'm in game I can press Esc, click 'Help Topics' and the console will appear.
After playing around with all the console commands I could find in relation to camera none seemed to have any effect, though most other console commands works, such as adding money, items, XP, levels etc. So cheating is easy in Dungeon Siege III, but changing the camera angles isn't )-: Hopefully I'll have more time to play around with them and work something useful out.
The easiest way to activate the console on your version is by downloading the gui.zip file from http://www.mediafire.com/?sa7a3gepx3ea4f5, then extract the 'gui' folder from gui.zip into %steamapps%\common\dungeon siege iii\data\. Now start Dungeon Siege 3, and when in-game, click 'Help Topics' from the menu to access the console. You'll need to watch the video at 720 to read the names.
If the above video instructions didn't work for you, here are the manual steps.
I grabbed the Dungeon Siege 3 OAF Files Extractor and unpacked the files to a temp directory, unpack data_archive.oaf first, then unpack data_archive_2.oaf into the same place, the files in data_archive_2.oaf overwrite some which is how the game works too.
After looking around my first step was to get console working, I copied gui\console.scn and gui\game.gui into %steamapps%\common\dungeon siege iii\data\gui
Rather than having to repack the archives after editing just drop the files you changed here and it will pick it up rather than using the archived copy.
Now rename console.scn to help_topics.scn and edit game.gui. Find the line
Orange signals what was changed for ease of reading.
Now run the game, while in game press Esc, in the menu click Help Topics and you'll have access to the console.
To get back to the game type modal_close_all and press enter. You can also type mod and press TAB to auto-complete. As we've hacked the console into an unusual place, things don't appear in it's history straight away, so if you press top_down_mp_ and press TAB, because there are multiple options it won't display anything. After you have pressed TAB, just delete the text and type modal_close_all, then enter the console again and you'll now be able to see the options for your previous commands, so we'll see all available options for top_down_mp_ console commands.
I'll add the console commands and explanation here slowly as I find them, though I can't test them all so some might not work, let me know if you find more, descriptions are wrong or they don't work and I'll update this list.
quit -Quit game completely, back to Windows. render_csa reset_tutorial render_hit_flash rumble revert revert_all respawn retry reconnect rcon restart_server respawn_interval
script_list script_run - Runs AMX files located global\scripts, followed by the function name and arguments. Eg: script_run global\scripts\00_intro\00_intro CamShake will result in the screen shaking once you modal_close_all. I haven't looked into AMX files yet, will do a follow up post once I find more out. set_light_set set_global_variable stats_print speedy show_all_damage_numbers subtitle_notification seek_fullscreen_movie stop_fullscreen_movie start_fullscreen_movie status_effect_apply_to_player scale set_level set_resource set_health status startcell startlevel startlevel_data stream_proximity_radius survival_creature_set say start_conversation screen_shake_move_camera session_type save_load_enabled show_spinner save timeline_reload toggle_tutorial tutorial_enabled toggle_pause target_ui_neutral_player_index target_ui_hostile_player_index target_ui_neutral target_ui top_down_mp_fov top_down_mp_distance top_down_mp_pitch top_down_yaw_offset top_down_collision_mp_pitch_speed top_down_collision_mp_decay top_down_collision_mp_hold top_down_collision_mp top_down_collision_sp top_down_zoom_all unpause unlock_all user_setup_delay warning_notification write_file warp_to_player warp_to_position yaw_offset
I had 4 garden solar lights laying around as every time I mow I pull them out and never bother sticking them back in the ground. I wanted something that would notify me when my plants needed watering, when making the moisture sensors I thought I could just hook them up to the LDR on the solar lights and everything would be sweet, but when I cracked open the lights the clever Chinese hadn’t used an LDR, they had just directly used the solar panel, if power was coming in turn lights off, power stops, turn lights on. This was just as easy to tap into though, and in no time I had my moisture sensor rigged up and working, now I just need to see if it works in RL.
Things of interest: 1. Holes for USB, as I have time I'm tracing back where this goes to try and enable it, see if firmware will detect it. 2. CVBS and AGND markings for Composite video output.
I will hopefully be getting a flash chip programmer soon, then I wanted to have a peak at what's stored in the flash, I'm hoping it's the firmware and I can have a poke around at that, though I haven't had much experience disassembling firmware so see how far I get (-:
I'm also interested in VX1826, it supports I2C(IIC), might be able to use it as an easy I2C LCD screen.
Let me know if you have any further information about any of these chips, or if you have one of these units and have successfully modified them at all, I'd love to hear from you.
Other markings on the touchscreen and controller are: MicroTouch, RES-15.0-PL8, 95409 D, TDP#3169, 060304C0338, SR-12-8W-232, ETP-PB-031C-0349
I was given a touchscreen that had a dead LCD, but the touchscreen part still worked. I didn't have any drivers or manuals for it, so tried searching for part numbers. I found this was a Dynaclear-PL75, whose website goes to 3M with no further references.
The touchscreen has a ribbon cable leading to 8wires that connect to a small PCB. At the other end of the PCB is 5wires, in 2 groups. 2wires go to a plug, they are Red and Black so I assume power. The other 3 wires go to a 8pin connector, which I know plugged into the serial port on the motherboard of the computer it use to work with. These cables are Red, Brown and Black.
I plug the 2wire power plug into my breadboard and hook up my Dick Smith power adaptor set to 3V. I connect the Ground of my USBee Logic Analyser to the ground on my breadboard, then I connect channels 1-3 to the 3wire group(Red, Brown, Black).
While I'd assume this is 3wire serial communication, so Red/Brown are Tx/Rx and Black is ground, I'm not sure. I power the touchscreen on, start recording on the USBee Suite and press around on the touchscreen. Once the recording stops, there are no signals detected.
So I change the power supply to 5V, start recording again and push the touchscreen, this time I notice a small green LED lights each time I press the touchscreen, which is encouraging. Once the recording stops there are signals on 1 of the wires.
Figuring this is Async I setup a decoder for it and view the decoded info. I get 0x81 at the start of a 5byte signal, which I'm pretty sure if serial.
I start recording again, and press the screen in a pattern, as shown.
One the decoding finished, I find there are 4 distinct signal groups.
Each group has almost the same pattern in it, so the touchscreen is sending the location even when your finger is held down.
Each group has the following signals: 1. 0x81 0x00 0x5C 0x0F 0x11 2. 0x81 0x0F 0x27 0x0E 0x3F 3. 0x81 0x0F 0x46 0x00 0x69 4. 0x81 0x00 0x79 0x01 0x1E
0x81 is start byte, so guessing remaining 4 bytes are x and y coordinates. Converting to Decimal brings: 1. 92, 3857 2. 3879, 3647 3. 3910, 105 4. 121, 286
So there we have it, educated guess x and y are 0 to 4000. I plan on hooking this up to a linux machine, so I'll release source code once that's done to assist anyone else wanting to do something similar.
If anything is wrong here let me know, I'm just a hobbyist at this stuff.
Bought the PVR off eBay a few years back, came with a 80gb IDE harddrive. There is not a whole lot on TV I watch so 80gb was more than enough for my needs. With the new Free to Air stations though, I've found at times I've filled the drive. Mainly during cricket season.
I had a 250gb SATA drive that was in my home made computer PVR before its motherboard packe it in, so rather than buy a new IDE HDD I looked for ways to use this one. I found an IDE to SATA converter on eBay for ~$7 delivered, only problem was the IDE connector was under the HDD mount, even if I moved the HDD the converter sat too high to put the PVR lid back on. So I soldered together 2 male to male IDE connectors and plugged 2 IDE cabled into each other, which aligned the pins the right way and let me move the converter to under the HDD mount.
A better solution would have been to solder an IDE cable onto and male IDE connector, to properly align the pins, but I don't have a wire stripper for wires that small and couldn't be bothered stripping 40 wires with a knife and soldering the 40 small wires either.
I noticed how hot the 80gb HDD got, knowing a 250gb HDD would get hotter which would lead to early failure, I decided to add a fan while I did the upgrade too. I soldered the fan wires onto the power connector of the SATA converter.
Converter connected to 2 IDE cables and hacked connectors