Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news


  

Author Topic: new frontend F.E.E.L.  (Read 10867 times)

0 Members and 1 Guest are viewing this topic.

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #80 on: July 01, 2015, 02:07:29 am »
Screenshot was not on monitor but instead a bit higher. Anyway with latest version tested at work I cannot reproduce this.

There is other problem. At work I have 1440x900 desktop I started FEEL with default mame layout. When I start game using mamefx and quit FEEL changed it's resolution to 1440x900 too. At the beginning it's probably due  MAMEFX using also 1440x900 for game but when I enable res. switching in mamefx game started in 640x480 but upon exit monitor informed than 1440x900 is active. I did screenshot using PrintScr but it's 640x480. Really strange  ??? Maybe it's Intel HD2000 fault.

EDIT. Let's just ignore this, test was done with computer at work so it's not the best for testing.
« Last Edit: July 01, 2015, 03:09:48 am by haynor666 »

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #81 on: July 01, 2015, 03:15:52 pm »
It's quite a strange behaviour.. The emu should restore the right res upon closure, don't know how it happens but it should not be FEEL's fault anyway.. ;)

About wrong positions in layouts, it can sometimes happen, in case of crashes on layout change, to have some layout settings messed up..
In that (really not usual btw) case you have to restore layouts from the install package (or better from a good backup by you ;) ) to get back to work.
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #82 on: July 01, 2015, 04:58:23 pm »
I think I've found cause of crashes and one strange error. Error or crash always happens when I set vertical layout run game in game, quit mame (groovymame32_163) and hit lShift to change emulator with horizontal layout. But when next emulator is also vertical then everything is fine, in fact next emu can be horizontal again and nothing bad happens.

EDIT. No, wait. Orientation is not important, emulator is also not important. When run nestopia from horizontal layout and then switch to vba-m crach also appear :/

EDIT 2. Looks like problem is with resolution change, if one layout uses different resolution (denim, wood, MAME) then FEEL crashes during switching of course only when I run one game in any emulator.

EDIT. 3 Works fine (mostly) if I use option select emulator in menu

Sadly this crash is not logged in feel.log but error is. Attached

Another problem (it's probably my fault) is that sometimes layout switching does not rotate correctly. I managed fix this by setting everything once again form scratch but I attached current good configuration and previous bad. I really don't know what I did wrong.
« Last Edit: October 15, 2016, 06:38:50 am by haynor666 »

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #83 on: July 03, 2015, 03:17:10 pm »
There is second crash (so no log). Usually happens after I run couple games. Today  FEEL crashed twice after I leaved Tumble Pop.

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #84 on: July 03, 2015, 03:25:32 pm »
Hi haynor, I must admit in more than 3 years nobody's never experienced such a number of crashes.. And never in conjunction with mame's execution!! ??? Are you using screen resize very extensively?
That's the only place in which I noticed some bad behaviour.
This is somewhat related with XNA, because my code is quite clean and tested , and the crashes are not repeatable every time.
Anyway, I will locate some workaround for it..
Btw, I'll be out of home for weekend, I'll do some tests next week ;)
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #85 on: July 03, 2015, 03:58:29 pm »
First crash (layout switching) does not care what emu I use but second might be ralated to groovymame. It generates modelines on the fly for game. Second crash so far was reproduced only on XP x32. If I have to play on LCD I prefer MAMEUIFX.

baritonomarchetto

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 385
Re: new frontend F.E.E.L.
« Reply #86 on: July 04, 2015, 08:41:12 am »
Never ever had a FEEL crash on my racing cabinet with racermame, model 2, vivanonno and a bunch of other emus. I suppose there are problems on the emu side, in your case.

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #87 on: July 04, 2015, 05:15:37 pm »
First crash is present only from most recent version so if You have older FEEL than won't be any crash. Second one is probably related to groovymame. I'll do more test tests with model2, Nestopia and see how it goes.

BTW. What system do You use?

baritonomarchetto

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 385
Re: new frontend F.E.E.L.
« Reply #88 on: July 04, 2015, 06:13:33 pm »
OS? Windows xp sp3. I update FEEL as soon as a new release pops up
« Last Edit: July 04, 2015, 06:16:02 pm by baritonomarchetto »

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #89 on: July 05, 2015, 10:59:33 am »
I also have XP SP3. FEEL right now is v.1.8.0.6. Is this your current ?

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #90 on: July 10, 2015, 04:51:44 pm »
Hey haynor.. I'm out with new v.1.8.0.7.
This version contains a (possible) fix to your resolution-change bugs.
When you can, please try it and tell me if things work well now.
Thanks mate ;)
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #91 on: July 11, 2015, 09:05:50 am »
Both bugs are still there :(

Couple days ago I tried to enable second monitor (actually PC). Sadly my PC never enabled it. Since this experiment that white screen after leaving mame looks different so maybe all these problems are related to my specific hardware/software - Radeon 4350/Calamity (or maybe even general) ATI drivers.
« Last Edit: July 11, 2015, 09:09:04 am by haynor666 »

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #92 on: July 11, 2015, 10:26:15 am »
Oh sh.. :(
I currently use Calamity drivers on my cab, but with a older simplest 9250 ..
If you as i see are experiencing various problems with your videocard I suggest to remove drivers completely using ATI driver remover, and re-install from scratch the emudrivers.. That *should* solve most defects.
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #93 on: July 11, 2015, 11:56:24 am »
Reinstalling driver (full uninstall and install using ATI setup) didn't help. I even switch to LCD monitor (supports 640x480i) and still the same.

stigzler

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 879
  • It seemed like a good idea at the time....
    • Mago Arcade
Re: new frontend F.E.E.L.
« Reply #94 on: July 11, 2015, 12:19:32 pm »
But why this is another frontend using .NET and other ---steaming pile of meadow muffin---. ???

..and to think I thought that you didn't like it! :D

What fantastic support from these devs.

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #95 on: July 12, 2015, 04:41:16 pm »
dr.prodigy, I've found source of this grey screen during FEEL start and mame quit - this is color from windows gui - main color from oblject 3D in advanced properties of screen. If I change it to green than FEEL also has green screen.

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #96 on: July 12, 2015, 06:25:42 pm »
Whooooa, interesting! Never thought about that, thank you! :)
Mmmmmh, now I wonder how to hide it.. There's nothing about grey Windows' window in my code!
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #97 on: July 12, 2015, 06:31:33 pm »


..and to think I thought that you didn't like it! :D

What fantastic support from these devs.
Yep haynor in the end has jumped on this side of the barricade !! :-D
« Last Edit: July 13, 2015, 01:38:50 am by dr.prodigy »
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #98 on: July 13, 2015, 05:40:14 am »
Maybe this color is caused by the fact that whole FEEL screen is draw as one big window  instead draw as fullscreen :-\

Switching to second monitor works fine. It was my(or maybe even windows) fault. I simply cannot switch to undetected monitor (standard TV). Besides on second output unlike primary I use custom cable instead UMSA.

EDIT. I forgot to mention - crashes reproduced also on Win 7x64 on totally different hardware.
« Last Edit: July 13, 2015, 08:01:02 am by haynor666 »

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #99 on: July 14, 2015, 03:35:17 am »
I've found another problem. This time with variable [emulator_path] and/or roms_path.

Let's say I configured paths:

emulator_path            D:\mame
roms_path                  [emulator_path]\roms

Loading roms with such configuration works but creating games list does not. I get error "can't find [emulator_path]\roms".

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #100 on: July 14, 2015, 06:27:03 am »
I've found another problem. This time with variable [emulator_path] and/or roms_path.

Let's say I configured paths:

emulator_path            D:\mame
roms_path                  [emulator_path]\roms

Loading roms with such configuration works but creating games list does not. I get error "can't find [emulator_path]\roms".
Quite good testing you're doing! ;D
This is fixed and released (v.1.8.0.7: not changed version for such a simple debug!).
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #101 on: July 14, 2015, 06:31:18 am »
Maybe this color is caused by the fact that whole FEEL screen is draw as one big window  instead draw as fullscreen :-\
Okay, but I'm not sure I can do something about it.. underlying grey window is probably out of the scope of FEEL code.. I'll investigate and let you know. BTW, do you notice the grey background only when running in fullscreen mode, or even in test mode?

Switching to second monitor works fine. It was my(or maybe even windows) fault. I simply cannot switch to undetected monitor (standard TV). Besides on second output unlike primary I use custom cable instead UMSA.

EDIT. I forgot to mention - crashes reproduced also on Win 7x64 on totally different hardware.
Would you please explain this thing better? I'm not sure I understood..
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #102 on: July 14, 2015, 07:23:42 am »
I didn't notice it in test mode but right now I can only test Windows 7 x64. I'll try at home XP x32.

EDIT. Tested. Flashing screen is even in test mode.


I used two different solutions to TV connection. First TV was connected using primary (DVI) and using UMSA, Second TV was connected using secondary (VGA) using custom made cable. Maybe cable didn't allowed me to enabled second monitor or maybe it was windows detection problem (lack of EDID from TV which is normal). Anyway this has nothing to do with FEEL.
« Last Edit: July 14, 2015, 01:34:02 pm by haynor666 »

stigzler

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 879
  • It seemed like a good idea at the time....
    • Mago Arcade
Re: new frontend F.E.E.L.
« Reply #103 on: July 14, 2015, 01:42:41 pm »
Sorry - only half-reading, but is there a query about how to have from background as transparent in vb?

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #104 on: July 14, 2015, 03:55:56 pm »
Hi.. Well no, not exactly.. It looks like that, although through xna code FEEL controls all the video output of its window, for some reason during some transients upon emulator closure the underlying Feel main process window (which is grey as windows' default) appears for a fraction of sec.
Looks like a small bug in XNA, in the end.
Everything is developed in c# .NET framework 3.5.
If you have any suggestion, it would be of course very appreciated ;)
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #105 on: July 14, 2015, 04:25:42 pm »
I've probably another problem - building games list from mame exe twice causes program to crash.

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #106 on: July 14, 2015, 05:25:01 pm »
Well this 3d is getting embarassing!!
What kind of set-up you use haynor?!? :-D
This is something nobody has ever reported.. After dozens of satisfied users and more than 1 hundred emulators currently in use in FEEL!
..Would you please explain better what happens?

Ps: of course I appreciate the good work you're doing.. Thanks :)
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #107 on: July 14, 2015, 05:45:03 pm »
This behaviour was reproduced on Win7x64 with i5 2400 and Intel HD2000 and on Win 7x64 i5 4670k, GTX770, FEEL in test mode and with official mame 64 163.

When I start building games list using option Build list for first time this works but when I try to do this once again FEEL crashes right away. For testing I had only about 10 roms at work so list is short but at home whole mame set is readed.

This is what I get (description fields in polish, sorry):

Opis:
  Stopped working

Podpis problemu:
  Nazwa zdarzenia problemu:   CLR20r3
  Podpis problemu: 01:   feel.exe
  Podpis problemu: 02:   1.8.0.7
  Podpis problemu: 03:   55a4e1df
  Podpis problemu: 04:   mscorlib
  Podpis problemu: 05:   2.0.0.0
  Podpis problemu: 06:   53a12268
  Podpis problemu: 07:   3457
  Podpis problemu: 08:   21c
  Podpis problemu: 09:   System.IO.IOException
  Wersja systemu operacyjnego:   6.1.7601.2.1.0.768.3
  Identyfikator ustawień regionalnych:   1045

EDIT. FEEL does not crash on XP x32.
« Last Edit: July 16, 2015, 06:43:51 am by haynor666 »

stigzler

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 879
  • It seemed like a good idea at the time....
    • Mago Arcade
Re: new frontend F.E.E.L.
« Reply #108 on: July 15, 2015, 02:50:36 am »
Dunno xna. But there are ways to make form backgrounds transparent. If its brief, is xna reverting to a windows form briefly?

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #109 on: July 20, 2015, 06:44:16 am »
Today I've tested FEEL once again taking latest package and configuring everything once again on win 7 x64 with HD2000 with all updates for NET 3.5 so this time without groovymame and ATI/Calamity drivers.

This time I used official mame64 without any ini file (so mame is started with desktop resolution) and FEEL in test mode. For test I configured Daphne emu to use denim layout (because of different size/resolution). After I started single game I played short time, then quit and after couple second I hit LShift to change emulator to Daphne (with denim applied) FEEL popup error, even in test mode :/

Must call BeginScreenDeviceChange before calling EndScreenDeviceChange
System.InvalidOperationException: Must call BeginScreenDeviceChange before calling EndScreenDeviceChange
   w Microsoft.Xna.Framework.WindowsGameForm.EndScreenDeviceChange(String screenDeviceName, Int32 clientWidth, Int32 clientHeight)
   w Microsoft.Xna.Framework.WindowsGameWindow.EndScreenDeviceChange(String screenDeviceName, Int32 clientWidth, Int32 clientHeight)
   w Microsoft.Xna.Framework.GraphicsDeviceManager.ChangeDevice(Boolean forceCreate)
   w Microsoft.Xna.Framework.GraphicsDeviceManager.ApplyChanges()
   w feel.OBJScene.ChangeRes(Int32 resX, Int32 resY, Boolean rotateScreen)
   w feel.Feel.RefreshLayout()
   w feel.Feel.UpdateUI(GameTime gameTime)
   w feel.Feel.Update(GameTime gameTime)
   w Microsoft.Xna.Framework.Game.Tick()
   w Microsoft.Xna.Framework.Game.HostIdle(Object sender, EventArgs e)
   w Microsoft.Xna.Framework.GameHost.OnIdle()
   w Microsoft.Xna.Framework.WindowsGameHost.ApplicationIdle(Object sender, EventArgs e)
   w System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
   w System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMe ssageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   w System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   w System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   w System.Windows.Forms.Application.Run(Form mainForm)
   w Microsoft.Xna.Framework.WindowsGameHost.Run()
   w Microsoft.Xna.Framework.Game.Run()
   w feel.Feel.Main()

Dr.prodigy, could You look at this problem again, please?
« Last Edit: July 20, 2015, 06:47:09 am by haynor666 »

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #110 on: July 23, 2015, 05:42:51 pm »
Well of course I'll do.. In these days I'm a little busy so I cant do a lot.
Unfortunately I've been digging the thing quite deeply in the past, still without success (it's probably something wrong in xna code).
But if there's a solution, I'll find it.. Take it for granted ;-)
In the meanwhile I would suggest you to use layouts with same screen resolution only (this is true even if you move from a horizontal to a vertical layout with same sizes, i.e. 640x480 or 480x640v is the same): in this case resolution change code is not executed, so no crash should occur anymore.

Ps: Sorry for my late answer, let me know if this solves ;)
« Last Edit: July 23, 2015, 05:51:59 pm by dr.prodigy »
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #111 on: July 24, 2015, 01:51:59 am »
All my layouts has 640x480 but FEEL crashes even I switch from emulator layout mame to emulator with layout mame-vertical so orientation also cause this.

I did some tests and tested previous version. I tested back to 1.5 crashes happens but since previous ones didn't have layout switching crashes are only after I quit game (random - sometimes just quitting one game cause this, sometimes 10 different games).

EDIT. I forgot two things:
Yesterday I build list using ROMLister (it has nice feature - cutting from game names everything that is in brackets) I realized that ROMlister adds more control devices than FEEL. After browsing xml I've found differencies cause:

<input players="1" buttons="1" coins="2" tilt="yes">
         <control type="joy" ways="8"/>
         <control type="trackball" minimum="0" maximum="255" sensitivity="50" keydelta="10" reverse="yes"/>
      </input>

FEEL takes only first control type but ROMLister takes all so in FEEL we have for 720:
720
720 Degrees (rev 4)
1986
Atari Games


raster
Horizontal
stick - 1P - 2Bt

but in ROMLister we have:
720
720 Degrees
1986
Atari Games



Horz
stick, dial
« Last Edit: July 24, 2015, 06:26:04 am by haynor666 »

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #112 on: July 26, 2015, 04:17:27 am »
All my layouts has 640x480 but FEEL crashes even I switch from emulator layout mame to emulator with layout mame-vertical so orientation also cause this.
This should *never* happen: at layout change, if size x*y is not varying (even upon screen rotation), FEEL reloads object positions only, and doesn't touch anything about screen resolution.
Please double-check your setup (maybe, if you want, you could perhaps send me your zipped config and layouts, so that I can take a look? Send me a pvt msg if you want ;) ).
Anyway, I added another small res-change optimization code in v.1.8.0.8 new version (still applies to res-change cases, not when sizes don't change). Maybe it can help you out.

EDIT. I forgot two things:
Yesterday I build list using ROMLister (it has nice feature - cutting from game names everything that is in brackets) I realized that ROMlister adds more control devices than FEEL. After browsing xml I've found differencies cause:

<input players="1" buttons="1" coins="2" tilt="yes">
<control type="joy" ways="8"/>
<control type="trackball" minimum="0" maximum="255" sensitivity="50" keydelta="10" reverse="yes"/>
</input>

FEEL takes only first control type but ROMLister takes all so in FEEL we have for 720:
720
720 Degrees (rev 4)
1986
Atari Games


raster
Horizontal
stick - 1P - 2Bt

but in ROMLister we have:
720
720 Degrees
1986
Atari Games



Horz
stick, dial
Aaaah okay this is easy.. never noticed there's the possibility to have more than one controltype per rom!
This is fixed (now you'll see "stick,dial - 1P - 2Bt"), pls download v1.8.0.8 and you'll find out (of course, you'll need a list rebuild to see changes) ;)
« Last Edit: July 26, 2015, 07:38:15 am by dr.prodigy »
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #113 on: July 26, 2015, 08:05:36 am »
Thanks dr. prodigy but now it's getting even worse. Now I try to switch layouts from lets say r-type to r-type_vertical sometimes FEEL crash but sometimes not. When it crashes last used layout changes it's orientation partially - FEEL writes into layout.ini switched values for either background values or orientation or even option for rotation is erased. This is really strange. Should FEEL writes anything in layout.ini ? The same problem is with official layouts.

Crashes after I quit game are still there also :/
« Last Edit: July 26, 2015, 08:15:13 am by haynor666 »

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #114 on: July 26, 2015, 09:49:55 am »
Okay let's start it over..
- copy STD layouts in place from download pack
- start with horizontal layouts only, all with the same sizes x*y
- configure all your emus (set their own layout editing ini files manually - not changing it via menu)
Now..
1) Does everything work correctly in test mode?
2) Does it in fullscreen mode?

I know this looks a little stupid, but I fear in this troubleshooting we're getting too much "noise".. Beginning from scratch and simple things can help.
« Last Edit: July 26, 2015, 10:19:01 am by dr.prodigy »
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #115 on: July 26, 2015, 11:00:03 am »
Right now no crashes. For first time I've build everything from newest package using mame layout (default) leaving other emu also default.
For second time I copie my r-type layout (640x480) and so far no crashes.

Of course if I set daphne to use mame-vertical, then all problems regarding changing emulators reappear.
« Last Edit: July 26, 2015, 11:13:31 am by haynor666 »

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #116 on: July 27, 2015, 04:48:06 pm »
Okay, now this is *something*! :)

Well, given that (ie.: without rotations everything is well), download the new exe I uploaded just now (still numbered v.1.8.0.8 ), I've finally found why change res was occurring on rotation (my fault).

Now it isn't run anymore, so if you stick to the same screen size in your layouts you won't (hopefully!) never get exceptions/crashes.

Let me know, thank you! ;)
« Last Edit: July 28, 2015, 05:51:26 am by dr.prodigy »
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #117 on: July 28, 2015, 05:53:16 am »
Today I've test using LCD and fresh install XP x32, standard mame, standard ati driver (X1550). No crashes if I use layouts with 640x480 (which is my default config). Combination of rotated, non rotated layouts are finally fine but If I use denim layout then a different error appears:

EXECUTION ERROR
Must call BeginScreenDeviceChange before calling EndScreenDeviceChange
System.InvalidOperationException: Must call BeginScreenDeviceChange before calling EndScreenDeviceChange
   at Microsoft.Xna.Framework.WindowsGameForm.EndScreenDeviceChange(String screenDeviceName, Int32 clientWidth, Int32 clientHeight)
   at Microsoft.Xna.Framework.WindowsGameWindow.EndScreenDeviceChange(String screenDeviceName, Int32 clientWidth, Int32 clientHeight)
   at Microsoft.Xna.Framework.GraphicsDeviceManager.ChangeDevice(Boolean forceCreate)
   at Microsoft.Xna.Framework.GraphicsDeviceManager.ApplyChanges()
   at feel.OBJScene.ChangeRes(Int32 resX, Int32 resY, Boolean rotateScreen, Boolean applyChanges)
   at feel.Feel.RefreshLayout()
   at feel.Feel.UpdateUI(GameTime gameTime)
   at feel.Feel.Update(GameTime gameTime)
   at Microsoft.Xna.Framework.Game.Tick()
   at Microsoft.Xna.Framework.Game.HostIdle(Object sender, EventArgs e)
   at Microsoft.Xna.Framework.GameHost.OnIdle()
   at Microsoft.Xna.Framework.WindowsGameHost.ApplicationIdle(Object sender, EventArgs e)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMe ssageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at Microsoft.Xna.Framework.WindowsGameHost.Run()
   at Microsoft.Xna.Framework.Game.Run()
   at feel.Feel.Main()

BUT I'm not going to use layouts with different resolutions so it's no problem for me. Next step will test my own layouts and test everything on my hardware at home with groovymame and Calamity driver.

BTW. There is one bug, in fact already mentioned for one condition - [emulator_path] is some places does not work correctly. Today I realized that it does not work also with snap section, possibly others.

dr.prodigy

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 65
  • I want to build my own arcade controls!
Re: new frontend F.E.E.L.
« Reply #118 on: July 28, 2015, 06:06:25 am »
::) Okay haynor.. we knew that (when you change resolution you have crashes, and the exception you've posted is always the same..), but you should have no point in doing so (and probably nobody else should).

Please stick to one screen size of your choice (e.g. 640x480 as said, or any other) and you will be more than fine.

About [emulator_path] thing, would you please give me some details?
« Last Edit: July 28, 2015, 06:41:21 am by dr.prodigy »
"We don't stop playing because we grow old; we grow old because we stop playing"

F.E.E.L. - FrontEnd (Emulator Launcher) development & support
http://feelfrontend.altervista.org

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1071
  • retro maniac
Re: new frontend F.E.E.L.
« Reply #119 on: July 28, 2015, 06:52:00 am »
No problem, I'm using only 640x480 in layouts.

emulator_path               E:\mame
snap_path                     [emulator_path]\snap
Using [emulator_path]\snap does not show snaps in main window or screensaver but using just E:\mame\snap it's fine.

  
 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31