Trouble on Mac

Next
 From:  chippwalters
7045.1 
I tried adding the CustomUI stuff in the Mac app package contents and when I launched it just stuck a blank window on the screen. I quit and then deleted the app and put a fresh version in and now it won't launch at all.

I restarted, launched and all I got was a menu, which wouldn't quit the app so I had to Force Quit. So I tried launching again and the app icon jumped 'up and down' only once (it usually does it many times) and absolutely nothing launched.

What are the processes for Wine I need to Quit in the Activity Monitor so I can start Moi3D fresh again? Or is there something else I can do to get this to work? Should I delete my license and .ini files?
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
7045.2 In reply to 7045.1 
Hi Chipp, does this persist if you reboot the entire machine?

Seems like something must be getting cached by the system and not liking changes to the app.

The processes used by Wine would be wine and WineskinX11. But they do not launch automatically on system restart so if you reboot your system that should get you to a clean state I would think.

I doubt that deleting the license or .ini files would have any effect, something is going wrong with the Wineskin mechanism and not with MoI's own internals it sounds like.

What machine and operating system are you running with?

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  chippwalters
7045.3 In reply to 7045.2 
Geez Michael, I *CANNOT* believe you're still providing support at 4AM! Holy smokes, that has to be some kind of record for customer service. :)

Thanks for the quick reply. I was able to get everything working, including the custom interfaces with a third clean install. And I did not need to replace the ini files.

I'm wondering if it makes sense to move some of the plugin type files outside the app package? I suspect you haven't because hacking the package isn't officially supported (meaning designed for support). Still, it seems Apple or some virus app one day might do some Checksum against the package and then prevent it from launching if it's been changed. I don't think they want apps writing data to the package, though I really don't know for sure.

Thanks again. MoI3D has the *fastest* learning curve and is truly a most amazing 3D app. And now that I've mapped my custom keys from Lightwave to it, the workflow is second nature. Amazing how fast I can crank out ID concepts. I'll share some as soon as I have the OK from the client. Thanks again!
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
 From:  Michael Gibson
7045.4 In reply to 7045.3 
Hi Chipp, I'm glad you've got it all working now!

> I'm wondering if it makes sense to move some of the plugin type files outside the app package?

I would like to do something along those lines in the future - currently plug-ins have just not really been a major focus area quite yet.

One of the things I'd like to do in the future is not to just store them external to the app package but also have some kind of centralized online plug-in repository that you could browse through with some kind of UI inside of MoI so it would be simpler to install them.

But it takes time to develop such things, it just has not risen to the top of the priorities list yet.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All