I also would like to see this. Below are my comments from the firmware thread. Would like to see a way to keep profiles when upgrading firmware and a way to enable binding default profiles to inputs.
Is there any way to prevent firmware updates from clearing the profiles? Or allow the user to save and store the profiles on an SD card so that updating the firmware won’t affect profiles?
Would also be interesting in binding default profiles to individual inputs until the user changes them manually. Maybe allow this with a config file?
All profiles get erased unfortunately. 🙁
Is there any way to prevent firmware updates from clearing the profiles? Or allow the user to save and store the profiles on an SD card so that updating the firmware won’t affect profiles?
Would also be interesting in binding default profiles to individual inputs until the user changes them manually. Maybe allow this with a config file?
Just wanted to confirm that setting Sync Options -> H-PLL Post-Coast to 1 line also fixed the flicker issue with my Performance VGA box that I was seeing.
Mentioned on this page in Shmups forums.
http://shmups.system11.org/viewtopic.php?f=6&t=52158&start=3000
Has anyone else has issues with RGBHV input and the Dreamcast? Not sure if something has started failing in my unit, but the other day I noticed that there is a random flicker/white level change happening with VGA input from my Dreamcast. Noticeable on primarily lighter colors, especially the boot sequence. None of the other inputs have this occur or even with RGBS over AV3. Tried swapping Dreamcast systems, power supplies for the OSSC and it still happens. Bypassing the OSSC doesn’t show this issues on my VGA monitor. I’m going to try another RGBHV source like my GCN or my Xbox 360 VGA cable tonight to see if it’s that or something weird with how my Dreamcast VGA box interacts with the OSSC.
| Cookie | Duration | Description |
|---|---|---|
| _gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
| Cookie | Duration | Description |
|---|---|---|
| __gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| Cookie | Duration | Description |
|---|---|---|
| ct_checked_emails | session | No description |
| ct_has_scrolled | session | No description |
| ct_mouse_moved | session | No description |
| ct_screen_info | session | No description |
| wordpress_apbct_antibot | session | No description |
| wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |
