07 February 2016, 21:13 | #81 | |
R.I.P Smudge 18-08-16
Join Date: Aug 2005
Location: Leicester/UK
Age: 66
Posts: 3,968
|
Quote:
I still cant get a HDF to boot from the CDTV quickstart config. It will only boot if you select CDTV WD33C93 SCSI from Adv Chipset. I can't remember having to use that before, has something changed? |
|
07 February 2016, 21:46 | #82 |
Registered User
Join Date: Jun 2012
Location: Austria
Posts: 76
|
Quickstart options seem not to work in the latest Beta.
No matter to which config i switch in Quickstart, nothing changes. Must also be the reason why Arnie has problems with booting when using the CDTV quickstart config. Same problem with Beta 3. Doing it the usual way, i go to the normal quickstart menu point on the left, pick the chosen config from the emulated hardware dropdown - normally now the settings should be auto loaded, but as Arnie said, only very basic settings are chosen - which are the same for whatever for a config i pick that way. It worked normal In Beta 1. Last edited by SaphirJD; 07 February 2016 at 22:25. |
07 February 2016, 22:28 | #83 |
R.I.P Smudge 18-08-16
Join Date: Aug 2005
Location: Leicester/UK
Age: 66
Posts: 3,968
|
As Toni pointed out to me, make sure start in quick mode is ticked. It seems these betas don't have it ticked by default.
|
07 February 2016, 22:33 | #84 |
Registered User
Join Date: Jun 2012
Location: Austria
Posts: 76
|
I see, thanks
|
07 February 2016, 22:44 | #85 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
Quote:
There was registry handling fix in previous beta (= by following proper test procedures this would not have been so confusing..) that caused some non-existing keys to return non-zero value and this affected Quickstart mode button (and some others) if you have never previously clicked the checkbox at least once. |
|
07 February 2016, 23:06 | #86 |
Posts: n/a
|
When i open the floppy selection box winuae 64 bit crashes. The 32 bit version works instead.
|
08 February 2016, 08:17 | #87 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
Quote:
http://eab.abime.net/showthread.php?t=80216 Also I think this also needs to be mentioned because crystal ball also says this is not unique to 3.3. Quote:
|
||
08 February 2016, 16:39 | #88 | |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,337
|
Quote:
By the way, it looks like you do ST palette correction after gamma correction. Would it be better to do that before gamma correction? An equivalent (at least for ST-colours) to vi = (vi + (vi & 7)) * 2; is vi = (vi + (vi >> 4)) * 2; I don't know which would be faster or produce better code. Another equivalent would be vi = (vi<<1) + (vi>>3); Last edited by mark_k; 08 February 2016 at 16:46. |
|
08 February 2016, 16:41 | #89 | |
Posts: n/a
|
Quote:
However if it serves to someone else, i tried to deactivate many shell extensions and finally Crystall ball say to me that i must deactivate avast extensions. It seems that avast are the problem as you posted also in other thread. Hi. |
|
08 February 2016, 18:32 | #90 | ||||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
Quote:
EDIT: I added HDF to CDTV config, nothing happened with previous version. CDTV CD/other external boot device priorities are strange. Quote:
Quote:
Quote:
Last edited by Toni Wilen; 08 February 2016 at 18:37. |
||||
09 February 2016, 03:51 | #91 |
Global Moderator
Join Date: May 2013
Location: Setúbal, Portugal
Posts: 609
|
I'm here just to inform you that I'm having a strange issue with v3.3.0 Public Beta 4 - 2016.02.07.
When I load WinUAE my configurations are all as they always were but when I load a game, it automatically resets my controls (my USB Logitech Dual Action gets replaced with the Keyboad Layout A), rendering the use of the game pad impossible, even if i reassign and reconfigure it. I've tried to re-save the configurations but it still gets reset each time I load a new game. Does anyone else experience this issue? The version I was using before (v3.3.0 Public Beta 2 - 2016.01.31, to which I have since reverted back) was working fine. Last edited by PortuguesePilot; 09 February 2016 at 04:02. |
09 February 2016, 12:06 | #92 |
Missile Command Champion
Join Date: Aug 2005
Location: Germany
Age: 52
Posts: 12,438
|
|
09 February 2016, 14:45 | #93 | |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,337
|
Quote:
I'll refer to brightness as ranging from 0 (black) to 1 (white) as that's simpler when talking about gamma correction (just raise to a power). Whatever the gamma correction factor y, 0^y = 0 and 1^y = 1. Black and white are always unchanged. Suppose the user gamma-corrects with a value of 2. Unadjusted "ST white" is value 7/15. That becomes (7/15)^2 = 0.2178 approx after gamma correction. If we then double it (correcting ST to Amiga 4-bit) you get 0.4356 approx. So even ST white becomes less than 50% grey after ST-correction. Alternatively, suppose the gamma correction factor is 0.5. Then ~half-brightness ST is 4/7, i.e. 4/15 Amiga = $44/255 8-bit = 0.2667 approx. Raise that to power 0.5 ==> 0.5164 approx. If we do ST-correction after that, end up with 1.0323 which clips to 1 (i.e. full white). So anything above ST value 3 gets clipped to white in that case. |
|
10 February 2016, 15:36 | #94 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,337
|
Another suggestion/option for ST-correction... There are probably some/many ST ports for the Amiga which have corrected (doubled) colours. (Can anyone research into likely examples? How about Speedball, Xenon, Gods?)
So an option to extend the doubled 4-bit colours to 8-bit could also be useful. In other words Amiga $EEE ⤇ $FCFCFC. (For each colour component %xyx0xyz0 ⤇ %xyzxyz00.) The code could actually become clearer since you need to correct before gamma-correction. The current code in video_calc_gammatable() could become something like this: Code:
switch (currprefs.gfx_threebitcolors) { case 0: break; case 1: con *= 2.0f; // 0xEE/0x77 case 2: con = (con * 252.0f) / 119.0f; // 0xFC/0x77 case 3: con = (con * 252.0f) / 238.0f; // 0xFC/0xEE } v = video_gamma((float)(i - 256), gams[j], bri, con); By the way, similarly to needing to ST-correct before gamma correction, in video_gamma() it might be an idea to do value *= con; before value += bri;. Edit: Moving that con-setting code to the start of video_calc_gammatable() (where con is initially set to con = ((float)(currprefs.gfx_contrast + 1000)) / 1000.0f ) might be cleaner still. Last edited by mark_k; 10 February 2016 at 16:07. |
10 February 2016, 16:46 | #95 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
At least Speedball and Gods highest color value is EEE so it seems your third option makes sense.
|
10 February 2016, 17:33 | #96 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
http://www.winuae.net/files/b/winuae_3300b5.7z
http://www.winuae.net/files/b/winuae64_3300b5.7z Beta 5: - Game Ports mouse and joystick was always reset to defaults (b4) - Dark palette fix adjustment is now calculated before other adjustments (brightness, contrast, gamma) - Dark palette fix third option added, pre-converted Atari ST palette increased to full range, 12-bit EEE becomes nearly full white, FCFCFC in 24-bit RGB space. (Not FFFFFF because palette would not be linear anymore) OS4 UAE expansion updates: (Discussion thread here: http://eab.abime.net/showthread.php?t=81146) - Directory filesystem random errors fixed. - Directory filesystem/CDFS CD on the fly insertion/removal supported! (It wasn't that difficult after all) - uaescsi.device supported. NOTE: Try not to change uaegfx resolution in OS4, it can cause mysterious crashes or side-effects. Fix coming later. TODO: bsdsocket.library and fixing random hangs. |
10 February 2016, 21:35 | #97 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,337
|
I noticed that in video_calc_gammatable() you do
gamma[i][j] = (uae_u32)v; where v is of type float. Since the float-to-int conversion truncates, should you do this instead? gamma[i][j] = (uae_u32)(v + 0.5f); Edit to add: Similar issue in limit256() and limit256rb()? The limit256rb() case may be slightly different since there v can be negative. Last edited by mark_k; 10 February 2016 at 22:05. |
10 February 2016, 23:25 | #98 |
Registered User
Join Date: Feb 2014
Location: Poland
Posts: 190
|
I'm sorry if i'm writing this in a wrong thread, but i have spotted that on winuae64_3300b5 (latest 64-bit beta and at least previous) Realtek 8029 PCI could not open. This is happening only on 64-bit versions. The same config is working properly on 32-bit versions. Debug attached.
PS. Official WinUAE3220 64-bit works ok (on emulated Picasso IV Zorro III). Last edited by Snake79; 11 February 2016 at 00:05. Reason: PS |
11 February 2016, 08:16 | #99 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
Quote:
32-bit probably can't allocate full 512M. |
|
11 February 2016, 12:53 | #100 |
Registered User
Join Date: Feb 2014
Location: Poland
Posts: 190
|
Thanks for diagnosis and explanation. I will try to re-config tonight.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE 2.7.0 beta series | Toni Wilen | support.WinUAE | 326 | 03 December 2013 23:37 |
WinUAE 2.6.0 beta series | Toni Wilen | support.WinUAE | 271 | 14 May 2013 16:51 |
WinUAE 2.4.1 beta series | Toni Wilen | support.WinUAE | 223 | 09 May 2012 16:16 |
WinUAE 2.3.1 beta series | Toni Wilen | support.WinUAE | 90 | 23 February 2011 21:17 |
WinUAE 2.0.0 beta series | Toni Wilen | support.WinUAE | 445 | 13 December 2009 14:46 |
|
|