-
Notifications
You must be signed in to change notification settings - Fork 14
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
Second /shutdown
blackscreens on the FFXI -> POL transition
#8
Comments
Other details:
|
i use windower 4 and it does the same thing hello yall im just checking yalls github im interested in programming again i used to do it for fun as a kid but it was like :"What to make" now on FFXI the possibilities are endless. i don't know how any of the new windows work last one i used was 2000xp but i knew a lil C++, Delphi, Visual Basic , Basic A, Q basic , and turbo paschal . right now i don't even know how to get superwarp to load but i made my own outta scripts im eager to learn and i love the challenge. i can be a assistant doing what yall tell me to do |
I would love the chance to join I am actually quite honored and thank you
for responding so fast I'm on the window or discord already but I don't
know if this is a new discord that y'all have for developers and thank you
again for reaching out to me I appreciate it -Maka
…On Fri, Jul 8, 2022, 10:29 AM Nifim ***@***.***> wrote:
@maka85 <https://github.com/maka85> if you are interested in helping you
can join our discord
<https://discord.com/channels/338590234235371531/633140308850376714>,
there we discuss a sorts of stuff related to our development and help
people with their own projects as well.
—
Reply to this email directly, view it on GitHub
<#8>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV2W5HMMQD7VAFFJA5ZPM2TVTBCNJANCNFSM45KPROAA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Nah, we use the same Discord server. We have some internal channels, reserved for the development team, and there's a public development channel, but access is guarded by roles - see the |
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->Mine still does the exact thing everytime I shutdown. As long as there is only one official shutdown it seems the other will hang. Maybe something with how the profile saves on exit? Logging to one file blocking another.? I don’t understand computers only a lil bit of programming ty for CCing me. Sent from Mail for Windows From: ByrthSent: Friday, December 23, 2022 8:29 AMTo: Windower/FenestraCc: maka85; MentionSubject: [Windower/Fenestra] Second `/shutdown` blackscreens on the FFXI -> POL transition (#8) If I am logged in with two accounts on windower 5 (no addons) and use /shutdown on both of them, the first one successfully transitions from FFXI -> POL -> desktop. However, the second one transitions from FFXI -> POL and hangs.I have observed this four times at this point. It is eminently repeatable.The one time that my first instance crashed to desktop (missing the crash handler), the second instance was able to /shutdown without hanging.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
If I am logged in with two accounts on windower 5 (no addons) and use
/shutdown
on both of them, the first one successfully transitions from FFXI -> POL -> desktop. However, the second one transitions from FFXI -> POL and hangs.I have observed this four times at this point. It is eminently repeatable.
The one time that my first instance crashed to desktop (missing the crash handler), the second instance was able to
/shutdown
without hanging.The text was updated successfully, but these errors were encountered: