Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrating into Front End Proves difficult #40

Closed
GoogleCodeExporter opened this issue Jul 9, 2015 · 6 comments
Closed

Integrating into Front End Proves difficult #40

GoogleCodeExporter opened this issue Jul 9, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1: When I start in front end, the window with all the processes and info
takes ahold as the main window.  The game launches, but because it is not
the main window you cannot see the game. I see all the text outlining the
game info, the game launch, the shaders etc.. (it looks like dos), but the
actual game window gets hidden.

I'm sorry I'm not able use more technical terms.


What is the expected output? What do you see instead?

The expected output is: For the game to launch, I am using the following
code through the front end (Maximus Arcade) -config
ImageReader:defaultImage=%file

But instead I see: the box describing all the commands and things that
usually happen behind the scenes.



What version of the product are you using? What build? What plugins?

I use version: 104r22

I use a *Edit This*Release*Debug*-NoTrace*Edit This* build

I use the following plugins: The default plugins that came with this relesse



On what kind of system?
My system specifications are as follows:

Operating System: Win 7 64 bit
CPU: i7
Video Card: ati hdradeon 4850
Sound Card: ? i'm not sure
Additional related hardware and/or software: 8 gb of ram


Please provide any additional information below:

*Edit me*Providing information on the selected options and/or features of
the software and/or the used plugins when building/running can also be of
some help*Edit me*


Original issue reported on code.google.com by omarruva...@gmail.com on 13 May 2010 at 7:29

@GoogleCodeExporter
Copy link
Author

Hmm, nullDC is built as a console application and creates the window later on 
-- 
probably thats why. Will see if i can fix it easyly

Original comment by drkIIRaziel on 13 May 2010 at 9:58

  • Changed state: Accepted
  • Added labels: Priority-Low, Type-Enhancement
  • Removed labels: Priority-Medium, Type-Defect

@GoogleCodeExporter
Copy link
Author

Ahh, probably, when I have it to launch at fullscreen it launches and I can 
hear it
running in the background.  When I do "alt+tab" I can tell that the console
application is focused on.  Do you have info about the commandline commands, 
maybe
that change would work too. 

Also it may be useful to know that I had no issues doing the same thing with an 
older
version of nulldc. 

The new version works great on my machine by the way. The plugins for the 
xbox360
controllers work perfectly. Glad to see work has picked up on this again.






Original comment by omarruva...@gmail.com on 13 May 2010 at 10:15

@GoogleCodeExporter
Copy link
Author

Not sure if this will address your problem but it couldn't hurt.

Open your nullDC.cfg file in Note pad.  Under the 1st heading "[nullDC]" the 
last
line is "Emulator.NoConsole=0" change the 0 to a 1 and the console will no 
longer
appear.  If this works for your FE problem the build team might want to consider
deactivating the console by default and recommend activating it only to people 
that
are having problems.  Just a thought...

Original comment by atomikb...@hotmail.com on 15 May 2010 at 4:37

@GoogleCodeExporter
Copy link
Author

I tried that and it did eliminate one issue, now I can see the emulator window 
when I
launch it, but the windows is small instead of fullscreen (even though 
fullscreen is
checked off, and in the cfg I made sure it was set to 1). 

When I start a game, the game starts in a small window and all the vmu boxes 
popup
when the game starts.  I wonder, is there a way to turn off the vmu displays? 
Maybe
that would help?

Also, maybe the commandline has changed recently? This is what the front end I 
use
has listed under the command line. 

-config ImageReader:defaultImage=%file

where %file is the cd image 

Original comment by omarruva...@gmail.com on 15 May 2010 at 6:51

@GoogleCodeExporter
Copy link
Author

so.. I added the emulator in under another system in the front end and it worked
fine, the issue is with the frontend, not your program.

I must really commend you for your work though.  I'm happy with this final 
release. 
Somethings aren't perfect (like no sound for project justice), but this is an 
amazing
update that works many games flawlessly.  Thank you for all your hardwork, 
you've
allowed me to relieve some of my memories from late high school and early 
college and
it's been really fun.

Original comment by omarruva...@gmail.com on 21 May 2010 at 7:34

@GoogleCodeExporter
Copy link
Author

Should be fixed in r26. If you can compile a binary try it w/ -config 
nullDC:NoConsole=1 -config ImageReader:defaultImage=%file

Original comment by drkIIRaziel on 23 May 2010 at 8:33

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant