Opening interlaced screens with AMOS - Page 2

Retro1234 · 14 March 2017, 14:12

Quote:

Originally Posted by AronGooch

I just ran the same test with Amos 1.3 but this time in WinUAE as apposed to my real machine test I did earlier with Amos Pro.

The results are exactly the same as Amos Pro on my real A600 machine.

In WB3.1 the interlaced screen issue is present and running Amos 1.3 in WB1.3 the issue goes away and a proper interlaced screen is displayed.

is it not just Iprefs or something - what about Wb1.3 on kick 3.1?

03 July 2017, 05:20

Sorry it's been a few months since I last posted but have got back to this problem as I have a game that is almost finished on Amos Pro but cannot run it in anything above WB1.3 because this issue is still present.

Running Amos1.3 under kickstart1.3, the interlace screens work correctly as I posted earlier but running Amos1.3 under kickstart3.1 creates the same issue with the interlaced screen not showing correctly in Hires mode.

Samurai_Crow · 03 July 2017, 07:55

Have you unchecked the coersion item in the IPrefs preferences yet?

Toni Wilen · 03 July 2017, 09:05

Does it work with KS 2.0, 3.0? (As in, is it KS 3.1 _only_?)

3.1 changed how graphics.library vblank works, if graphics.library thinks mode is not interlaced (=interlace was not opened using system functions), it always sets long field bit in vblank routine.

Amiten · 05 July 2017, 17:35

Hello, can someone explain how to fix the interlace issue in Amos please ? I read all Thread and not find any solution exept Modify something in Amos Config but is not clear what and how...

Thank you in advance

Enviado desde mi ONE LTE HD (ONE TORO) mediante Tapatalk

kamelito · 05 July 2017, 17:44

Maybe detect the OS and if it is 3.1 call the OS fonction instead of using Amos.
Kamelito

Toni Wilen · 05 July 2017, 17:54

If the problem is KS 3.1 only: open interlaced screen using system routines (resolution can be any, preferably as small as possible to not use too much ram), then use normal AMOS commands to open interlaced mode, which should now work correctly.

kamelito · 07 July 2017, 07:59

@samuraicrow
What is the status of Amos re développement done at ultimateamiga.co.uk?
Is there build of Amos Pro 2.1 or Amos Pro 3.x? What came out of the work done on the originals sources? Any binaries available?
Kamelito

Samurai_Crow · 07 July 2017, 11:13

Kamelito, the head developer of the effort (BruceUncle) had back surgery just before he was about to release the 2.1 bug fix version. We are trying to put all of his changes into a private version control system because a recent former team member tried to break up the team and deleted our contributions on GitHub.

Problem solved for the OP.

13 July 2017, 07:31

Sorry all, been busy times lately.

Im happy to say the problem I was having with the interlace screen opening in Amos Pro has been fixed. I can now correctly open fully working interlace screens in Amos Pro under Kickstart 3.1 now.

I have found via Amiga.Org forum that there might be a possibility I hadn't been using the latest Amos Pro libraries. Upon further investigation and from many users input I found there is an 'amos.library' version 2.30. Downloading this, which was very difficult to obtain I found, renaming to amos.library and placing in my Libs directory I found Amos Pro now has no issues opening an interlace screen. Awesome stuff!

kamelito · 13 July 2017, 07:49

Glad you solve your issue. As you wrote that it was difficult to obtain, why not upload it here in the zone to avoid having to look after it later?
Kamelito

LocalH · 08 July 2019, 03:20

For anyone who may be dealing with this issue, I Zone'd amos.library 2.30.

Also, ensure you don't also have an older version of it in your AMOS installation's APSystem directory. If there is, then AMOS will use it instead of the one in LIBS:

CaptainNow · 09 December 2020, 14:16

I had the same issue today in Amos Pro.

Screen wouldn't work properly in WB 3.1 but works fine in WB 1.3.

Worth noting for anyone else who rips their hair out over this issue (like I have done haha)

Predseda · 09 December 2020, 14:28

Quote:

Originally Posted by LordNipple

Screen wouldn't work properly in WB 3.1 but works fine in WB 1.3.

And is this also hardware-related? (AGA/OCS)? Or the different versions of Workbench on the same Amiga config?

Wertysoft · 21 April 2022, 12:41

Can some re-up The Amos 2.30 file in the zone?

07 July 2017, 11:13	#29
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	Kamelito, the head developer of the effort (BruceUncle) had back surgery just before he was about to release the 2.1 bug fix version. We are trying to put all of his changes into a private version control system because a recent former team member tried to break up the team and deleted our contributions on GitHub. Problem solved for the OP. Last edited by Samurai_Crow; 12 July 2017 at 19:35.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Interlaced vs Non-Interlaced display	whitebird	support.Hardware	9	12 January 2015 10:20
Scanline flicker when moving between interlaced and non-interlaced WB screens	mr_a500	support.FS-UAE	0	19 December 2014 17:10
Automatically disable Direct3D scanlines/mask during interlaced screens (WinUAE)	Maren	request.UAE Wishlist	6	26 September 2010 09:14
Flickering when interlaced and non-interlaced highres screens "meet"	Maren	support.WinUAE	12	27 November 2009 22:59
Where's the amos.library on the 3-disk AMOS set?	andreas	support.Apps	0	15 November 2001 16:04

03 July 2017, 05:20	#22
AronGooch Posts: n/a	Sorry it's been a few months since I last posted but have got back to this problem as I have a game that is almost finished on Amos Pro but cannot run it in anything above WB1.3 because this issue is still present. Running Amos1.3 under kickstart1.3, the interlace screens work correctly as I posted earlier but running Amos1.3 under kickstart3.1 creates the same issue with the interlaced screen not showing correctly in Hires mode.

03 July 2017, 07:55	#23
Samurai_Crow Total Chaos forever! Join Date: Aug 2007 Location: Waterville, MN, USA Age: 49 Posts: 2,186	Have you unchecked the coersion item in the IPrefs preferences yet?

03 July 2017, 09:05	#24
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Does it work with KS 2.0, 3.0? (As in, is it KS 3.1 _only_?) 3.1 changed how graphics.library vblank works, if graphics.library thinks mode is not interlaced (=interlace was not opened using system functions), it always sets long field bit in vblank routine.

05 July 2017, 17:35	#25
Amiten Banned Join Date: May 2011 Location: Spain Posts: 519	Hello, can someone explain how to fix the interlace issue in Amos please ? I read all Thread and not find any solution exept Modify something in Amos Config but is not clear what and how... Thank you in advance Enviado desde mi ONE LTE HD (ONE TORO) mediante Tapatalk

05 July 2017, 17:44	#26
kamelito Zone Friend Join Date: May 2006 Location: France Posts: 1,801	Maybe detect the OS and if it is 3.1 call the OS fonction instead of using Amos. Kamelito

05 July 2017, 17:54	#27
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	If the problem is KS 3.1 only: open interlaced screen using system routines (resolution can be any, preferably as small as possible to not use too much ram), then use normal AMOS commands to open interlaced mode, which should now work correctly.

07 July 2017, 07:59	#28
kamelito Zone Friend Join Date: May 2006 Location: France Posts: 1,801	@samuraicrow What is the status of Amos re développement done at ultimateamiga.co.uk? Is there build of Amos Pro 2.1 or Amos Pro 3.x? What came out of the work done on the originals sources? Any binaries available? Kamelito

13 July 2017, 07:31	#30
AronGooch Posts: n/a	Sorry all, been busy times lately. Im happy to say the problem I was having with the interlace screen opening in Amos Pro has been fixed. I can now correctly open fully working interlace screens in Amos Pro under Kickstart 3.1 now. I have found via Amiga.Org forum that there might be a possibility I hadn't been using the latest Amos Pro libraries. Upon further investigation and from many users input I found there is an 'amos.library' version 2.30. Downloading this, which was very difficult to obtain I found, renaming to amos.library and placing in my Libs directory I found Amos Pro now has no issues opening an interlace screen. Awesome stuff!

13 July 2017, 07:49	#31
kamelito Zone Friend Join Date: May 2006 Location: France Posts: 1,801	Glad you solve your issue. As you wrote that it was difficult to obtain, why not upload it here in the zone to avoid having to look after it later? Kamelito

08 July 2019, 03:20	#32
LocalH Amiga user since 1990 Join Date: Aug 2004 Location: Kingsport, TN / USA Age: 44 Posts: 295	For anyone who may be dealing with this issue, I Zone'd amos.library 2.30. Also, ensure you don't also have an older version of it in your AMOS installation's APSystem directory. If there is, then AMOS will use it instead of the one in LIBS:

09 December 2020, 14:16	#33
CaptainNow Eleventh Hour Games Join Date: Feb 2011 Location: Carnforth, England Age: 49 Posts: 558	I had the same issue today in Amos Pro. Screen wouldn't work properly in WB 3.1 but works fine in WB 1.3. Worth noting for anyone else who rips their hair out over this issue (like I have done haha)

21 April 2022, 12:41	#35
Wertysoft Registered User Join Date: Apr 2022 Location: Haparanda / Sweden Posts: 1	Can some re-up The Amos 2.30 file in the zone?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)